** 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 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.

-- 
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
  physical devices present ..."  during bionic image deployment from
  MAAS

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to