The workaround for this issue is to manually replace bootaa64 and
grubaa64 files in Maas /car/snap/maas/common/Maas/image-
storage/bootloaders/UEFI/arm64 with files of previous version 2.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Tested juju 3.5.5 with new netplan formatting created by netplan 0.107.
The correction works and now juju does not complain about int -> str
formatting.
1) Original juju controller version 3.5.4
juju status -m controller
Model ControllerCloud/Region Version SLA Timestamp
** Description changed:
Ubuntu 22.04
netplan - 0.107.1-3ubuntu0.22.04.1
juju - 3.5.4
It looks like there is a regression with new netplan 0.107 version under
22.04. Now juju can not start lxd containers due to following error:
2024-10-12 09:10:24 ERROR juju.worker.lxdprovisioner
I tested PPA on Jammy 22.04 an can confirm netplan with SRIOV backports
works properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083008
Title:
Enabling HW offloading to Mellanox cards causing
Regarding "Linux bridges, by default, "auto-tune" the bridge MTU to
MIN(mtu) of all member ports. This is updated each time an interface is
added or removed (except with vlan aware mode, which uses MAX(mtu)
instead)".
Is it also applicable for openvswitch bridge created using netplan?
--
You rec
Hi MAAS team, I wanted to reopen this issue since I faced exactly the
same problem. I'm testing GIGABYTE servers R282-P92-00. There are 6
servers which can not boot Ubuntu Jammy 22.04 via PXE boot under MAAS
control. When PXE boot happens I see that IP address gets assigned and
server receives two
