Guestinfo configuration applied in wrong order #2630
When applying a guestinfo configuration in VMware, CoreOS attempts to connect to the
Container Linux Version
What hardware/cloud provider/hypervisor is being used to run Container Linux?
CoreOS should configure the network prior to fetching
coreos-cloudinit: 2019/11/08 07:10:48 Unable to fetch data: Get https://host/coreos/path/user_data: dial tcp: lookup host: no such host
vApp environment xml:
The text was updated successfully, but these errors were encountered:
@theit8514 thanks for the report. The configuration you are trying to apply is for cloud-init, which is known to have such race issues and has been superseded by Ignition.
The recommendation is to follow https://coreos.com/os/docs/latest/booting-on-vmware.html#defining-the-ignition-config-in-guestinfo and stick to
Thanks for the reply. The only thing I didn't state from the above is that these settings were generated by the CoreOS OVA file.
I have tried switching over to the
I am still seeing a race condition with my config: The IP address is not pingable and Ignition is attempting to fetch the config but failing now due to systemd-resolved "connection refused". It also seems to be stuck in an infinite boot loop waiting for ignition to complete.
I have tried both config>replace and config>append.
I found this document stating that my use case is not supported and to use kernel ip= parameters: https://coreos.com/ignition/docs/latest/network-configuration.html#using-static-ip-addresses-with-ignition
Attempting to do so (
@theit8514 at an high level, you are expecting Ignition to fetch and apply a configuration to change the initramfs (i.e. the environment where Ignition is running), in order to influence how Ignition fetches its configuration. This is a fundamental chicken-egg problem which (by design) cannot be solved by Ignition alone.
There are have a few ways out of that: