yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1846535@xxxxxxxxxxxxxxxxxx>]

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 <oddbloke@xxxxxxxxxx>  Fri, 04 Oct 2019 11:42:12
-0400

** Changed in: cloud-init (Ubuntu Eoan)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1846535

Title:
  cloud-init 19.2.36 fails with python exception "Not all expected
  physical devices present ..."  during bionic image deployment from
  MAAS

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  Fix Committed
Status in cloud-init source package in Eoan:
  Fix Released

Bug description:
  [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 results in a maas machine deployment failure and the machine gets released

  Procedure:
  1. juju bootrap mymaas --no-gui
  2. After bootstrap failure and machine is powered off click on the failed/released node in the MAAS UI
  3. Click Rescue Mode from the 'Take Action' drop down in the MAAS UI
  4. Grab the IP from the interfaces tab
  5. ssh ubuntu@<theRescueMachineIP> -- cloud-init status --long
  # Expect failure message
  6. Click Exit Rescue Mode on the node in MAAS UI.

  7. ssh to the maas server add the following lines to
  /etc/maas/preseeds/curtin_userdata to test official *-proposed
  packages:

  system_upgrade: {enabled: True}
  apt:
    sources:
      proposed.list:
         source: deb $MIRROR $RELEASE-proposed main universe   # upstream -proposed

  8. Repeat step 1 and expect bootstrap success
  # expect to see MAASDatasource from bootstrapped machine and no errors
  9. juju ssh 0 -- cloud-init status --long


  Also, this test case touches Azure cloud support for accelerated networking.
  We will be performing our manual SRU test case runs on Azure, OpenStack and Ec2 and attaching logs to confirm that this doesn't regress other clouds.

  * TODO Azure test template: https://github.com/cloud-init/ubuntu-sru/blob/master/sru-templates/manual/azure-sru
  * TODO Ec2 test template: https://github.com/cloud-init/ubuntu-sru/blob/master/sru-templates/manual/ec2-sru
  * TODO OpenStack test template: https://github.com/cloud-init/ubuntu-sru/blob/master/sru-templates/manual/openstack-sru

  [Regression Potential]

  The change being SRU'd adds more conditions to an existing
  conditional.  There is potential to regress the cases that the
  existing conditional was introduced to cover, so we will be testing
  those specifically.  Other than that, there was some minor refactoring
  of the existing conditional statement (which did not change the logic
  it checks), which could cause issues for Oracle netfailover
  interfaces.  We will also specifically test on Oracle.

  [Original Report]

  Symptoms
  ========

  After deployment of Ubuntu Bionic image on MAAS provider (deploying to
  a bare metal server) juju cannot access any deployed machine due to
  missing SSH keys and machines are stuck in pending state:

  $ juju ssh 0
  ERROR retrieving SSH host keys for "0": keys not found

  $ juju machines
  Machine  State    DNS            Inst id          Series  AZ   Message
  0        pending  172.20.10.125  block-3          bionic  AZ3  Deployed
  1        pending  172.20.10.124  block-2          bionic  AZ2  Deployed
  2        pending  172.20.10.126  block-1          bionic  AZ1  Deployed
  3        pending  172.20.10.127  object-2         bionic  AZ1  Deployed
  4        pending  172.20.10.128  object-1         bionic  AZ2  Deployed
  5        pending  172.20.10.129  object-3         bionic  AZ3  Deployed

  It worth mentioning that pods can be successfully deployed with MAAS,
  only bare metal deployment fails.

  We checked different bionic images: cloud-init 19.2.24 works, and
  cloud-init 19.2.36 doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions