Bug 1448818

Summary:	[Ref-Arch] HA Installation not cleanup for satnode3
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Documentation	Assignee:	satellite-doc-list
Status:	CLOSED CANTFIX	QA Contact:	satellite-doc-list
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.9	CC:	adahms
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:27:25 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-08 09:40:12 UTC

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:

Comment 1 Kenny Tordeurs 2017-05-09 17:27:18 UTC

Still present in newer doc [0]

[0] https://access.redhat.com/documentation/en-us/reference_architectures/2017/html-single/deploying_a_highly_available_red_hat_satellite_server_6_environment/#installing_red_hat_satellite_on_third_node_satnode3

Comment 2 Andrew Dahms 2018-07-23 05:27:25 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