Bug 1316238

Summary: foreman-installer --scenario capsule --help fails and not provide help information when Satellite is already installed
Product: Red Hat Satellite Reporter: Elyézer Rezende <erezende>
Component: InstallerAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED ERRATA QA Contact: Sanket Jagtap <sjagtap>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, ehelms, erezende, kbidarka
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
URL: http://projects.theforeman.org/issues/13850
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:03:56 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 Elyézer Rezende 2016-03-09 18:34:05 UTC
Description of problem:
Running foreman-installer --scenario capsule --help is not providing the help information and failing.

Version-Release number of selected component (if applicable):
Sat6.2.0-Beta-Snap3.0

How reproducible:
Always

Steps to Reproduce:
1. Have Satellite installed (--scenario katello)
2. Run foreman-installer --scenario capsule --help


Actual results:
Command fail and not provide help information

Expected results:
Command prints the help information and exits

Additional info:
Sample run output

# foreman-installer --scenario capsule --help
[ INFO 2016-03-09 13:29:58 verbose] Executing hooks in group pre_migrations
[ INFO 2016-03-09 13:29:58 verbose] All hooks in group pre_migrations finished
[ERROR 2016-03-09 13:29:58 verbose] You are trying to replace existing installation with different scenario. This may lead to unpredictable states. Use --force to override. You can use --compare-scenarios to see the differences
[ INFO 2016-03-09 13:29:58 verbose] Log was be written to /var/log/foreman-installer/capsule.log
[ INFO 2016-03-09 13:29:58 verbose] Logs flushed

Comment 1 Brad Buckingham 2016-03-10 17:18:51 UTC
Is it correct to assume that the prior version was Satellite 6.2 and it was installed with 'foreman-installer --scenario katello'?  

Or was it a previous version of Satellite (i.e. using katello-installer)?

Comment 2 Elyézer Rezende 2016-04-06 02:40:26 UTC
Yes. It is a Satellite 6.2 which was installed with 'foreman-installer --scenario katello'. Since I was looking for information about the capsule scenario I decided to run the command to check what options are available for the capsule scenario.

I just ran the command on a recent build and got the following:

[root@sat62-beta ~]# foreman-installer --scenario capsule --help
[ INFO 2016-04-05 22:38:40 verbose] Executing hooks in group pre_migrations
[ INFO 2016-04-05 22:38:40 verbose] All hooks in group pre_migrations finished
[ERROR 2016-04-05 22:38:40 verbose] You are trying to replace existing installation with different scenario. This may lead to unpredictable states. Use --force to override. You can use --compare-scenarios to see the differences
[ INFO 2016-04-05 22:38:40 verbose] Log was be written to /var/log/foreman-installer/capsule.log
[ INFO 2016-04-05 22:38:40 verbose] Logs flushed

[root@sat62-beta ~]# rpm -qa | grep satellite
tfm-rubygem-foreman_theme_satellite-0.1.3-1.el7sat.noarch
satellite-6.2.0-6.1.beta.el7sat.noarch

Comment 4 Martin Bacovsky 2016-04-25 11:50:07 UTC
Connecting redmine issue http://projects.theforeman.org/issues/13850 from this bug

Comment 5 Martin Bacovsky 2016-04-25 11:53:01 UTC
The upstream issue was fixed.

Comment 6 Sanket Jagtap 2016-05-10 14:27:07 UTC
foreman-installer --scenario capsule --help
and
foreman-installer -S capsule --full-help
works provides the help options

Comment 7 Bryan Kearney 2016-07-27 11:03:56 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