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.
DescriptionChristian Marineau
2018-03-18 16:46:37 UTC
Document URL:
This could be written in the "Prerequisites" section, or any relevant place:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/upgrading_and_updating_red_hat_satellite/
Section Number and Name:
To be determined
Describe the issue:
When the Satellite/Capsule setup involves a "High Availability" architecture (which is not support without "support exception"), attempting to Upgrade may result in a non working environment.
Users who need to keep their existing "HA" setup should *Not* upgrade to 6.3 until this scenario is fully supported, tested and documented.
Suggestions for improvement:
Add one or multiple Warning in the documentation so that the users will not try to attempt an upgrade until this scenario is fully supported, tested and documented.
Additional information:
There are actual known cases where the user faced an issue with their Capsules as they previously configured a multi-host certificate under Satellite 6.2. Following the upgrade steps will result in a broken "Satellite to Capsule" communication.