Bug 1706721

Summary: Installer still shows 6.4 to 6.5 version to upgrade existing capsule
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: InstallationAssignee: Evgeni Golov <egolov>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: egolov, vsedmik
Target Milestone: 6.6.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: satellite-installer-6.6.0.4-1.beta Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nikhil Kathole 2019-05-06 07:26:59 UTC
Description of problem:

After satellite 6.6 install/upgrade, installer shows

* To upgrade an existing 6.4 Capsule to 6.5:
       Please see official documentation for steps and parameters to use when upgrading a 6.4 Capsule to 6.5.


Version-Release number of selected component (if applicable):
Satellite 6.6 snap 1


How reproducible: always


Steps to Reproduce:
1. Install/upgrade satellite


Actual results:

Once installer completed, it shows
* To upgrade an existing 6.4 Capsule to 6.5:
       Please see official documentation for steps and parameters to use when upgrading a 6.4 Capsule to 6.5.



Expected results:
* To upgrade an existing 6.5 Capsule to 6.6:
       Please see official documentation for steps and parameters to use when upgrading a 6.5 Capsule to 6.6.


Additional info:

Comment 7 errata-xmlrpc 2019-10-22 12:47:30 UTC
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/RHSA-2019:3172