On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: > This patch is coming through the gate this morning - > https://review.openstack.org/#/c/71996/ > > The point being to actually make devstack stop when it hits an error, > instead of only once these compound to the point where there is no > moving forward and some service call fails. This should *dramatically* > improve the experience of figuring out a failure in the gate, because > where it fails should be the issue. (It also made us figure out some > wonkiness with stdout buffering, that was making debug difficult). > > This works on all the content that devstack gates against. However, > there are a ton of other paths in devstack, including vendor plugins, > which I'm sure aren't clean enough to run under -o errexit. So if all of > a sudden things start failing, this may be why. Fortunately you'll be > pointed at the exact point of the fail.
This is awesome! It just helped me solve the problem I've been having for the past 2 days with devstack on one of my machines. I was hitting a problem where I'd set DEST and DATA_DIR but not set SERVICE_DIR in local.conf, resulting in mysterious failures later on since $SERVICE_DIR had not been created properly. https://bugs.launchpad.net/devstack/+bug/1285720 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 :| _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
