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 1448476

Summary: [Ref-Arch] HA wrong scenario to install integrated capsule
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: DocumentationAssignee: satellite-doc-list
Status: CLOSED CANTFIX QA Contact: satellite-doc-list
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.9CC: adahms, bthurber, swadeley
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 05:17:31 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: 1425213    

Description Kenny Tordeurs 2017-05-05 13:54:27 UTC 
Document URL: 

Section Number and Name: 4.1.3.2 Install Integrated Capsule On First Node - satnode1


Describe the issue: 
[root@satnode1 /]# satellite-installer --scanario capsule \
 --foreman-proxy-dns-interface "eth0" \
 --foreman-proxy-dns "true" \
 --foreman-proxy-dns-zone "sysmgmt.bos.redhat.com" \
 --foreman-proxy-dns-forwarders "10.19.2.10" \
 --foreman-proxy-dns-reverse "2.19.10.in-addr.arpa" \
 --foreman-proxy-dhcp "true" \
 --foreman-proxy-dhcp-interface "p2p2" \
 --foreman-proxy-dhcp-range "10.19.2.101 10.19.2.130" \
 --foreman-proxy-dhcp-gateway "10.19.2.254" \
 --foreman-proxy-dhcp-nameservers "10.19.2.10" \
 --foreman-proxy-tftp "true" \
--foreman-proxy-tftp-servername "10.19.2.10"
--capsule-puppet "true" \
--capsule-puppetca "true"

=> The scenario should still be satellite IMHO

Suggestions for improvement: 
Correct typo for scanario > scenario and it should be:

# satellite-installer --scenario satellite
...

Additional information: 
[root@satnode1 /]# satellite-installer --scanario capsule 
We can also see it's writing to the katello.log in the end and not foreman-proxy or capsule.log (/var/log/satellite-installer/katello.log )

 --foreman-proxy-dns-interface "eth0" \
 --foreman-proxy-dns "true" \
 --foreman-proxy-dns-zone "sysmgmt.bos.redhat.com" \
 --foreman-proxy-dns-forwarders "10.19.2.10" \
 --foreman-proxy-dns-reverse "2.19.10.in-addr.arpa" \
 --foreman-proxy-dhcp "true" \
 --foreman-proxy-dhcp-interface "p2p2" \
 --foreman-proxy-dhcp-range "10.19.2.101 10.19.2.130" \
 --foreman-proxy-dhcp-gateway "10.19.2.254" \
 --foreman-proxy-dhcp-nameservers "10.19.2.10" \
 --foreman-proxy-tftp "true" \
--foreman-proxy-tftp-servername "10.19.2.10"
--capsule-puppet "true" \
--capsule-puppetca "true"
Installing Done [100%]
[..........................................................................]
 Success!
 * Katello is running at https://sat62-ha.sysmgmt.bos.redhat.com
 Initial credentials are admin / xxxxxxxxxx
 * Capsule is running at https://sat62-ha.sysmgmt.bos.redhat.com:9090
 * To install additional capsule on separate machine continue by running:"
 capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/
$CAPSULE-certs.tar"
 The full log is at /var/log/satellite-installer/katello.log 

Also the following confirms it:
# satellite-installer --list-scenarios
~~~
Available scenarios
  Capsule (use: --scenario capsule)
        Install a stand-alone Capsule.
  Satellite (INSTALLED)
        Install Satellite server
~~~
Comment 1 Kenny Tordeurs 2017-05-05 13:58:38 UTC 
Document URL: 
https://access.redhat.com/sites/default/files/attachments/sat6ha-lb-refarch.pdf
https://access.redhat.com/articles/2474581
Comment 2 Stephen Wadeley 2017-05-05 14:08:19 UTC 
Hello Kenny

Thank you for reporting this issue.

Hello Balaji

Can you take care of this?


Thank you
Comment 3 Kenny Tordeurs 2017-05-09 17:09:48 UTC 
Still present in [0]

[0] https://access.redhat.com/documentation/en-us/reference_architectures/2017/html-single/deploying_a_highly_available_red_hat_satellite_server_6_environment/#create_shared_filesystems_for_ha_lvm
Comment 5 Andrew Dahms 2018-07-23 05:17:31 UTC 
This bug was raised against the document "Deploying a Highly Available Red Hat Satellite Server 6 Environment", for which customers are now being asked to contact Red Hat (either their account team or consulting team) directly for assistance.

Because the product documentation team is unable to process this request, and in consultation with the Reference Architecture team, I am now closing this bug.

See the following article for more information -

https://access.redhat.com/solutions/1603283