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 1328244 - Satellite 6.2.0 Beta: remove the default foreman scenario from foreman-installer and emphasize katello scenario to prevent customer confusion/pain
Summary: Satellite 6.2.0 Beta: remove the default foreman scenario from foreman-instal...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-04-18 20:08 UTC by Xixi
Modified: 2019-09-26 14:47 UTC (History)
7 users (show)

Fixed In Version: katello-installer-base-3.0.0.19-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:17:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Xixi 2016-04-18 20:08:53 UTC 
Description of problem:
For Satellite 6.2 Beta the new installer is foreman-installer, with default scenario as foreman, which is not the correct one to use for Satellite install; there is also no messaging in the utility to use katello if installing Satellite.

Customers can easily and very likely choose the default foreman-scenario when trying to install Sat 6.2 Beta, and end up with incomplete Sat6 install/missing functionality which would look like an issue/bug - for example "not see content and subscription related menu items, (i.e. wouldn't be able to import a manifest)" - rather than having chosen the wrong scenario.

To avoid unnecessary customer confusion and pain, we need to:
a) delete foreman scenario for beta;
and
b) state clearly in foreman-installer commandline (when run without arguments and when listing/running scenarios) to use katello scenario for Satellite installation, and capsule scenario for Capsule installation.

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

How reproducible:
always

Steps to Reproduce:
1. (see above)
2.
3.

Actual results:
(see above)

Expected results:
(see above)

Additional info:
Comment 3 Martin Bacovsky 2016-04-18 20:53:18 UTC 
Proposed low risk changes for Beta:
- description of Katello scenario [1] 
- removal of foreman scenario [2]

[1] https://gitlab.sat.lab.tlv.redhat.com/satellite6/katello-installer/merge_requests/43
[2] https://gitlab.sat.lab.tlv.redhat.com/satellite6/satellite-packaging/merge_requests/22
Comment 4 Xixi 2016-04-18 21:16:19 UTC 
(In reply to Martin Bacovsky from comment #3)
> Proposed low risk changes for Beta:
> - description of Katello scenario [1] 
> - removal of foreman scenario [2]
> 
> [1]
> https://gitlab.sat.lab.tlv.redhat.com/satellite6/katello-installer/
> merge_requests/43

"Install Satellite server with Capsule"

Thank you Martin - to clarify this for customers, could we change "Capsule" to "Integrated Capsule"?  or remove "with Capsule" if it's always implied with a Satellite 6 installation, whichever is more consistent with the Installation Guide docs). 

> [2]
> https://gitlab.sat.lab.tlv.redhat.com/satellite6/satellite-packaging/
> merge_requests/22
Comment 5 Martin Bacovsky 2016-04-19 11:41:43 UTC 
Description was changed to "Install Satellite server with Integrated Capsule".
Comment 6 Lukas Pramuk 2016-04-21 12:19:05 UTC 
VERIFIED.

@Sat6.2.0-Beta-Snap9
foreman-installer-1.11.0.3-1.el7sat.noarch

# foreman-installer --list-scenarios
Available scenarios
  Capsule (use: --scenario capsule)
        Install a stand-alone Capsule.
  Katello (INSTALLED)
        Install Satellite server with Integrated Capsule

# foreman-installer --scenario foreman
ERROR: Scenario (/etc/foreman-installer/scenarios.d/foreman.yaml) was not found, can not continue

>>> now Katello scenario has decent description and Foreman scenario doesn't exist
Comment 7 Bryan Kearney 2016-07-27 11:17:55 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
Note You need to log in before you can comment on or make changes to this bug.