Re: [Wg-openstack] OpenStack WG Meeting, April 5 2017

[Jim Fehlig <jfehlig@xxxxxxxx>]

On 04/05/2017 10:29 AM, Lars Kurth wrote:
> 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
Doesn't that mean that the frontend never attempted to initialize the vbd? Does 
this test always fail?
Regards,
Jim


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