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.
Document URL: https://access.redhat.com/sites/default/files/attachments/sat6ha-lb-refarch.pdf
Section Number and Name:
4.1.3.9 Installing Satellite on third node – satnode3
Describe the issue:
Repeat steps on satnode3 as mentioned in step Cleanup On satnode1 to 28
=> We are doing on installation on satnode3 not a cleanup
Suggestions for improvement:
Repeat steps on satnode3 as mentioned in step 4.1.3.6 Install Satellite On Second Node – satnode2
Additional information:
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