I've added jammy:linux-gcp as a target for this patch, just for
consistency across the releases of Google kernels. I have not observed
the problematic behavior on Jammy myself. I've committed a config change
to make IDPF built in on linux-gcp from jammy to resolute.
Also of note: we have observed this same issue on Google's C4 bare metal
machines, not just C3.
** Changed in: linux-gcp (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Questing)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Resolute)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Noble)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
** Changed in: linux-gcp (Ubuntu Questing)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
** Changed in: linux-gcp (Ubuntu Resolute)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
** Also affects: linux-aws (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu Jammy)
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Jammy)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
--
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
