Description of problem:

3-node cluster bootstrap failed due to missing /etc/resolve.conf. 

Version-Release number of selected component (if applicable):

4.11

How reproducible:

100% in my ipv6 virtual env with 4.11.0-fc.6 build

Steps to Reproduce:
1.  trigger ipi deployment with a 3-node cluster
2. waiting for openshift nodes to appear
3. 

Actual results:

openshift nodes did not appear, pods stuck at pending.

journal log indicates name resolution failure. 

noticed /etc/resolve.conf does not exist.

Expected results:

install succeeded

Additional info:

• after restarting NetworkManager, /etc/resolve.conf was created and installation continued.
• journal log before restarting NetworkManager:

[core@openshift-master-0 ~]$ journalctl -l --system | tail -1
Aug 03 17:33:47 openshift-master-0.kni-qe-15.lab.eng.rdu2.redhat.com sh[351063]: Error: initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4780fe1a31696f4de04d5915ac40f5d9ff62a7306857b58359f1895e0881d3e3: (Mirrors also failed: [registry.kni-qe-15.lab.eng.rdu2.redhat.com:5005/openshift-release-dev/ocp-v4.0-art-dev@sha256:4780fe1a31696f4de04d5915ac40f5d9ff62a7306857b58359f1895e0881d3e3: pinging container registry registry.kni-qe-15.lab.eng.rdu2.redhat.com:5005: Get "https://registry.kni-qe-15.lab.eng.rdu2.redhat.com:5005/v2/": dial tcp: lookup registry.kni-qe-15.lab.eng.rdu2.redhat.com on [::1]:53: read udp [::1]:54133->[::1]:53: read: connection refused]): quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4780fe1a31696f4de04d5915ac40f5d9ff62a7306857b58359f1895e0881d3e3: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp: lookup quay.io on [::1]:53: read udp [::1]:50893->[::1]:53: read: connection refused