Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1332319

Summary: Section 3.4 , Installing Satellite Server has a non working installation command
Product: Red Hat Satellite Reporter: Rich Jerrido <rjerrido>
Component: Docs Quick Start GuideAssignee: Allison Heslin <aheslin>
Status: CLOSED CURRENTRELEASE QA Contact: Brandi Munilla <bmcelvee>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.0CC: adahms, aheslin
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 21:31:47 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:

Description Rich Jerrido 2016-05-02 22:46:44 UTC
Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/quick-start-guide/chapter-3-installing-satellite-server

Section Number and Name: 3.4 

Describe the issue: 


Section 3.4, Step 2 provides the following command to install Satellite


# foreman-installer --scenario katello
--foreman-admin-username admin-username \
--foreman-admin-password admin-password \
--capsule-puppet true \
--capsule-puppet-ca-proxy true \
--foreman-proxy-tftp true

This command has two major errors

* the first line doesn't end with a backslash ('\') so bash treats it as two distinct commands

* the  --capsule-puppet-ca-proxy  switch says 'proxy puppet CA requests to $THIS' server. That is not the behavior that is desired. (The command as presented in the docs says 'proxy puppet CA traffic to a server with the hostname "true"'


The "--foreman-proxy-puppetca true" switch says 'enable the Puppet CA feature', which is what is actually desired. 

Suggestions for improvement: 


Replace the command in section 3.4, step 2 with the following. 


# foreman-installer --scenario katello \
--foreman-admin-username admin-username \
--foreman-admin-password admin-password \
--capsule-puppet true \
--foreman-proxy-puppetca true \
--foreman-proxy-tftp true

Comment 2 Allison Heslin 2016-05-03 13:19:30 UTC
Made the correction. Changes should be visible the next time the docs are refreshed for Beta.

Comment 3 Andrew Dahms 2016-05-03 21:31:47 UTC
This content is now live on the Customer Portal.

Closing.