communication from a vm without floating-ip to another vm with floating-ip
doesn't work in dvr-multinode setup. [1]
see the result of tempest test cases. [2]
the same test is working well for midonet [3] and linuxbridge. [4]
[1] gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv
[2] https://review.openstack.org/#/c/424959/
[3] gate-tempest-dsvm-networking-midonet-ml2-ubuntu-xenial
[4] gate-tempest-dsvm-neutron-scenario-linuxbridge-ubuntu-xenial-nv
eg. http://logs.openstack.org/59/424959/6/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/071223e/
2017-06-02 03:07:48,518 347 INFO [tempest.lib.common.ssh] Creating ssh connection to '10.1.0.8:22' as 'ubuntu' with public key authentication
2017-06-02 03:07:48,518 347 INFO [tempest.lib.common.ssh] Creating ssh connection to '172.24.5.21:22' as 'ubuntu' with public key authentication
2017-06-02 03:07:48,712 347 INFO [paramiko.transport] Connected (version 2.0, client OpenSSH_7.2p2)
2017-06-02 03:07:48,911 347 INFO [paramiko.transport] Authentication (publickey) successful!
2017-06-02 03:07:48,925 347 INFO [tempest.lib.common.ssh] ssh connection to ubuntu@172.24.5.21 successfully created
2017-06-02 03:07:51,806 347 INFO [paramiko.transport] Connected (version 2.0, client OpenSSH_7.2p2)
2017-06-02 03:07:52,052 347 INFO [paramiko.transport] Authentication (publickey) successful!
2017-06-02 03:07:52,059 347 INFO [tempest.lib.common.ssh] ssh connection to ubuntu@10.1.0.8 successfully created
2017-06-02 03:07:55,854 347 WARNING [neutron.tests.tempest.scenario.base] Failed to ping IP: 172.24.5.23 via a ssh connection from: 10.1.0.8.
I'm wondering if this is related to bug 1695101 as that is a regression where the snat namespace is not being created properly, and could result in a VM without a FIP not being able to work properly. We should merge https:/