Re: [Wg-openstack] OpenStack XenProject CI loop update

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

Hello,

I did restarted the CI loop last week. It is about 70% success, so there
is still 30% of failure, mostly false.

There is one issue that I've notice that is often why a run fail, it is
something to do with attaching an extra volume.

For example, in
http://logs.openstack.xenproject.org/44/416444/20/check/dsvm-tempest-xen/fd978c7/

tempest.log (console.html):
> Details: volume add66099-b0b8-43fd-ad92-5dc5850f1ff9 failed to reach in-use 
> status (current available) within the required time (196 s).

libvirt/libxl-driver.log:
> libxl: debug: libxl_aoutils.c:88:xswait_timeout_callback: backend 
> /local/domain/0/backend/vbd/131/51744/state (hoping for state change to 2): 
> xswait timeout (path=/local/domain/0/backend/vbd/131/51744/state
> libxl: debug: libxl_event.c:867:devstate_callback: backend 
> /local/domain/0/backend/vbd/131/51744/state wanted state 2  timed out
> libxl: error: libxl_device.c:1006:device_backend_callback: unable to add 
> device with path /local/domain/0/backend/vbd/131/51744
> libxl: error: libxl.c:2014:device_addrm_aocomplete: unable to add vbd with id 
> 51744

I don't know what's wrong, and I'm not sure where to look next. Any idee?

Anyway, there some nice graph about the success rates here:
http://104.130.29.226/munin/XenProjectCI/XenProjectCI/index.html


-- 
Anthony PERARD

_______________________________________________
Wg-openstack mailing list
Wg-openstack@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-openstack