CoreOS since 1745.5.0 cannot fetch cloudinit #2452
Comments
I did re-test everything once again, and my that CoreOS on stable 1745.5.0 cannot fetch cloudinit file on pre-boot\bootstrap stage. |
I did check this for beta, 1772.2.0 has this problem too. |
Could you post the output of Also, what are the contents of |
journalctl of systemd-networkd:
|
Please create a file,
Then reboot and post the output of |
|
Err needs to be
|
And I did recheck isc-dhcpd again:
|
It seems that systemd-networkd is sending DHCP DISCOVER messages and receiving no response:
Can you obtain a packet trace at the DHCP server and see whether the messages are arriving there? |
Meanwhile isc-dhcpd:
isc-dhcpd log exactly same as I did pasted above. And I did remove all of leases and start over again, but see same result, btw ubuntu get ip address without any problems. To clarify some things, this setup with isc-dhcpd box, worked perfectly fine before ~1688.5.3 |
I did recheck, and new stable version, 1745.7.0 is booting, bootstrapping and doing everything as usual. |
@Savemech Great. Would you mind checking beta as well? |
Well I got hands on some latest vSphere, here is the log:
This one is broken, too. |
Any updates on that? |
Issue Report
Bug
Container Linux Version
Environment
vSphere 5.5
isc-dhcpd for dhcp
What hardware/cloud provider/hypervisor is being used to run Container Linux?
Expected Behavior
CoreOS boots, take IP from DHCP, fetches cloudinit file to properly configure self, then configure to static IP configured in VMware
Actual Behavior
CoreOS boots, did not trying to get DHCP IP address, fails to fetch cloud-init.yaml file, boots with "old" configuration
Reproduction Steps
Other Information
copy from CoreOS journalctl -u oem-cloudinit.service
isc-dhcpd log, Yes there is also available addresses in leases, also leases granted for 30 sec for max 60 sec, and that works absolutely fine with all stable <1688.x.x
At first I was, wow dhcp arent alive seems like, but as you see in log, there is ubuntu-server, which was specially booted to just check dhcp is working fine.
The text was updated successfully, but these errors were encountered: