Description of problem: Scenarios present inside satellite-maintain content should be restricted Version-Release number of selected component (if applicable): Satellite 6.8 Beta rubygem-foreman_maintain-0.6.8-1.el7sat.noarch How reproducible: # satellite-maintain content switchover Running Switch support for certain content from Pulp 2 to Pulp 3 ================================================================================ Switch support for certain content from Pulp 2 to Pulp 3: Performing final content migration before switching content [FAIL] Failed executing foreman-rake katello:pulp3_migration, exit status 127: sh: foreman-rake: command not found -------------------------------------------------------------------------------- Scenario [Switch support for certain content from Pulp 2 to Pulp 3] failed. The following steps ended up in failing state: [content-switchover] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="content-switchover" Actual results: Scenario to switch content from Pulp 2 to Pulp 3 is attempted. Expected results: Red Hat Satellite 6.x, still has Pulp-2, so "# satellite-maintain content" should be hide or scenarios present should not be executed.
Hello Ameya, Pull-request already opened and currently under review. With this change, it won't run any steps inside but those sub-commands will be visible. https://github.com/theforeman/foreman_maintain/pull/376 Linking the upstream issue to BZ for further tracking. Thanks for reporting this. - Kavita
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30458 has been resolved.
Verified verified with: - Satellite 6.8.0 snap 14 - rubygem-foreman_maintain-0.6.9-1.el7sat.noarch Test steps: 1. foreman-maintain content prepare 2. foreman-maintain content switchover Observation: - Scenario present in prepare and switchover command are not executed.
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 (Satellite 6.8 Satellite Maintenance 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/RHBA-2020:4365