Bug 1474707
Summary: | could not start DNS, unable to read config file: open /etc/origin/node/resolv.conf | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Gan Huang <ghuang> |
Component: | Installer | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.0 | CC: | aos-bugs, bleanhar, jokerman, mmccomas, sdodson, tkimura |
Target Milestone: | --- | ||
Target Release: | --- | ||
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: | 2017-08-10 05:32: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: |
Description
Gan Huang
2017-07-25 08:48:41 UTC
The problem is almost certainly related to the 'NM_CONTROLLED=no' line. Could you try configuring a static IP with nmcli: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html If disabling network manager was ever supported I think we should update our documentation to mention the new requirement. For now I'm moving this to 3.6.1 unless we find that it still doesn't work with nmcli. Hi Brenton, Actually I don't think it's related to the configuration of the interface. In today's testing, I can easily reproduce it in DHCP environment, But that's not reproduced 100%. I found that it could be reproduced 100% while using static interface. I'll spin up a new cluster with DHCP environment (there is no 'NM_CONTROLLED=no' settings) for you tomorrow in my time if needed. Thanks for the additional info. I'll move it back to the blocker list then. Thanks for pointing it out. I've set up another env with DHCP. # cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=dhcp DEVICE=eth0 HWADDR=fa:16:3e:48:80:91 ONBOOT=yes TYPE=Ethernet USERCTL=no It appears to me that it would fail once in almost 3 attempts. Looked at the logs, it seems the same issue with Comment 6. Logs for NetworkManager-dispatcher attached I think this may be fixed in https://github.com/openshift/openshift-ansible/pull/4890 Can you try it? I set up a huge bunch of environments, and haven't hit it yet. I assume it has been fixed according to my past experience. Verified with openshift-ansible-3.6.172.0.0-1.git.0.d90ca2b.el7.noarch.rpm Thanks Scott! 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-2017:1716 |