Bug 1360422

Summary:	[Docs] Need to explicitly document that use of DHCP any other interface will cause problems for QCI provisioning.
Product:	Red Hat Quickstart Cloud Installer	Reporter:	James Olin Oden <joden>
Component:	doc-Installation_Guide	Assignee:	Julie <juwu>
Status:	CLOSED ERRATA	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	bthurber, jlabocki, jmatthew, joden, juwu, tpapaioa
Target Milestone:	ga	Keywords:	Documentation, Triaged
Target Release:	1.0
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:	2016-09-13 16:34:29 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:

Description James Olin Oden 2016-07-26 17:04:44 UTC

Description of problem:
Presently the installation documentation: 

https://access.redhat.com/documentation/en/quickstart-cloud-installer/1.0/paged/quickstart-cloud-installer-guide/

though it specifies that there should be no DHCP server on the provisioning network, it does not explain that DHCP should not be used on the on any other interface (including extra interfaces not part of the documented network diagram).   If a customer does do this, then the resolv.conf will get 
overwritten, and the DNS server entry for the QCI machine will be removed.
We need to document explicitly that DHCP should either:

- not be used on any other interface.
- be configured to not update the resolv.conf (i.e. set PEERDNS=no in the
  interface file).

Either of these paths will work for the customer (and QCI).

Comment 3 James Olin Oden 2016-08-02 12:56:33 UTC

It might be good to let them know why this is important.   The first question I would have as a customer is "why?".

Comment 4 James Olin Oden 2016-08-02 15:03:29 UTC

Also, I worry that "in the environment" will be interpreted to be on not only the fusor/satellite system but other systems that are "in the environment".

Comment 6 James Olin Oden 2016-08-03 12:58:46 UTC

That's awesome.

Comment 8 errata-xmlrpc 2016-09-13 16:34:29 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2016:1862