Bug 1449153

Summary:	[Ref-Arch] HA pcs cluster setup is missing the name
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Documentation	Assignee:	satellite-doc-list
Status:	CLOSED CANTFIX	QA Contact:	satellite-doc-list
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.9	CC:	adahms
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
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:29:55 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-09 09:59:14 UTC

Document URL: https://access.redhat.com/sites/default/files/attachments/sat6ha-lb-refarch.pdf

Section Number and Name: 
4.1.4.2 Create The Cluster

Describe the issue: 
[root@satnode1 ~]# pcs cluster setup --start --name satnode1 satnode2 \
satnode3

=> In this case the name of the cluster would be satnode1 and satnode1 would not be part of the cluster

Suggestions for improvement: 
# pcs cluster setup --start --name clustername satnode1 satnode2 satnode3 

Additional information:

Comment 1 Kenny Tordeurs 2017-05-09 17:31:10 UTC

Still present in newest 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/#create_the_cluster

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