Bug 1243608 - Installation Guide: document Satellite / Capsule version compatibility
Summary: Installation Guide: document Satellite / Capsule version compatibility
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Peter Ondrejka
QA Contact: David O'Brien
URL:
Whiteboard:
: 1230962 (view as bug list)
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2015-07-15 23:01 UTC by Xixi
Modified: 2018-08-31 15:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1241264
Environment:
Last Closed: 2015-08-12 11:53:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xixi 2015-07-15 23:01:11 UTC
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.

Comment 1 Xixi 2015-07-15 23:02:56 UTC
(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

Comment 2 Bryan Kearney 2015-07-16 19:53:28 UTC
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.

Comment 9 Mike McCune 2015-08-03 14:36:37 UTC
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.

Comment 11 David O'Brien 2015-08-04 00:56:41 UTC
*** Bug 1230962 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.