cloudbuilders/devstack — Issue #72: stack.sh failure doesn't bubble up to build_lxc.sh
Author: anotherjesse
Created: 2011-10-16 00:26:39+00:00
State: open

if jenkins is using build_lxc.sh

echo BRIDGE=br0 > localrc
echo CONTAINER=STACK >> localrc
echo CONTAINER_IP=192.168.2.50 >> localrc
echo CONTAINER_CIDR=192.168.2.50/24 >> localrc
echo CONTAINER_NETMASK=255.255.255.0 >> localrc
echo CONTAINER_GATEWAY=192.168.2.1 >> localrc
echo NAMESERVER=192.168.2.1 >> localrc
echo MYSQL_PASSWORD=password >> localrc
echo RABBIT_PASSWORD=password >> localrc
echo SERVICE_TOKEN=tokentoken >> localrc
echo ADMIN_PASSWORD=password >> localrc
cd tools
sudo ./build_lxc.sh

if stack.sh fails, such as:

+ sudo mount /mnt/sdb1
mount: Could not find any loop device. Maybe this kernel does not know
about the loop device? (If so, recompile or `modprobe loop'.)
++ failed
++ local r=2
++ set +o xtrace
stack.sh failed: full log in /opt/stack/devstack/stack.sh.474.log

All done! Time to start clicking.

Finished - Zip-a-dee Doo-dah!
ln -s builds/2011-10-15_17-10-27 /home/jesse/.jenkins/jobs/devstack-swift/builds/../lastSuccessful failed: -1
ln -s builds/2011-10-15_17-10-27 /home/jesse/.jenkins/jobs/devstack-swift/builds/../lastStable failed: -1
Finished: SUCCESS

build_lxc.sh thinks everything is still a-ok