> if the issue is cloud-init inside the 24.04 deploy image, how come the
fix is going to be a MAAS fix?
There is nothing to fix in MAAS: the cloud-init team has to publish a
new update to the archive.
To give you more context, everything was working until ~a week ago
because the original version of cloud-init for 24.04 was 24.1.3 (and it
was not affected). Then, last week 24.4.1-0ubuntu0~24.04.2 was pushed to
the updates in the archive and given that MAAS is upgrading cloud-init
(if there is an update available) this is how you ended up with the new
version with the bug.
** Changed in: maas
Status: Triaged => Invalid
** Changed in: maas
Importance: High => Undecided
** Changed in: maas
Milestone: 3.7.0 => None
--
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/2103903
Title:
Deployment fails when using interface with OVS bridge
Status in cloud-init:
New
Status in MAAS:
Invalid
Bug description:
Describe the bug:
When trying to deploy a 24.04 Ubuntu node with OVS bridge configured on the
interface as primary network, deployment will fail over cloud-init error
("cannot apply final stage").
Notes:
Commissioning of the node is ok.
Deploying the same node with linux bridge instead of OVS is ok.
Deploying 22.04 with OVS is ok.
It was working for us with 24.04 as well, however at some point is stopped
working.
Steps to reproduce:
1. Commission a node
2. Configure node network to have OVS bridge on the primary interface
(MAAS-provided, static IP)
3. Deploy node with cloud-init for adding a user and additional configuration
(attached)
4. Node will start PXE-based deployment and will re-start the node to boot
from local disk, then it will fail with network configuration error
Expected behavior (what should have happened?):
Node deployment with OVS networking should be completed with no errors.
Actual behavior (what actually happened?):
Node deployment is not completed, cloud-init is not applied.
MAAS version and installation type (deb, snap):
# snap list maas
Name Version Rev Tracking Publisher Notes
maas 3.5.4-16349-g.4dbbed5f4 38907 3.5/stable canonical?
# apt list maas
Listing... Done
MAAS setup (HA, single node, multiple regions/racks):
single node
Host OS distro and version:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.2 LTS"
Additional context:
- cloud-init:
#cloud-config
system_info:
default_user:
name: depuser
passwd: "$6$jOKPZPHD9...0kn/"
lock_passwd: false
groups: [adm, audio, cdrom, dialout, dip, floppy, lxd, netdev, plugdev,
sudo, video]
sudo: ["ALL=(ALL) NOPASSWD:ALL"]
shell: /bin/bash
ssh_pwauth: True
package_upgrade: true
runcmd:
- apt-get update
- apt-get -y install nfs-common openvswitch-switch
- |
UPLINK_MAC=$(cat /sys/class/net/enp1s0/address)
ovs-vsctl set Bridge brenp1s0 other-config:hwaddr=$UPLINK_MAC
ovs-vsctl br-set-external-id brenp1s0 bridge-id brenp1s0 --
br-set-external-id brenp1s0 bridge-uplink enp1s0
Attached:
- screenshots of network interface configuration with ovs
- journalctl logs attached (machine name test-master-ovs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2103903/+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
