yahoo-eng-team team mailing list archive

[Dan Watkins <daniel.watkins@xxxxxxxxxxxxx>]

** 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
       Status: New

** Also affects: cloud-init (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Disco)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Bionic)
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Disco)
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

-- 
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:
  In Progress
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Bionic:
  In Progress
Status in cloud-init source package in Disco:
  In Progress
Status in cloud-init source package in Eoan:
  In Progress

Bug description:
  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