Ubuntu host configure breaks undefined network configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kayobe |
Triaged
|
Medium
|
Unassigned |
Bug Description
When running an Ubuntu 20.04 VM in OpenStack, the network configuration is defined using system-networkd with:
/run/systemd/
/run/systemd/
If AUFN is run on this VM, the `seed hypervisor host configure` step will perform the following:
TASK [network-debian : Remove netplan.io packages]
changed: [seed-hypervisor]
TASK [network-debian : meta]
RUNNING HANDLER [network-debian : Find netplan systemd-networkd configuration]
ok: [seed-hypervisor]
RUNNING HANDLER [network-debian : Remove netplan systemd-networkd configuration]
changed: [seed-hypervisor] => (item=/
changed: [seed-hypervisor] => (item=/
Some network configuration is then applied in /etc/systemd/
/etc/systemd/
/etc/systemd/
/etc/systemd/
/etc/systemd/
/etc/systemd/
/etc/systemd/
Networking connectivity won't break right away but it will fail at the time of lease renewal (24 hours after last renewal?)
Changed in kayobe: | |
status: | Expired → New |
Changed in kayobe: | |
importance: | Undecided → Medium |
Changed in kayobe: | |
status: | New → Triaged |
seems strange, which version of the kayobe used? also please provide at least etc/kayobe/ seed-hypervisor .yml