Public bug reported:

If Python 3.5 starts before the kernel has initialised its RNG, it will
hang[0] until there is sufficient entropy for it to randomise dictionary
keys.

As cloud-init uses Python 3.5, this means that cloud-init will hang
until this happens (meaning that the instance won't be properly
initialised).

I have seen this cause a hang of up to 7 minutes on an OpenStack cloud.


[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822431

** Affects: cloud-images
     Importance: Undecided
         Status: New

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: python3.5 (Debian)
     Importance: Unknown
         Status: Unknown

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Bug watch added: Debian Bug tracker #822431
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822431

** Also affects: python3.5 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822431
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584147

Title:
  cloud-init hangs on boot as Python waits for sufficient randomness to
  start

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

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

Reply via email to