From what the logs show it looks like nova-compute goes in some sort of loop where it keeps getting network info: See nova-cpu and nova-cond logs:
http://logs.openstack.org/03/56303/2/check/check-tempest-devstack-vm-neutron-pg/23f03ba/logs/screen-n-cpu.txt.gz http://logs.openstack.org/03/56303/2/check/check-tempest-devstack-vm-neutron-pg/23f03ba/logs/screen-n-cond.txt.gz
and search for request:
req-8c5d20d1-5191-4683-8fb8-25570e72bf97
Whether that's induced by a Neutron failure remains to be seen. I'll keep digging.
From what the logs show it looks like nova-compute goes in some sort of loop where it keeps getting network info: See nova-cpu and nova-cond logs:
http:// logs.openstack. org/03/ 56303/2/ check/check- tempest- devstack- vm-neutron- pg/23f03ba/ logs/screen- n-cpu.txt. gz logs.openstack. org/03/ 56303/2/ check/check- tempest- devstack- vm-neutron- pg/23f03ba/ logs/screen- n-cond. txt.gz
http://
and search for request:
req-8c5d20d1- 5191-4683- 8fb8-25570e72bf 97
Whether that's induced by a Neutron failure remains to be seen. I'll keep digging.