cloud-init-19.2-36-g059d049c-0ubuntu1~18.04.1 breaks bond/bridge configuration in MAAS

Bug #1846661 reported by Lee Trager on 2019-10-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Undecided
Unassigned

Bug Description

cloud-init was recently updated to 19.2-36-g059d049c-0ubuntu1~18.04.1 this update has broken bond and bridge configuration in MAAS. static and DHCP configuration do not seem to be effected. Machines configured with bonds and bridges will sometimes be able to contact MAAS to finalize the deployment however I have been unable to connect to any machine post deployment.

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 653, in status_wrapper
    ret = functor(name, args)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 362, in main_init
    init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL))
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 697, in apply_network_config
    net.wait_for_physdevs(netcfg)
  File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 499, in wait_for_physdevs
    raise RuntimeError(msg)
RuntimeError: Not all expected physical devices present: {'52:54:00:1a:cb:cb', '52:54:00:50:76:1c'}

Lee Trager (ltrager) wrote :
Lee Trager (ltrager) wrote :
Lee Trager (ltrager) wrote :
Lee Trager (ltrager) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers