Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26725 has been resolved.
Sat 6.6 upgrade scenario is present in foreman_maintain-0.4.3.
FailedQA Version tested: # rpm -qa |grep maintain satellite-maintain-0.0.1-1.el7sat.noarch rubygem-foreman_maintain-0.4.3-2.el7sat.noarch We need https://github.com/theforeman/foreman_maintain/pull/270 as well for further 6.6 upgrades. See comment #6 as well.
Nikhil, The fix that includes 6.6.z is available in rubygem-foreman_maintain-0.4.4 - however, docker removal steps [1] are not present in it. We'll make another build once this is merged. [1] https://github.com/theforeman/foreman_maintain/pull/272
We're doing rubygem-foreman_maintain-0.4.5 release now.
VERIFIED Version tested: Satellite 6.6.0 snap 11 # rpm -qa | grep maintain satellite-maintain-0.0.1-1.el7sat.noarch rubygem-foreman_maintain-0.4.5-1.el7sat.noarch on sat 6.5: # foreman-maintain upgrade run --target-version not specified Possible target versions are: 6.5.z 6.6 on sat 6.6: # foreman-maintain upgrade run --target-version not specified Possible target versions are: 6.6.z 6.5 -> 6.6 and 6.6 -> 6.6.z upgrade successful.
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