Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
VM content-host profile shows no subscriptions attached and auto-attach fails with an error "An error occured trying to auto-attach subscriptions. Please check logs for more information" . When you login to the Vm and run '# subscription-manager list --consumed' , it shows that the VDC derived sku has been properly consumed as expected.
Version-Release number of selected component (if applicable): 6.2.2
How reproducible: Not reproducible
Actual results:
Vm content-host profile in sat webui shows no subscriptions consumed
Expected results:
Vm content-host profile should show that the VDC derived sku has been consumed.
Additional info:
The workaround to this issue is changing the satellite manifest version from 6.1 to 6.2 and updating the manifest. But, the option to change the version does not appear in the customer's case.