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.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Upgrading_Red_Hat_Satellite_and_Capsule_Server.html
Section Number and Name:
Chapter 7. Upgrading Red Hat Satellite Server and Capsule Server
Describe the issue:
no messaging on supported upgrade paths and Satellite/Capsule compatibility
Suggestions for improvement:
messaging on supported upgrade paths and Satellite/Capsule compatibility, for example from the beta FAQ:
"1) Supported upgrade paths for Satellite 6.1 GA:
Satellite 6.0 -> Satellite 6.1 (standard, Beta for non-production/testing, GA for production)
Satellite 6.1 Beta -> Satellite 6.1 GA (Only if Satellite 6.1 beta is not in production during Beta)
2) Unsupported upgrade paths: Production Satellite 6.0 -> Satellite 6.1 Beta -> Satellite 6.1
3) Capsule needs to be the same version as Satellite i.e. cannot run Capsule 6.0 with Satellite 6.1 or vice versa.
Customers using Satellite 6.0 and earlier can Beta 6.1 as a new installation for non-production testing and then upgrade to production use from that Beta to GA.
(see https://access.redhat.com/articles/1475583#Q_Upgrade_paths for more)"
Additional information:
+++ This bug was initially created as a clone of Bug #1241264 +++
Description of problem:
Currently, Capsule server fails silently if version does not match Satellite (e.g. 6.1 vs 6.0). Instead it needs to clearly alert/explain to user from Capsule and Satellite the matching versions and to upgrade as needed. This would improve usability/ customer experience and reduce support calls.
(In reply to Xixi from comment #0)
> 3) Capsule needs to be the same version as Satellite i.e. cannot run Capsule
> 6.0 with Satellite 6.1 or vice versa.
>
this particular note is probably good for the Satellite/Capsule Installation pre-req section
I think item 3 is relevant above. We should state in the docs that the server and capsule must be in sync. Ideally, this would be in section 7 and Section 1.
if we can I would change it to:
"Satellite 6.1 Public Beta (non-production) -> Satellite 6.1 GA"
with the addition of the "Public" to the sentence. We had a private beta for ~20 customers and this will help clarify for them.