yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #62019
[Bug 1669930] [NEW] OpenStack Mitaka instance with nova-vmware (vsphere 6.0) hangs while booting at "... random: nonblocking pool is initialized"
Public bug reported:
I have seen it recreated consistently with the Xenial vmdk cloud image.
I also attempted to qemu-conver the QCOW2 version to vmdk and it hit
that. It seems to eventually time out.
With Trusty, I was able to see the instance booting with the vmdk I
created by converting the QCOW2 image to vmdk, but one of the instances
started hitting this hang consistently after previously booting without
any issue.
I then attempted to deploy another Trusty instance and it worked.
I have attached the screen shot.
** Affects: cloud-images
Importance: Undecided
Status: New
** Tags: oil
** Attachment added: "Screenshot from 2017-03-03 17-37-37.png"
https://bugs.launchpad.net/bugs/1669930/+attachment/4831009/+files/Screenshot%20from%202017-03-03%2017-37-37.png
** Project changed: cloud-init => cloud-images
--
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/1669930
Title:
OpenStack Mitaka instance with nova-vmware (vsphere 6.0) hangs while
booting at "... random: nonblocking pool is initialized"
Status in cloud-images:
New
Bug description:
I have seen it recreated consistently with the Xenial vmdk cloud
image. I also attempted to qemu-conver the QCOW2 version to vmdk and
it hit that. It seems to eventually time out.
With Trusty, I was able to see the instance booting with the vmdk I
created by converting the QCOW2 image to vmdk, but one of the
instances started hitting this hang consistently after previously
booting without any issue.
I then attempted to deploy another Trusty instance and it worked.
I have attached the screen shot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1669930/+subscriptions