yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

I honestly don't see any evidence of some broken behaviour in Nova if,
particularly, other instances with other guest image using cloud-init
can boot correctly.

Please provide us some logs or better trace of a potential Nova problem
in order for us to classify the potential root cause and a possible
solution, but in the meantime I'll have to close this bug from the Nova
point of view. You can reopen this bug by changing its status to New.

** Changed in: nova
       Status: New => Invalid

** Tags added: metadata

-- 
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/1851552

Title:
  since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is
  unable to boot up on openstack instance

Status in cloud-init:
  Invalid
Status in networking-calico:
  New
Status in OpenStack Compute (nova):
  Invalid
Status in OpenStack Community Project:
  New
Status in qemu-kvm:
  New
Status in cloud-init package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  New

Bug description:
  Openstack Queens release which is running on ubuntu 18 LTS Controller and Compute.
  Tried to boot up the instance via horizon dashboard without success.
  Nova flow works perfect.
  When access to console I discovered that the boot process stuck in the middle.
  [[0;1;31m TIME [0m] Timed out waiting for device dev-vdb.device.
  [[0;1;33mDEPEND[0m] Dependency failed for /mnt.
  [[0;1;33mDEPEND[0m] Dependency failed for File System Check on /dev/vdb.
  It receives IP but looks like not get configured at time.
  since ubuntu 18 there is netplan feature managing the network interfaces
  please advise.

  more details as follow:
  https://bugs.launchpad.net/networking-calico/+bug/1851548

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