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.
Created attachment 1471864[details]
Excerpt from foreman log file
If manifest can't be found upstream (usually in RHSM), "Subscriptions" page will display unhelpful error message that consists only of HTTP error. Satellite log is a bit better, but still doesn't make it easy to understand what the issue is.
Manifest might be missing from upstream if it was deleted there (this will result in error 410) or if manifest if was manually changed (this will result in error 404 and is probably done only by robottelo test framework).
Version-Release number of selected component (if applicable):
satellite-6.4.0-10.beta.el7sat.noarch
foreman-1.18.0.4-1.el7sat.noarch
katello-3.7.0-4.rc2.el7sat.noarch
Steps to Reproduce:
1. Go to access.redhat.com, create new subscription allocation, allocate some product and download manifest file
2. In Satellite, create new organization and upload manifest file
3. In access.redhat.com, remove subscription allocation created in step 1
4. In Satellite, go to Content -> Subscriptions
Actual results:
Following error message is displayed:
"410 Gone"
If instead of removing subscription, we manually change zip content ("uuid" must be changed in manifest.zip/consumer_export.zip/export/consumer.json), then error message will be "404 Not Found".
It's impossible to tell what caused this error and how to solve it.
Expected results:
More helpful error message is displayed.
Attaching screenshot of the error.
Note: in 6.3, this error will not exist, since there is no API call to the RHSM for upstream allocation information.
Verified!
@ Satellite 6.4 snap 22
Steps:
1. Go to access.redhat.com, created new subscription allocation, allocated some product and downloaded manifest file
2. In Satellite, created new organization and upload manifest file
3. In access.redhat.com, deleted manifest
4. In Satellite, go to Content -> Subscriptions
Observation:
The Satellite subscription page showed the subscriptions is No Loner available and 'No error as said in the description of this bug is shown'.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:2927
Created attachment 1471864 [details] Excerpt from foreman log file If manifest can't be found upstream (usually in RHSM), "Subscriptions" page will display unhelpful error message that consists only of HTTP error. Satellite log is a bit better, but still doesn't make it easy to understand what the issue is. Manifest might be missing from upstream if it was deleted there (this will result in error 410) or if manifest if was manually changed (this will result in error 404 and is probably done only by robottelo test framework). Version-Release number of selected component (if applicable): satellite-6.4.0-10.beta.el7sat.noarch foreman-1.18.0.4-1.el7sat.noarch katello-3.7.0-4.rc2.el7sat.noarch Steps to Reproduce: 1. Go to access.redhat.com, create new subscription allocation, allocate some product and download manifest file 2. In Satellite, create new organization and upload manifest file 3. In access.redhat.com, remove subscription allocation created in step 1 4. In Satellite, go to Content -> Subscriptions Actual results: Following error message is displayed: "410 Gone" If instead of removing subscription, we manually change zip content ("uuid" must be changed in manifest.zip/consumer_export.zip/export/consumer.json), then error message will be "404 Not Found". It's impossible to tell what caused this error and how to solve it. Expected results: More helpful error message is displayed.