On 09/01/17, Matthew Miller wrote: > On Mon, Jan 09, 2017 at 10:16:51AM -0500, Dusty Mabe wrote: > > > I finally managed to reproduce the error on a local box. After doing the > > > reboot like in [1], the tool can not ssh back into the vm. When I tried > > > the same on debug mode on, it still fails for some time, and then > > > randomly allows to ssh again. > > > I could not reproduce this using the same images over our OpenStack > > > cloud. Any tips will be helpful to find the cause. > > > > > Can we get together and debug this? > > Is this a key-generation entropy problem? Finally managed to isolate the issue. If we boot the image with only one CPU, the error comes up. If we boot with 2 or more CPU(s), no issues at all. Now the question is if we should make local testing on Autocloud with 2 CPU(s) or get this issue fixed somehow? Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
