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:
Created redmine issue https://projects.theforeman.org/issues/35201 from this bug
Hello, There is a wrong version of rubygem-foreman_maintain in 6.12 snap2 (which comes from 6.11.1 snap2), could you please check? Thanks Gaurav
Hi, While testing upgrades with rubygem-foreman_maintain-1.1.4-1.el8sat.noarch, upgrades to 6.12.0 to 6.12.z succeeded for Satellite and Capsule, and upgrades from 6.11.z to 6.12.0 also passed for Satellite but failed for Capsule, with this error in the list-versions command, # foreman-maintain upgrade list-versions No such file or directory @ rb_check_realpath_internal - /etc/foreman-installer/scenarios.d/last_scenario.yaml Therefore, I am moving this BZ back to the ASSIGNED state. Please feel free to update it as needed. Thanks Gaurav
Hello, I am setting this back to ON_QA as we don't expecting missing the last_scenario.yaml in working state of Satellite or Capsule systems. @Gaurav request you to move it to verified state once you are done with any of the pending tests you may be working on. Regards, Amit Upadhye.
Verified. Tested on Satellite 6.12.0 Snap 8.0 Version: rubygem-foreman_maintain-1.1.4-1.el8sat.noarch Steps: 1. # foreman-maintain upgrade run --target-version 6.12 --whitelist 'repositories-validate,repositories-setup' Observation: Tested both Satellite and Capsule upgrades from 6.11.z to 6.12 and 6.12.0 to 6.12.z
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 (Important: Satellite 6.12 Release), 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-2022:8506