Bug 1803962
Summary: | Installing on VMware, all nodes try to bootstrap themselves as "localhost" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Hugo Cisneiros (Eitch) <hcisneir> |
Component: | RHCOS | Assignee: | Ben Howard <behoward> |
Status: | CLOSED DUPLICATE | QA Contact: | Michael Nguyen <mnguyen> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.z | CC: | bbreard, behoward, dustymabe, imcleod, jligon, miabbott, nstielau, osousa, walters |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-05 18:14:04 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
Hugo Cisneiros (Eitch)
2020-02-17 20:06:06 UTC
Do you have a console log from one of the affected hosts? I don't have it currently, do you know any way to get it in VMware? Or is there a specific file(s) which contain the logs you want? (dmesg, journalct, etc) Can you fetch dmesg, journalctl and the contents of /etc/resolv.conf? This is something we should investigate as part of the work to improve static IP networking on VMWare in 4.5 Do you recommend any workarounds? The customer can't install 4.x on their infrastructure because of this. Maybe using the bare metal installation and raw image instead of using .ova would work? Please note that we used DHCP and not kernel command line options to set a static IP. A likely workaround is to encode /etc/hostname in Ignition. But, I agree we should probably be handling this by default. Fix for this should be in 4.3.4. *** This bug has been marked as a duplicate of bug 1763700 *** Hi Colin, The referenced bug 1763700 was fixed in 4.3.0. Is there any new bugs to track this on 4.3.4? For some reason that patch didn't actually make it into 4.3.0. But it should be in the next 4.3.X release (which is probably 4.3.5). I specifically verified the fix is in https://openshift-release.svc.ci.openshift.org/releasestream/4.4.0-0.nightly/release/4.4.0-0.nightly-2020-03-05-142733 *** Bug 1839900 has been marked as a duplicate of this bug. *** |