Seeing temporary subscription attached on the newly build machine when using virt-who in Red Hat Satellite provisioning

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.2.x.

Issue

  • Getting a temporary subscription when using activation key with VDC subscription attached.

  • Unable to provision a machine, it fails at the step of attaching the VDC subscriptions.

Resolution

  • Change the provisioning template settings for post install steps with below information:
echo "Registering the System"
subscription-manager register --org="<%= @host.rhsm_organization_label %>" --name="<%= @host.name %>" --activationkey="<%= @host.params['kt_activation_keys'] %>"
subscription-manager attach --auto<<<<<<<<<<<<<<<<<<<<<<<Add this line to the post install step of registration.

For more KB articles/solutions related to Red Hat Satellite 6.x Provisioning Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Provisioning related Issues

Root Cause

  • Below error can be found in candlepin logs-
2017-06-15 11:33:45,148 [thread=http-bio-8443-exec-9] [req=479d8c69-2b20-4f06-93de-daa74a7153ed, org=redhat] INFO  org.candlepin.service.impl.DefaultEntitlementCertServiceAdapter - Setting 24h expiration for unmapped guest pool entilement: Fri Jun 16 11:29:54 CEST 2017

Diagnostic Steps

  • At the time of provisioning the VM, the subscription attaching step fails and the system will get temporary subscriptions just after the reboot of the VM.

  • The system should get a temporary subscription before reboot only.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.