[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

[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 is fixed in Ubuntu and as such I am unsubscribing field-critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected

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

Hey Dan, see https://bugs.launchpad.net/cloud-init/+bug/1847583 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected

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

On Wed, Oct 09, 2019 at 05:18:27PM -, Richard Maynard wrote: > I was able to capture the logs by making a snapshot of the volume and > mounting it to a different host, however with the previous version of > cloud-init it had the same problem, sorry for the false note but it > looks like this

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

I was able to capture the logs by making a snapshot of the volume and mounting it to a different host, however with the previous version of cloud-init it had the same problem, sorry for the false note but it looks like this issue is not related to the upgrade. -- You received this bug

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

Thanks! I'll work to capture logs and reproduce. We worked around for now by using apt to hold the package back (we use an older base image from july that then does an apt get update all while building our image). -- You received this bug notification because you are a member of Ubuntu Bugs,

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

Hi Richard, Alexander, Richard: We've published new daily images to AWS containing the newer version of cloud-init. Can you try to reproduce using the most recent daily image (which is ami-0802dbc378772aca8 in us-west-2), please? If you can still reproduce, then please file a new bug (because

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

Hi Richard and Alexander, Dan Watkins (driving the recent upload) will be around any minute and take a look. Until then if you both could try to get to a failing instance (or its disk) somehow and get the log [1] which usually is at /var/log/cloud-init-output.log that would be great. I know

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

the issue Richard describes also applies to GCP and Azure instances. The netplan configuration is not re-generated if the mac address changes and is hardcoded with a `match: { mac: address}`. So if a image is created the newly spawned instances do not have network enabled on their main interface.

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

Using 19.2-36-g059d049c-0ubuntu1~18.04.1 any of our new AWS instances can not get networking. A standard package update AMI build resulted in moving from 19.2.24 to 19.2.36 and now our instances come up inaccessible. Our cloudconfig does not make any adjustments to the networking. The specific

[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~16.04.1 --- cloud-init (19.2-36-g059d049c-0ubuntu2~16.04.1) xenial; urgency=medium * cherry-pick a7d8d032: get_interfaces: don't exclude bridge and bond members (LP: #1846535) -- Daniel Watkins Fri,

[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,

[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,

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

** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with

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

That's correct, that was done to work around the cloud-init issue while we land the fix in the archive. (That specific change was tracked in bug 1846845, but that's in a private project so odds are people won't be able to view it.) -- You received this bug notification because you are a member

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

It looks like images.maas.io has an older image with cloud-init 19.2-24 -ge7881d5c-0ubuntu1~18.04.1 (the version before the regression was introduced) as 20191004 (the latest as of right now). $ curl -s https://images.maas.io/ephemeral-v3/daily/bionic/amd64/20191003/squashfs.manifest | grep -w

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

I manually tested the new cloud-init using the MAAS CI as we don't have automated tests for bonds or bridges. Xenial, Bionic, and Disco can all commissioning and deploy fine using static IPs, bonds, and bridges. -- You received this bug notification because you are a member of Ubuntu Bugs, which

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

Oracle SRU verification logs ** Attachment added: "oracle-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/cloud-init/+bug/1846535/+attachment/5294454/+files/oracle-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

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

Attach file ec2-sru-19.2.36.ubuntu2.txt. ** Attachment added: "ec2-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294457/+files/ec2-sru-19.2.36.ubuntu2.txt ** Description changed: [Impact] Any instances launched with bridges or bonds in their network

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

Attach file nocloud-lxd-sru-19.2.36.ubuntu2.txt. ** Attachment added: "nocloud-lxd-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294458/+files/nocloud-lxd-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs,

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

Attach file azure-sru-19.2.36.ubuntu2.txt. ** Attachment added: "azure-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294460/+files/azure-sru-19.2.36.ubuntu2.txt ** Description changed: [Impact] Any instances launched with bridges or bonds in their

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

gce sru verification logs ** Attachment added: "gce-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/cloud-init/+bug/1846535/+attachment/5294455/+files/gce-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

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

Attach file openstack-sru-19.2.36.ubuntu2.txt. ** Attachment added: "openstack-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294456/+files/openstack-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which

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

Attach file nocloud-kvm-sru-19.2.36.ubuntu2.txt. ** Attachment added: "nocloud-kvm-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294459/+files/nocloud-kvm-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs,

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

I have also successfully verified the bionic fix on MAAS. Enabling the *-proposed repo via curtin_userdata pulled the latest cloud-init package fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

@darmadoo: The cloud-init package is baked into the cloud images that MAAS uses to deploy instances. You have to wait for the next cloud image that will contain this fixed cloud-init, or you can use the workaround in my comment #16 to use a previous image in the meantime. -- You received this

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

How would I make sure that MAAS pulls the latest package of cloud-init? running 'apt policy cloud-init' shows that I do not have cloud-init installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

I successfully verified the bionic fix on MAAS. Here's what I did: 1. deployed a machine with a bridge via maas 2. machine went to deployed mode, couldn't ssh in 3. switched to rescue mode, ssh'd in 4. mounted /, captured cloud-init-output.log with error: http://paste.ubuntu.com/p/Gg53xf9wtZ/ 5.

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

** Description changed: [Impact] Any instances launched with bridges or bonds in their network configuration will fail to bring up networking. [Test Case] # Juju bootstrap on maas of a machine sets up a network bridge that triggers a failure in cloud-init init stage. # This

[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

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

Hello Nikolay, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/19.2-36 -g059d049c-0ubuntu2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing

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

** Description changed: [Impact] Any instances launched with bridges or bonds in their network configuration will fail to bring up networking. [Test Case] - # Juju bootstrap on maas of a machine sets up a network bridge that triggers a failure in cloud-init init stage. + # Juju

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

As an FYI, my workaround for this is to grab the squasfh file from https://images.maas.io/ephemeral-v3/daily/bionic/amd64/20190930/ and copy it over the file /var/lib/maas/boot- resources/current/ubuntu/amd64/ga-18.04/bionic/daily/squashfs on my MAAS nodes (assuming you deploy Ubuntu 18.04 with

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

Hello Nikolay, or anyone else affected, Accepted cloud-init into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/19.2-36 -g059d049c-0ubuntu2~19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this

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

** Description changed: [Impact] Any instances launched with bridges or bonds in their network configuration will fail to bring up networking. [Test Case] + # Juju bootstrap on maas of a machine sets up a network bridge that triggers a failure in cloud-init init stage. + # This

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

** Description changed: + [Impact] + + Any instances launched with bridges or bonds in their network + configuration will fail to bring up networking. + + [Test Case] + + + [Regression Potential] + + The change being SRU'd adds more conditions to an existing conditional. + There is potential

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

** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373660 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36

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

** Also affects: cloud-init (Ubuntu Eoan) Importance: Critical Assignee: Dan Watkins (daniel-thewatkins) Status: In Progress ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Disco) Importance: Undecided

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

** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373655 ** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373656 ** Merge proposal linked:

[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 fixed with commit a7d8d032 to cloud-init on branch master. To view that commit see the following URL: https://git.launchpad.net/cloud-init/commit/?id=a7d8d032 ** Changed in: cloud-init Status: In Progress => Fix Committed -- You received this bug notification because you are

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

** Changed in: cloud-init (Ubuntu) Status: Confirmed => In Progress ** Changed in: cloud-init Status: New => In Progress ** Changed in: cloud-init Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) ** Changed in: cloud-init Importance: Undecided => Critical **

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

** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/373649 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title:

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

Bumped up the importance due to more reports in production env hitting this problem (apparently, not fully confirmed). ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Critical ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs,

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

** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all