New local provider changes land in trunk - quantal users beware

[Clint Byrum]

Excerpts from Jonathan Lange's message of 2012-10-08 11:16:11 -0700:
> On 6 October 2012 17:24, Clint Byrum <clint at ubuntu.com> wrote:
> ...
> > This change switches the local provider to use the Ubuntu Cloud Images
> > instead of building a minimal chroot with debootstrap. This brings the
> > local provider closer in line with the other providers. This also means
> > that you are more likely to have an up to date container on deploy.
> ...
> > We've also removed all upstart jobs from the local provider, so there
> > shouldn't be issues with the machine agent spinning out of control on
> > reboot. It also won't leave anything behind if you reboot other than
> > stale pid files in the data-dir.
> >
> 
> Both very cool! Thanks!
> 
> > Unfortunately, while testing this extensively, I ran into this kernel
> > bug in quantal quite a bit:
> >
> > https://bugs.launchpad.net/ubuntu/quantal/+source/linux/+bug/1021471
> >
> 
> Are you planning on holding off uploading to quantal until that bug is fixed?

I'm not, because we are so short on time, and because the fix for non-wl
users is basically done and should land in the final 12.10 kernel. As far
as I can tell, the new provider just makes the effect more pronounced,
it still happens sometimes with the old one, though its not clear why
the new provider makes it more common. My guess is that libvirt does
something slightly different with the bridge that makes the route cache
race less likely. Also, the local provider in quantal is pretty messed
up anyway, so this is a net win.