Hide Forgot
Description of problem: In some cases it is useful to disable scenario (e.g. when it was replaced with new one) but not delete it. Disabled scenario should be hidden from scenario list and prevented from running but it should stay on the system to make migration to new scenario possible. Actual results: not possible Expected results: After 'foreman-installer --disable-scenario old_scenario' the old_scenario is not listed in --list-scenarios and is not possible to install.
Created redmine issue http://projects.theforeman.org/issues/14373 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/14373 has been closed ------------- Martin Bacovsky Applied in changeset commit:a0651adff0e32c54fdac822a0f9a863a38a1dd73.
foreman-installer --list-scenarios Available scenarios Capsule (use: --scenario capsule) Install a stand-alone Capsule. Katello (use: --scenario katello) Install Satellite server with Integrated Capsule [root@sjagtap-sat6 ~]# foreman-installer --disable-scenario capsule Scenario capsule was disabled [root@sjagtap-sat6 ~]# foreman-installer --list-scenarios Available scenarios Katello (use: --scenario katello) Install Satellite server with Integrated Capsule [root@sjagtap-sat6 ~]# foreman-installer -S capsule ERROR: Selected scenario is DISABLED, can not continue. Use --list-scenarios to list available options. You can also --enable-scenario SCENARIO to make the selected scenario available. [root@sjagtap-sat6 ~]# foreman-installer --enable-scenario capsule Scenario capsule was enabled [root@sjagtap-sat6 ~]# oreman-installer --list-scenarios -bash: oreman-installer: command not found [root@sjagtap-sat6 ~]# foreman-installer --list-scenarios Available scenarios Capsule (use: --scenario capsule) Install a stand-alone Capsule. Katello (use: --scenario katello) Install Satellite server with Integrated Capsule
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/RHBA-2016:1501