** Summary changed:
- Delayed NIC initialization on c3-metal leads to first-boot metadata failures
+ Delayed NIC initialization on GCP and AWS instances lead to first-boot
metadata failures
** Changed in: linux-aws (Ubuntu Noble)
Assignee: (unassigned) => Leah Goldberg (goldberl)
** Changed in: linux-aws (Ubuntu Questing)
Assignee: (unassigned) => Leah Goldberg (goldberl)
** Changed in: linux-aws (Ubuntu Resolute)
Assignee: (unassigned) => Leah Goldberg (goldberl)
** Summary changed:
- Delayed NIC initialization on GCP and AWS instances lead to first-boot
metadata failures
+ Delayed NIC initialization on AWS and GCP instances lead to first-boot
metadata failures
** Description changed:
====== [Bug Description] ======
+
+ ----- AWS Instance -----
+
+ On Ubuntu 24.04 Minimal EC2 AMIs, cloud-init may fail to retrieve EC2
+ metadata and userdata on the first boot for certain instance types
+ (notably hpc7a.*, every time on hpc7a.96xlarge). This results in SSH
+ keys from user-data not being applied and prevents SSH access until the
+ instance is rebooted.
+
+ The issue appears to be caused by a race condition where no eligible
+ network interfaces are present during the init-local stage when the EC2
+ datasource attempts metadata discovery.
+
+ ----- GCP Instance -----
C3-metal instances on Google Cloud fail to boot properly because cloud-
init runs before the network interface (NIC) is up. As a result, cloud-
init cannot detect any instance datasource.
The issue appears to be caused by a race condition where no eligible
network interfaces are present during the init-local stage when the GCE
datasource attempts metadata discovery.
====== [Reproducer] ======
+
+ ----- AWS Instance -----
+
+ 1. Launch an Ubuntu 24.04 Noble Minimal EC2 AMI
+
+ 2. Use an EC2 instance type where network interfaces may not be immediately
available at early boot (e.g.
+ hpc7a.96xlarge reproduces consistently)
+
+ 3. Wait several minutes after the instance reaches running, then attempt
+ to SSH into the instance
+
+ You will see this error: ubuntu@<public-ip>: Permission denied
+ (publickey).
+
+ If you access the machine through the AWS console, you will see the following
cloud-init errors:
+ * Unable to get metadata
+ * The instance must have at least one eligible NICattempts metadata
discovery.
+
+ ----- GCP Instance -----
1. Launch a c3-standard-192-metal machine on Google cloud.
2. Wait several minutes after the instance reaches running, then attempt
to SSH into the instance
You will see this error: Permission denied (publickey).
If you access the machine through the Google cloud console, you will see the
following cloud-init errors:
* No instance datasource found! Likely bad things to come!
* Getting data from <class
'cloudinit.sources.DataSourceGCE.DataSourceGCELocal'> failed
====== [Environment Details] ======
+ ----- AWS Instance -----
+
+ * Cloud-init version: cloud-init 25.2-0ubuntu1~24.04.1
+ * Operating System Distribution: Ubuntu 24.04 LTS (Noble) Minimal AMI
+ * Cloud provider: Amazon EC2, hpc7a.* (notably hpc7a.96xlarge) instances
+ * Kernel: linux-image-6.14.0-1018-aws
+
+ ----- GCP Instance -----
+
* Cloud-init version: cloud-init 25.3~2g890873f5-0ubuntu2
* Operating System Distribution: Ubuntu Questing (25.10) and Ubuntu Noble
(24.04)
* Cloud provider, platform or installer type: Google
* Kernel: linux-image-6.17.0-1008-gcp
====== [Suggested Fixes] ======
- Include the `IDPF` driver as a built-in module in the noble and questing
- gcp kernels.
+ * Include the `ENA_ETHERNET` driver as a built-in module in the noble aws
kernel.
+ * Include the `IDPF` driver as a built-in module in the noble and questing
gcp kernels.
====== [Related Links] ======
- cloud-init bug: https://github.com/canonical/cloud-init/issues/6737
+ cloud-init bug AWS: https://github.com/canonical/cloud-init/issues/6697
+ cloud-init bug GCP: https://github.com/canonical/cloud-init/issues/6737
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2144694
Title:
Delayed NIC initialization on AWS and GCP instances lead to first-boot
metadata failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2144694/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
