On Thu, Oct 26, 2017 at 03:56:24PM -0000, Scott Moser wrote:
> You can grep through, the onlyi real function taht uses it is
> 'rand_str'. and i'm not sure really why that would be called at the
> point that you're seeing the slow down.
> I think it more valuable for you to figure out why your environment is
> causing this issue and fixing that rather than fixing cloud-init (and
> subsequently all users of entropy).
We know that Ubuntu Cloud images must function in entropy-poor environments;
that's why we ship pollinate by default. If this particular delay is due to
cloud-init (or something it invoked) consuming entropy in early boot and
blocking, that is a problem, even if we do resolve the lack of an in-kernel
entropy source for this particular image and use case.
> Also, information about how you've come across this bug would be good.
I don't think I have ever seen the boot delay Mathieu is reporting, even
using the same image. So we're dependent on him to provide a reproducer.
On Thu, Oct 26, 2017 at 03:56:24PM -0000, Scott Moser wrote:
> You can grep through, the onlyi real function taht uses it is
> 'rand_str'. and i'm not sure really why that would be called at the
> point that you're seeing the slow down.
> I think it more valuable for you to figure out why your environment is
> causing this issue and fixing that rather than fixing cloud-init (and
> subsequently all users of entropy).
We know that Ubuntu Cloud images must function in entropy-poor environments;
that's why we ship pollinate by default. If this particular delay is due to
cloud-init (or something it invoked) consuming entropy in early boot and
blocking, that is a problem, even if we do resolve the lack of an in-kernel
entropy source for this particular image and use case.
> Also, information about how you've come across this bug would be good.
I don't think I have ever seen the boot delay Mathieu is reporting, even
using the same image. So we're dependent on him to provide a reproducer.