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).
It might be good to let them know why this is important. The first question I would have as a customer is "why?".
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".
That's awesome.
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