I think we hit this on 26.04.1 with cloud-init 26.1-0ubuntu3~26.04.1 on
a mix of Graviton 2 and Graviton 3 instances. It happens a couple of
times per week: the instance finishes first boot with DataSourceNone and
never runs its user-data. A restart (from the AWS console) fixes it
every time.
Timeline from the journal and cloud-init.log of one affected instance:
```
3.06s Starting cloud-init-local.service
3.25s Finished cloud-init-local.service
DataSourceEc2.py[ERROR]: The instance must have at least one eligible
NIC
stages.py[INFO]: network config is disabled by fallback
3.46s kernel: ena 0000:00:05.0: enabling device (0010 -> 0012)
3.54s kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) found ...
3.64s kernel: ena 0000:00:05.0 ens5: renamed from eth0
... cloud-init-network retries IMDS for 240s, "Network is unreachable"
for both 169.254.169.254 and fd00:ec2::254
236.9s systemd-networkd: ens5: Configuring with
/run/systemd/network/10-netplan-ens5.network
(the fallback config cloud-init wrote after giving up)
240.3s Cloud-init ... finished. Datasource DataSourceNone.
```
Let me know if you need more logs or information.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2151279
Title:
cloud-init-local executes before ENA network driver completes PCI
probe, causing DataSourceEc2 failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2151279/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
