Description of problem: "410 gone" alert popped up on Satellite UI after manifest file successfully uploaded. Version-Release number of selected component (if applicable): 6.6.0 -Snap2 How reproducible: always Steps to Reproduce: 1. Install satellite. 2. Login to Satellite UI. 3. Click on the content sidebar and select Subscriptions 4. Upload manifest file. 5. Manifest file uploaded successfully. Actual results: After manifest file uploaded we observed "410 Gone" message on the Subscriptions screen. Expected results: This alert should not be displayed on the UI screen after manifest file uploaded. Additional info: This popped up alert didn't observe on Satellite 6.5.
Uploaded manifest file available on CDN, I downloaded it at "14 March 2019", And used the same manifest here(the Same step repeated today and observed 410 gone error with the older manifest file) But this issue didn't observe with the latest created manifest file.
Created redmine issue https://projects.theforeman.org/issues/26912 from this bug
Thanks Devendra, The error is valid, 410 GONE means the subscription allocation no longer exists in RHSM, you will have to create a new manifest in the portal and import it. I opened a PR to show a more user-friendly message.
Upstream bug assigned to jomitsch
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26912 has been resolved.
Thanks John for fixing this issue. This issue has been successfully verified with the latest snap(6.6.0-snap10). The populated message after uploading the non-existence manifest file was very meaningful. "The Subscription Allocation providing the imported manifest has been removed. Please create a new Subscription Allocation and import the new manifest."
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-2019:3172