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:
When importing a new manifest (after deleting old of course), the numbers for the old manifest still show up in Content > Red Hat Subscriptions. Clicking the link for that those entitlements sends up a perma-spinner, with a big trace in logs.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150324.0
How reproducible:
Steps to Reproduce:
1. Import a small manifest with 10 entitlements; consume some of these
2. Delete that manifest and import a larger one with 50 entitlements.
3. Go to Content > Red Hat subscriptions
4. Click the link for the old (consumed) entitlements.
Actual results:
"Loading..." spinner
Big log trace (forthcoming)
Expected results:
Traces of old subscription wiped out.
Additional info:
Notably, when I move my systems over to the new inventory (i.e., it should read 4 of 50), nothing ever gets updated there, either. Not sure if this is part of the same issue.
To emphasize - the old consumed entitlements do not appear to be available for consumption in Content Hosts UI. They seem to be gone everywhere except here.
Is this reproducible any longer? My guess is that it was due to elasticsearch not getting updated to reflect the new subscriptions. This should all be working now.
Comment #7 seems to be correct now, I think - I am no longer able to reproduce this. We can reopen if it rears its ugly head again.
Tested in Compose 7