Bug 1004486 - Table 3.1 Installation Options not match install.pl script --help
Table 3.1 Installation Options not match install.pl script --help
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Installation Guide (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Dan Macpherson
Dan Macpherson
Depends On:
Blocks: sat560-docs
  Show dependency treegraph
Reported: 2013-09-04 14:05 EDT by DzungDo
Modified: 2013-10-11 07:26 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-11 07:26:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description DzungDo 2013-09-04 14:05:00 EDT
Description of problem:

Running "install.pl --help" returned a different installation option list than what is in the installation documentation (documentation out of date possibly?).
Documentation has "--external-db" as an option; The install.pl script presented three separate options: --external-oracle, --external-postgresql, and --managed-db

Version-Release number of selected component (if applicable):
ISO image: Satellite-5.6.0-RHEL6-re20130903.0-x86_64.iso
Document location: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Satellite/5.6/html/Installation_Guide/sect-Installation_Guide-Installation-PreInstallation.html

How reproducible:

Steps to Reproduce:
1. mount Satellite-5.6.0-RHEL6-re20130903.0-x86_64.iso and run install.pl --help
2. Then compare to documentation

Actual results:

Expected results:
Same list of options on both places(?)

Additional info:
Comment 3 Clifford Perry 2013-10-11 07:26:48 EDT
Satellite 5.6 Documentation is published, as part of the 5.6 release and can be found here: 


Closing this bug out. Please open a new bug, if there is further issues/concerns with the Satellite Documentation.


Note You need to log in before you can comment on or make changes to this bug.