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.
1. Proposed title of this feature request
satellite-maintain should not suggest any whitelist options if the migration or upgrade fails.
2. What is the nature and description of the request?
In recent times, we have seen many cases where customer tries to upgrade/migrate data from pulp2 to pulp2,
using Satellite-maintain and When the update/upgrade fails due to a certain steps/checks, satellite-maintains just suggest
to whitelist those steps/checks.
For example:-
~~~~~~~~~~--whitelist="packages-update"
--whitelist="content-switchover"
--whitelist="installer-upgrade"
~~~~~~~~~~
These options rather than adding values to the upgrading procedure add a devastating effect
(Like pulp2 to pulp3 migration is skipped or satellite-maintain was executed successfully
however packages were not updated), which causes major problems later.
In order to avoid those issues, I would suggest "satellite-maintain should not suggest any whitelist options if the migration or upgrade fails."
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.