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:
It's reported that oftentimes customers delete manifest when trying to update subscriptions / upload a newer manifest, in which case all that's needed is a Refresh, and deletion would cause problems by losing/disconfiguring server and client subscriptions etc. The only times where manifest needs to be deleted includes when a Satellite server is no longer active or the manifest has been removed from the Customer Portal.
A confirmation step will address this confusion by explaining to users refresh vs delete and asking if they're sure they want to delete manifest or just go back and refresh it.
Version-Release number of selected component (if applicable):
Satellite 6
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Deleting a subscription manifest is one of the most destructive operations that can be done in a Satellite organization. I am STRONGLY in support of giving the user a very stern warning requiring an additional confirmation before deleting a manifest.
Manifest deletion means that
- I have to reupload my manifest.
- I have to reattach subs to
- systems
- hypervisors
- activation keys.
And while attaching subs is significantly better in Satellite 6.2.2+ this situation is best avoided. It is exceedingly rare to actually in a production scenario to have to DELETE a 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/RHBA-2017:1553