Thank you for filing this bug for a friend and making cloud-init better. So looks like an upgrade path affected these systems on Bionic. If possible do we have the ability to run `sudo cloud-init collect-logs` on an affected upgraded system and attach the resulting tarfile?
What we'd like to know to better triage this issue:
- Was there custom network config provided in either /etc/netplan or /etc/NetworkManager
- nmcli general
- netplan get all
- what version of systemd was on the affected system
- the contents of /run/systemd/network files
- the cloud-ini.tar.gz from cloud-init collect logs (which gives us journal info, logs etc)
NOTICE: if `sudo cloud-init query userdata` on the affected system contains secrets or passwords you'll want to avoid providing userdata at the collect-logs prompt
Thank you for filing this bug for a friend and making cloud-init better. So looks like an upgrade path affected these systems on Bionic. If possible do we have the ability to run `sudo cloud-init collect-logs` on an affected upgraded system and attach the resulting tarfile?
What we'd like to know to better triage this issue: network files
- Was there custom network config provided in either /etc/netplan or /etc/NetworkManager
- nmcli general
- netplan get all
- what version of systemd was on the affected system
- the contents of /run/systemd/
- the cloud-ini.tar.gz from cloud-init collect logs (which gives us journal info, logs etc)
NOTICE: if `sudo cloud-init query userdata` on the affected system contains secrets or passwords you'll want to avoid providing userdata at the collect-logs prompt