[Group.of.nepali.translators] [Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

This bug is believed to be fixed in cloud-init in version 19.2-55. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a

[Group.of.nepali.translators] [Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

This bug was fixed in the package cloud-init - 19.2-36-g059d049c- 0ubuntu2~19.04.1 --- cloud-init (19.2-36-g059d049c-0ubuntu2~19.04.1) disco; urgency=medium * cherry-pick a7d8d032: get_interfaces: don't exclude bridge and bond members (LP: #1846535) -- Daniel Watkins Fri,

[Group.of.nepali.translators] [Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

This bug was fixed in the package cloud-init - 19.2-36-g059d049c- 0ubuntu2~18.04.1 --- cloud-init (19.2-36-g059d049c-0ubuntu2~18.04.1) bionic; urgency=medium * cherry-pick a7d8d032: get_interfaces: don't exclude bridge and bond members (LP: #1846535) -- Daniel Watkins Fri,

[Group.of.nepali.translators] [Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

This bug was fixed in the package cloud-init - 19.2-36-g059d049c- 0ubuntu2 --- cloud-init (19.2-36-g059d049c-0ubuntu2) eoan; urgency=medium * cherry-pick a7d8d032: get_interfaces: don't exclude bridge and bond members (LP: #1846535) -- Daniel Watkins Fri, 04 Oct 2019