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:
Issue with updating manifest of disconnected Satellite via sync host. Refresh with latest generated manifest will reult in candlepin error and make the subscription assign to Activation/Content Host in 'Invalid Subscription' status.
Version-Release number of selected component (if applicable):
How reproducible: Always.
Steps to Reproduce:
1. Generate a new manifest from Portal (due to subscription addition or other
reasons).
2. Refresh the newly generated manifest to Disconnected Satellite 6, this will
display a message "Owner has already imported from another subscription
management application" and candlepin errror is showing:
"Katello::Errors::CandlepinError: Owner has already imported from another subscription management application."
Activation key and Content Host get 'Invalid Subscription' status.
3. Delete the existing manifest and upload the latest, will lead to go to each
activation key/ Content Host and re-add/re-assign the subscription.
Actual results:
As per Step 2. and 3.
Step 3 is a workaround as documented in the KBase article;
https://access.redhat.com/solutions/1349373
but with an organization that has 100+ systems and growing, the current solution causes issues with large organization.
Expected results:
Refreshing the manifest should work without error.
Additional info:
Customer is aware that Disiconnected Satellite via sync host will soon be replace with another technology. But until then, customer needs a better resolution.