Comment 21 for bug 1851552

In Rocky release I’m not experiencing kind of issues. And make sure you use kvm and not qemu, cause qemu is limited on its performance and kvm just born to work with latest hardware :)

Best,
Vasili

Sent from iPhone

> On 14 Jan 2020, at 20:35, Dan Watkins <email address hidden> wrote:
>
> Hi Vasili,
>
>> From a cloud-init perspective, there isn't anything we can do so I'm
> going to move the upstream task to Invalid too. I'm afraid I don't
> really have any advice on how to proceed, as this appears to be a
> hypervisor or cloud issue.
>
>
> Dan
>
> ** Changed in: cloud-init
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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):
> New
> 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