Bug 1369581

Summary:	Fusor-installer --list-scenarios actually runs the foreman-installer
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	fusor-installer	Assignee:	Derek Whatley <dwhatley>
Status:	CLOSED ERRATA	QA Contact:	Thom Carlin <tcarlin>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	dwhatley, smallamp, tsanders
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Triaged
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-13 16:37:22 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:

Description Thom Carlin 2016-08-23 20:42:57 UTC

Description of problem:

"fusor-installer --list-scenarios" displays the available scenarios (e.g. Fusor), then runs foreman-installer and rake fusor-setup

Version-Release number of selected component (if applicable):

QCI-1.0-RHEL-7-20160819.t.0

How reproducible:

100%

Steps to Reproduce:
1. Install QCI
2. "fusor-installer --list-scenarios"

Actual results:

Checks hardware
Displays Available scenario [Fusor]
Runs foreman-installer
Runs "rake fusor-setup"

Expected results:

Displays a message indicating "launch-fusor-installer" is correct "scenario"

Additional info:

Comment 2 Derek Whatley 2016-08-29 19:01:17 UTC

PR at https://github.com/fusor/fusor-installer/pull/92

Comment 3 Thom Carlin 2016-08-31 14:19:21 UTC

VERIFIED in QCI-1.0-RHEL-7-20160830.t.0

foreman-installer --list-scenarios
Available scenarios
  Capsule (use: --scenario capsule)
        Install a stand-alone Capsule.
  Satellite (use: --scenario satellite)
        Install Satelite server
  Fusor (INSTALLED)

Does *not* run installer -- which is correct behavior

Comment 5 errata-xmlrpc 2016-09-13 16:37:22 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/RHEA-2016:1862