ppc64el / arm64 - issues with cloud-init setting default route
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Incomplete
|
Undecided
|
Unassigned | ||
Netplan |
Invalid
|
Undecided
|
Unassigned | ||
cloud-init |
Expired
|
Undecided
|
Unassigned |
Bug Description
This is quite possibly a cloud-init bug.
MAAS version: 2.6.2 (7841-ga10625be
This problem manifests whether to machine is deployed with juju or manually via the MAAS ui.
This problem is intermittent and I have only seen it affecting arm64 and ppc64el machines (out of 29 machines in total) - all of these machines have 2 interfaces connected to the same fabric in the same subnet - one is set to unassigned to be used as a bridge port / data port for openstack deployments, the other is set to auto assign.
This problem occurs with bionic, eoan and focal deployments.
I have recommissioned the affected machines numerous times, including attempts to update firmware.
Symptoms: when the machine comes up after it is deployed there is no default gateway, e.g.
ubuntu@
10.245.168.0/21 dev enP5p9s0f0 proto kernel scope link src 10.245.168.63
The rsyslog on the MAAS server shows that the machine is being configured correctly:
https:/
But the cloud-init log on the machine does not have a default gateway:
https:/
Additional info:
Something I have observed is that the machines where this problem occurs seem to sometimes have the 'unassigned' interface as the PXE interface, and sometimes the auto-assigned interface. I've tried to force this but the PXE interface moves around by itself.
Changed in cloud-init: | |
status: | Incomplete → New |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
tags: | added: bug-council |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
MAAS passes network config to cloud-init which writes it to /etc/netplan/ 50-cloud- init.yaml and uses netplan to actually apply it once the system has booted. netplan is non-blocking and I've seen cloud-init output incomplete network information even though netplan hasn't finished applying network config.
* Have you verified the network configuration isn't correct by logging onto the effecting system and checking routes with `route`?
* When you logged in is the netplan process running?
* Can you post full Curtin output? You can get this with
maas $PROFILE machine get-curtin-config $SYSTEM_ID