I probably have one more hint on Neutron failures.
When neutron isolated jobs fail, there is sometimes an error in adding a VIF. This error is somewhat hidden at least in the logs [1]
As a result, the VIF is not wired and SSH connection fails even if the floating IP is correctly wired.
The fault lies in regex parsing of ovs-vsctl find Interface, which expects the ofport to be always populated - the ofport is instead asynchronously set by vswitchd. instead of returning an integer, ovs-vsctl find Interface returns '[]' for ofport thus causing the parsing regex search to fail.
This has been seen in 3 out of 3 failure logs analysed ([1], [2], and [3])
A possible solution would be to make the regex more robust; however it is paramount to find a reliable way to deal with ports for which ofport has not yet been set.
I probably have one more hint on Neutron failures.
When neutron isolated jobs fail, there is sometimes an error in adding a VIF. This error is somewhat hidden at least in the logs [1]
As a result, the VIF is not wired and SSH connection fails even if the floating IP is correctly wired.
The fault lies in regex parsing of ovs-vsctl find Interface, which expects the ofport to be always populated - the ofport is instead asynchronously set by vswitchd. instead of returning an integer, ovs-vsctl find Interface returns '[]' for ofport thus causing the parsing regex search to fail.
This has been seen in 3 out of 3 failure logs analysed ([1], [2], and [3])
A possible solution would be to make the regex more robust; however it is paramount to find a reliable way to deal with ports for which ofport has not yet been set.
[1] http:// logs.openstack. org/59/ 53459/4/ experimental/ check-tempest- dsvm-neutron- isolated/ e0aefb5/ logs/screen- q-agt.txt. gz#_2014- 01-06_22_ 51_40_376 logs.openstack. org/39/ 64139/6/ check/check- tempest- dsvm-neutron- isolated/ 2f967f8/ console. html logs.openstack. org/17/ 57517/7/ check/check- tempest- dsvm-neutron- isolated/ 11505f4/ console. html
[2] http://
[3] http://