Bug 1373273 - Installation script on 6.2 ISO prints outdated commands
Summary: Installation script on 6.2 ISO prints outdated commands
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1367674
TreeView+ depends on / blocked
 
Reported: 2016-09-05 16:09 UTC by Stephen Wadeley
Modified: 2019-09-26 14:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 21:56:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1370311 0 high CLOSED install_packages script from 6.2.1 references foreman-installer instead of satellite-installer 2021-02-22 00:41:40 UTC

Internal Links: 1370311

Description Stephen Wadeley 2016-09-05 16:09:40 UTC 
Description of problem:

 ISO for 6.2 has installation script which suggests using 6.1 style commands:

Install is complete. Please run foreman-installer --scenario katello

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

satellite-6.2.1-rhel-7-x86_64-dvd.iso

How reproducible:
everytime

Steps to Reproduce:
1. mkdir /media/sat6
2. mount -o loop /dev/disk/by-label/Satellite-6.2.1\\x20RHEL-7\\x20x86_64 /media/sat6
3. cd /media/sat6
4. ./install_packages

Actual results:
Install is complete. Please run foreman-installer --scenario katello

Expected results:
Install is complete. Please run satellite-installer --scenario satellite

Additional info:
As the ISO can also be used to install a Capsule Server, perhaps a more generic message is best. For example:

Install is complete. Please run satellite-installer with --scenario satellite or --scenario capsule.
Comment 2 Bryan Kearney 2016-09-29 21:56:09 UTC 
Version 6.2.2 of the ISO corrected this.
Note You need to log in before you can comment on or make changes to this bug.