Bug 1592010
| Summary: | ansible installer fails to create "/etc/cni/net.d/80-openshift-network.conf" during installation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Preetesh Sharma <prsharma> | ||||
| Component: | Networking | Assignee: | Casey Callendrello <cdc> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Meng Bo <bmeng> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.9.0 | CC: | aos-bugs, bbennett, gkeegan, jokerman, ktadimar, mmccomas, pasik, szobair, tdudgeon.ml | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.9.z | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-08-22 20:55:53 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: | |||||||
| Attachments: |
|
||||||
|
Description
Preetesh Sharma
2018-06-16 05:48:48 UTC
The installer doesn't populate this directory. Moving to Networking. Do you have logs from the SDN pod? It writes the configuration file when it is up. I can readily show this in action if anyone wants to investigate. Please get in touch with me. There is lots of extra information available in the related github issue: https://github.com/openshift/openshift-ansible/issues/7967 Make sure you use a 3.9 commit of the installer. Installer master won't work on 3.9, since that file is written differently in 3.10 This has been needinfo for a week; dropping from urgent. I object to this being dropped to low priority. It is very significant problem! 5 days ago I pointed to lots of extra info on this, and offered to demonstrate this in action. Nobody has been in touch since. Can you get the logs of the SDN pod? That should indicate why it has not written the CNI file. This is not a containerised installation. Where would I look for the relevant logs? Since it's not a containerized install, the SDN is part of the node process. Check in "journalctl -u origin-node". The SDN will write that file once it has connected to the apiserver and determined the clusternetwork. If it fails to do so, it should log accordingly. So a thing to check is that the node process is able to talk to the apiserver. Sorry for delay on this - our cluster went down and took some time to get running again. What I'm finding now with the latest code on the release-3.9 branch of the ansible installer is that this problem is NOT manifesting itself. I ran through the installation process about 8 times and did not hit this problem. I'm not confident that this means its 'fixed', but right now I cannot generate any logs where it is happening. If the other users who have encountered this could also check if its still happening for them it would be useful. Venkata, OCP 3.7 and 3.9 use very different ways to create that file; please file a separate issue. Tim, I'm going to close this for now, feel free to reopen if the problem manifests itself. Be aware that there is still traffic on this issue on the upstream github project: https://github.com/openshift/openshift-ansible/issues/7967 For me on one environment its not happening now, but I'm not convinced that means its fixed. I hope to do some more tests soon in an environment where this happened more frequently. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |