See https://github.com/canonical/cloud-init/pull/6167 for cloud-init
fix.
** Project changed: cloud-init => cloud-init (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Importance: Unknown => Undecided
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => New
** Changed in: cloud-init (Ubuntu)
Remote watch: github.com/canonical/cloud-init/issues #6119 => None
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2106671
Title:
Deployments using a bonded interface on the "MAAS" management network
are broken
Status in MAAS:
Triaged
Status in MAAS 3.4 series:
Triaged
Status in MAAS 3.5 series:
Triaged
Status in MAAS 3.6 series:
Triaged
Status in cloud-init package in Ubuntu:
In Progress
Bug description:
Describe the bug:
Deployments of images using cloud-init 24.04.1 are stuck at
"rebooting" if you use a bonded interface on the network that is used
for the MAAS management.
Steps to reproduce:
Deploy noble 20250401 with a bonded interface
Expected behavior (what should have happened?):
Should work fine
Actual behavior (what actually happened?):
Machine is stuck at rebooting because cloud-init/netplan are not
waiting for the network interfaces to be configured and cloud-init
crashes when it tries to reach out to MAAS
MAAS version and installation type (deb, snap):
Any
MAAS setup (HA, single node, multiple regions/racks):
Any
Host OS distro and version:
Additional context:
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/2106671/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
