On Thu, Jan 19, 2017 at 4:48 PM, Adam Williamson
On Wed, 2017-01-18 at 09:28 -0500, Matthew Miller wrote:
> > On Wed, Jan 18, 2017 at 10:05:41AM +0530, Kushal Das wrote:
> > > 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?
> > I think we need to find out what the issue is and fix it.
> +1. I wonder if this is actually a widespread problem that we've just
> noticed in this way.
Someone was actually asking me yesterday about a bug where they
couldn't ssh into a freshly-booted system for several minutes. Wonder
if it might possibly be the same thing...
That sounds like some form of DNS failure and a lookup waiting to
timeout before it falls back