Comment 15 for bug 1273386

We have now rolled the new kernel in the nodes used for the experimental jobs.
This did not help anyway. In the logs the 'waiting for thing to become ACTIVE' failures are still present, but there is a different failure mode (no kernel crash).

However, openvswitch is just not working [1] and the vm boot times out after 120 seconds as it is unable to reach vswitchd [2].
I reckon we should install the saucy version of ovs (1.10) [3]

On another note, there still is something interesting happening during nbd mount for key injection, as it seems no suitable nbd device is found [4]. I am not sure this is desired behaviour, but at least it won't hang VM boot.

Finally, the new kernel is also unable to resolve the hostname. This might not be a problem but puts error-level statements in pretty much all log files.

[1] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-q-agt.txt.gz?level=WARNING#_2014-01-29_15_46_25_922
[2] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-n-cpu.txt.gz?level=WARNING#_2014-01-29_15_48_34_969
[3] http://packages.ubuntu.com/saucy/openvswitch-switch
[4] http://logs.openstack.org/64/61964/21/experimental/experimental-tempest-dsvm-neutron-isolated/39133b0/logs/screen-n-cpu.txt.gz?level=WARNING#_2014-01-29_15_46_13_781