Bug 1449930

Summary: [Ref-Arch] HA /var/lib/named instead of /var/named
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
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:31:16 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-11 07:56:09 UTC 
Document URL: https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_a_highly_available_red_hat_satellite_server_6_environment/installation_and_configuration#creating_pacemaker_resources

Section Number and Name: 4.5.5. Creating Pacemaker Resources
Filesystems

Describe the issue: 
[root@satnode1 /]# pcs resource create fs_named Filesystem device="/dev/sat_vg/lv_named" directory="/var/named" fstype="xfs"

In [0] it says the mount point is /var/lib/named and not /var/named
~~~
[root@satnode1 ~]# mkdir -p  /var/lib/named
AND
[root@satnode1 /]# mount  /dev/mapper/sat_vg-lv_named /var/lib/named
~~~

[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


Suggestions for improvement: 
[root@satnode1 /]# pcs resource create fs_named Filesystem device="/dev/sat_vg/lv_named" directory="/var/lib/named" fstype="xfs"

Additional information:
Comment 1 Andrew Dahms 2018-07-23 05:31:16 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