[openstack-dev] [qa] Can't interpret failure from XenServer CI

2014-02-23 Thread David Kranz
XenServer reported failure on https://review.openstack.org/#/c/73704. The pointer to the logs should look like a jenkins failure but does not in two ways. First, there is no console log, with a directory of other log files next to it. Second, the .gz log files are not set up to be downloaded

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

2014-02-23 Thread Bob Ball
Hi David, That's a very strange error - it basically means the node has been used for running a test already (both the first error in run_tests.log about the git repository also existing, and the more fatal error about vif 3 existing) I believe this was my fault - I should have purged all

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

2014-02-23 Thread David Kranz
On 02/23/2014 03:29 PM, Bob Ball wrote: Hi David, That's a very strange error - it basically means the node has been used for running a test already (both the first error in run_tests.log about the git repository also existing, and the more fatal error about vif 3 existing) I believe this

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

2014-02-23 Thread Bob Ball
I believe I've identified the bug - it seems to have occurred when restarting the Citrix CI system while the tests were in the process of being run, leading it to believe that they had not been invoked yet and therefore triggering the tests on that node a second time. I've implemented a fix -

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

2014-02-23 Thread Bob Ball
Agreed on both counts - I'd already updated the message to say that as well as supporting the standard recheck you can run citrix recheck to only trigger a recheck of XenServer and will try and fix the http headers tomorrow. Bob From: David Kranz