Comment 9 for bug 1590420

I've investigated this bug and found that test fails (time by time, not always!) when we run bunch of test, like:

rally --debug verify start --regex tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON
....
{0} tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_can_create_server_with_max_number_personality_files [92.704434s] ... ok
{0} tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_create_server_with_personality [21.695728s] ... FAILED
{0} tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_personality_files_exceed_limit [1.174876s] ... ok
{0} tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_rebuild_server_with_personality [54.739215s] ... ok

If run single test

rally --debug verify start --regex tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_create_server_with_personality

it will pass.

Note: it's Neutron DVR con
root@node-3:~# grep '^router_distributed' /etc/neutron/neutron.conf
router_distributed = True

So, I added breakpoint right after line 71
https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_server_personality.py#L71
ran tests and found that instance is running and I can connect to instance via IP in namespace, but floating IP is not available by icmp.
Also, from instance all networks (internet, router, controller) are available.

Details http://pastebin.com/FMMBa344