Bug 1448470

Summary:	[Ref-Arch] HA stop and disable named service but bind is not yet installed
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Documentation	Assignee:	satellite-doc-list
Status:	CLOSED CANTFIX	QA Contact:	satellite-doc-list
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2.9	CC:	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:19:54 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:38:57 UTC

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

Section Number and Name: 
4.1.2.7 Create Shared Filesystems For HA LVM
Stop and disable “named” service on all the nodes.
[root@satnode1 ~]# for HOST in satnode1 satnode2 satnode3; do systemctl
stop named.service; sysmtemctl disable named.service; done 

Describe the issue: 
Default installation of RHEL7 the named service is not present because bind package is not installed.

Suggestions for improvement: 
Not sure at which point this should be disabled and why it's done there.

Additional information: 
bind will be installed later with satellite-installer

Comment 1 Stephen Wadeley 2017-05-05 14:06:51 UTC

Hello Kenny

Thank you for reporting this issue.

Hello Balaji

Can you take care of this?


Thank you

Comment 2 Kenny Tordeurs 2017-05-09 17:03:16 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 4 Andrew Dahms 2018-07-23 05:19:54 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