Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1322025

Summary:	Add ability to enable/disable scenarios to foreman-installer
Product:	Red Hat Satellite	Reporter:	Martin Bacovsky <mbacovsk>
Component:	Installation	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED ERRATA	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, ehelms, kbidarka, mhulan, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14373
Whiteboard:
Fixed In Version:	rubygem-kafo-0.7.3-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:16:17 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:
Bug Depends On:
Bug Blocks:	1323708

Description Martin Bacovsky 2016-03-29 15:14:35 UTC

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.

Comment 2 Martin Bacovsky 2016-03-29 15:24:54 UTC

Created redmine issue http://projects.theforeman.org/issues/14373 from this bug

Comment 4 Bryan Kearney 2016-03-31 16:14:22 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/14373 has been closed
-------------
Martin Bacovsky
Applied in changeset commit:a0651adff0e32c54fdac822a0f9a863a38a1dd73.

Comment 5 Sanket Jagtap 2016-05-10 14:23:42 UTC

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

Comment 6 Bryan Kearney 2016-07-27 11:16:17 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/RHBA-2016:1501