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 Controller Cloud/Region Version SLA Timestamp
Notes
controller foundations-maas maas_cloud 3.5.4 unsupported 13:13:21Z
upgrade available: 3.5.5
2) VM/baremetal machine 3 is added to the juju model from the maas
cloud.
3) netplan on machine 3 is manually "corrupted" by using strings instead
of int for spme config values and using openvswitch in vland section:
sudo cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
ens4:
addresses:
- 10.11.2.153/24
gateway4: 10.11.2.1
match:
macaddress: 52:54:00:b8:51:30
mtu: 1500
nameservers:
addresses:
- 10.11.2.12
- 10.11.2.11
- 10.11.2.10
search:
- pc1.canonical.com
- maas
set-name: ens4
bridges:
br-data:
macaddress: "52:54:00:b8:51:30"
mtu: 9000
interfaces:
- ens4
parameters:
forward-delay: "15"
stp: false
openvswitch: {}
vlans:
br-data.3213:
addresses:
- "10.150.41.15/24"
mtu: 9000
routes:
- metric: 0
to: "10.150.42.0/24"
via: "10.150.41.1"
- metric: 0
to: "10.150.43.0/24"
via: "10.150.41.1"
id: 3213
link: "br-data"
openvswitch: {}
version: 2
4) Add new machine as an lxd container on existing machine:
juju add-machine lxd:3
We see an error in lxd container creation:
3/lxd/1 down pending ubuntu@22.04 bridge
activation error: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `15` into int
line 37: field ope...
Logs: var/log/juju/machine-3.log
2024-12-17 13:21:51 WARNING juju.worker.lxdprovisioner provisioner_task.go:1395
machine 3/lxd/1 failed to start: failed to bridge devices: bridge activation
error: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `15` into int
line 37: field openvswitch not found in type netplan.VLAN
2024-12-17 13:21:51 WARNING juju.worker.lxdprovisioner provisioner_task.go:1433
failed to start machine 3/lxd/1 (failed to bridge devices: bridge activation
error: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `15` into int
line 37: field openvswitch not found in type netplan.VLAN), retrying in 10s
(1 more attempts)
2024-12-17 13:22:01 ERROR juju.worker.lxdprovisioner provisioner_task.go:1307
cannot start instance for machine "3/lxd/1": failed to bridge devices: bridge
activation error: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `15` into int
line 37: field openvswitch not found in type netplan.VLAN
5) Upgrade controller and agents to 3.5.5
juju upgrade-controller
juju-upgrade-model --agent-version=3.5.5
juju status -m controller
Model Controller Cloud/Region Version SLA Timestamp
Notes
controller foundations-maas maas_cloud 3.5.5 unsupported 13:48:37Z
upgraded on "2024-12-17T13:24:47Z"
juju add-machine lxd:3 --constraints spaces=oam-space
No errors reported and lxc container is successfully spin up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084444
Title:
juju can not parse new 50-cloud-init.yaml properly after netplan 0.107
under 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/2084444/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
