Red Hat Satellite 6 will not auto-attach Red Hat Enterprise Linux subscriptions if the activation key contains only custom product subscription

Solution Verified - Updated -

Environment

  • Red Hat Satellite 6

Issue

  • Red Hat Satellite 6 will not auto-attach subscriptions if the activation key contains only custom product subscriptions.

  • If auto-attach is set to yes for an activation key, and there are no subscriptions assigned to the activation key, the Red Hat Satellite auto-attaches to the best fit RHEL subscription from the general pool of subscriptions available to that Organization, even if it's the temporary virtual subscription until virt-who is executed. However, If there are ONLY custom products assigned to the Activation Key for third party products when a Content Host is registered with that Activation Key, it will not attach a Red Hat Enterprise Linux subscription.

Resolution

  • This has been determined to be the correct behaviour. The presence of any subscription whatsoever in the activation key will prevent auto-attach from running at registration time only. It will not stop future manual clicks of the Run auto-attach button from attaching subs, nor will it stop the auto-healing done when subscription-manager checks in.

  • To elicit auto-attach behavior at registration time in the above situation, it is recommended to use two Activation Keys.

  • The first Activation Key would have zero subscriptions attached, but would have auto-attach set to True. The second Activation Key would contain the subscriptions for the custom third-party products.

  • Then registration would specify both keys:

    # subscription-manager register --activationkey key1,key2

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.

Comments