Bug 1335668

Summary:	satellite-installer --upgrade generates errors without --scenario or --force
Product:	Red Hat Satellite	Reporter:	Brad Buckingham <bbuckingham>
Component:	Installation	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED ERRATA	QA Contact:	Sachin Ghai <sghai>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	cwelton, ehelms, sghai
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	satellite-installer-6.2.0.3-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:32:09 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:	1335807

Description Brad Buckingham 2016-05-12 19:54:39 UTC

Description of problem:

Attempting to perform an upgrade of Satellite using satellite-installer requires both --scenario and --force in order to execute.

Version-Release number of selected component (if applicable):
Satellite 6.2 Snap 11

How reproducible:
Always

Steps to Reproduce:

1. install Satellite 6.1

2. satellite-installer --upgrade
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

Note: with the prior foreman-installer --upgrade appeared to default to katello (satellite)

3. satellite-installer --scenario satellite --upgrade
[ INFO 2016-05-12 18:53:23 verbose] Executing hooks in group pre_migrations
[ INFO 2016-05-12 18:53:23 verbose] All hooks in group pre_migrations finished
[ERROR 2016-05-12 18:53:23 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-05-12 18:53:23 verbose] Log was be written to /var/log/foreman-installer/satellite.log
[ INFO 2016-05-12 18:53:23 verbose] Logs flushed


Additional info:

Including --force will allow the upgrade to proceed; however, there are other issues during foreman_migrate to be addressed separately.

Comment 2 Brad Buckingham 2016-05-16 12:38:11 UTC

*** Bug 1335732 has been marked as a duplicate of this bug. ***

Comment 4 Sachin Ghai 2016-05-26 08:25:13 UTC

Verified with upgrade from sat6.1.9 -> sat6.2 snap13.1

Lists possible scenarios:
=========================
~]# satellite-installer --list-scenarios
Available scenarios
  Capsule (use: --scenario capsule)
        Install a stand-alone Capsule.
  Satellite (INSTALLED)
        Install Satelite server


Ran installer without --force option.
======================================
 ~]# satellite-installer --scenario satellite --upgrade
Upgrading...
Upgrade Step: stop_services...

subsequent upgrade without --scenario
====================================

~]# satellite-installer --upgrade
Upgrading...
Upgrade Step: stop_services...


Installer with invalid option:
==============================

 ~]# satellite-installer --test
ERROR: Unrecognised option '--test'

See: 'satellite-installer --help'


Installer with --help option
~]# satellite-installer --help
Usage:
    satellite-installer [OPTIONS]

Options:

= Generic:
    --reset                       This option will drop the Katello database and clear all subsequent backend data stores.You will lose all data! Unfortunately we
                                  can't detect a failure at the moment so you should verify the success
                                  manually. e.g. dropping can fail when DB is currently in use. (default: false)


Looks like reported issue is fixed. Moving this to verified. thanks

Comment 5 Bryan Kearney 2016-07-27 11:32:09 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