metadata api detection runs before network-online
Bug #1779139 reported by
Bernhard M. Wiedemann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Undecided
|
Unassigned |
Bug Description
Version: 18.2
originally filed at https:/
I found that cloud-init did not import authorized keys
because DataSourceNone was used
because the metadata API detection ran before the VM's network was up.
To post a comment you must log in.
typo corrections:
Thank you for the bug Bernhard and making cloud-init better. cloud-init needs to run before networking is up in some cases to collect any local metadata that may be available.
I heard mention of an issue that might be affecting you here, but it's hard to tell without cloud-init logs.
On the failed system, can you run "sudo cloud-init collect-logs" and attach the resulting cloud-init.tar.gz
Recent changes allow the OpenstackDatasource to use dhclient to setup a network sandbox to query metadata and configure networking on all nics with data from network_data.json.
My thoughts are that this issue related to EphemeralDHCP setup because SLES has wicked network client instead of dhclient installed. Without a dhclient utlity on the system, a traceback in DatasourceOpenStack detection would cause cloud-init to fallback to DataSourceNone as a catchall.