Open Stack

On Tue, Jul 08, 2014 at 02:50:40PM -0700, Joe Gordon wrote:
> > > But for right now, we should stop the bleeding, so that nova/libvirt
> > > isn't blocking everyone else from merging code.
> >
> > Agreed, we should merge the hack and treat the bug as release blocker
> > to be resolve prior to Juno GA.
> >
> 
> 
> How can we prevent libvirt issues like this from landing in trunk in the
> first place? If we don't figure out a way to prevent this from landing the
> first place I fear we will keep repeating this same pattern of failure.

Realistically I don't think there was much/any chance of avoiding this
problem. Despite many days of work trying to reproduce it by multiple
people, no one has managed even 1 single failure outside of the gate.
Even inside the gate it is hard to reproduce. I still have absolutely
no clue what is failing after days of investigation & debugging with
all the tricks I can think of, because as I say, it works perfectly
every time I try it, except in the gate where it is impossible to
debug it.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|