destack has a silent failure which causes tempest tests to fail

[Sukhdev Kapur]

When I run devstack (stack.sh), I see that following failure is logged:

2014-08-22 14:50:24.712 | ++ euca-bundle-image -r x86_64 -i /home/arastra/devstack/files/images/cirros-0.3.2-x86_64-uec/cirros-0.3.2-x86_64-vmlinuz --kernel true -d /home/arastra/devstack/files/images/s3-materials/cirros-0.3.2
2014-08-22 14:50:24.953 | euca-bundle-image: error: No such file or directory: /home/arastra/devstack/files/images/s3-materials/cirros-0.3.2

On IRC, upon chat with clarkb, he pointed that other places are logging the same issue - he provided the following link -
http://logs.openstack.org/24/115824/2/check/check-tempest-dsvm-full/837b411/logs/devstacklog.txt.gz#_2014-08-21_01_11_18_408

stack.sh does not fail because of this and continues. However, later when I try to run the scenario tests, the VM's do not correctly boot as they do not have correct image.

Upon further investigation, I noticed that the path used in the init_tempest() at line https://github.com/openstack-dev/devstack/blob/33dc8699e6b774cc39b39e0dba97be41bbb47abe/lib/tempest#L336 and the path set at line
https://github.com/openstack-dev/devstack/blob/33dc8699e6b774cc39b39e0dba97be41bbb47abe/lib/tempest#L62
seem to be different, and, hence, may be the cause of the problem.

All of this seems to go undetected until later the tempest tests (e.g. test_network_basic_ops()) try to use the image to launch a VM. The VM does not boot because of the image issue.

Hope this is good enough of an explanation of the issue.

[Ian Wienand (iwienand)]

I think you're seeing the results of [1]. that should merge soon

[1] https://review.openstack.org/#/c/113767/

[Sean Dague (sdague)]

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.