It looks like tempest doesn't test ssh connectivity most of the time, which explains how we are seeing "no address available" in syslog for successful multinode runs (http://logs.openstack.org/55/138255/17/check/check-tempest-dsvm-multinode-full/878eb11/logs/syslog.txt.gz).
We are not seeing "no address available" in single node runs, so maybe this is a general nova-net multihost or migration issue
It looks like tempest doesn't test ssh connectivity most of the time, which explains how we are seeing "no address available" in syslog for successful multinode runs (http:// logs.openstack. org/55/ 138255/ 17/check/ check-tempest- dsvm-multinode- full/878eb11/ logs/syslog. txt.gz).
We are not seeing "no address available" in single node runs, so maybe this is a general nova-net multihost or migration issue