Comment 4 for bug 1788403

Before the ssh fails after the resize revert, the floaging IP is down:

http://logs.openstack.org/98/591898/3/check/tempest-slow/c480e82/job-output.txt.gz#_2018-08-21_23_20_11_731057

2018-08-21 23:20:11.731057 | controller | 2018-08-21 23:17:58,661 9451 INFO [tempest.scenario.manager] FloatingIP: {u'router_id': u'188eb35a-1270-4536-a02a-92f9ec031c7a', u'description': u'', u'tags': [], u'status': u'DOWN', u'tenant_id': u'38bf4237efd54095959153ffc2227946', u'created_at': u'2018-08-21T23:17:10Z', u'updated_at': u'2018-08-21T23:17:10Z', u'floating_network_id': u'0fd1d892-0aa3-4c0c-818f-44f1c9a9b569', u'fixed_ip_address': u'10.1.0.9', u'port_details': {u'status': u'ACTIVE', u'name': u'', u'admin_state_up': True, u'network_id': u'6c9a79d8-b508-4a97-a15d-bf4acee8b4a8', u'device_owner': u'compute:nova', u'mac_address': u'fa:16:3e:2b:a9:39', u'device_id': u'015f755f-2779-4613-9b28-9bc377056fe2'}, u'floating_ip_address': u'172.24.5.13', u'revision_number': 0, u'project_id': u'38bf4237efd54095959153ffc2227946', u'id': u'ac394112-d245-461b-b660-00cab7c1b51a', u'port_id': u'b835ff51-0262-4237-ab52-7b08206bd099'} is at status: ACTIVE
2018-08-21 23:20:11.731352 | controller | 2018-08-21 23:17:58,661 9451 DEBUG [tempest.scenario.manager] checking network connections to IP 172.24.5.13 with user: cirros
2018-08-21 23:20:11.731802 | controller | 2018-08-21 23:17:58,662 9451 DEBUG [tempest.scenario.manager] TestNetworkAdvancedServerOps:test_server_connectivity_cold_migration_revert begins to ping 172.24.5.13 in 120 sec and the expected result is reachable
2018-08-21 23:20:11.732072 | controller | 2018-08-21 23:19:58,848 9451 DEBUG [tempest.lib.common.utils.test_utils] Call ping returns false in 120.000000 seconds
2018-08-21 23:20:11.732512 | controller | 2018-08-21 23:19:58,850 9451 DEBUG [tempest.scenario.manager] TestNetworkAdvancedServerOps:test_server_connectivity_cold_migration_revert finishes ping 172.24.5.13 in 120 sec and the ping result is unexpected

Formatted json:

{
   u'router_id':u'188eb35a-1270-4536-a02a-92f9ec031c7a',
   u'description':u'',
   u'tags':[

   ],
   u'status':u'DOWN',
   u'tenant_id':u'38bf4237efd54095959153ffc2227946',
   u'created_at': u'2018-08-21T23:17:10 Z',
   u'updated_at': u'2018-08-21T23:17:10 Z',
   u'floating_network_id':u'0fd1d892-0aa3-4c0c-818f-44f1c9a9b569',
   u'fixed_ip_address':u'10.1.0.9',
   u'port_details':{
      u'status':u'ACTIVE',
      u'name':u'',
      u'admin_state_up':True,
      u'network_id':u'6c9a79d8-b508-4a97-a15d-bf4acee8b4a8',
      u'device_owner': u'compute:nova',
      u'mac_address': u'fa:16:3e:2 b: a9:39 ', u' device_id':u'015f755f-2779-4613-9b28-9bc377056fe2'
   },
   u'floating_ip_address':u'172.24.5.13',
   u'revision_number':0,
   u'project_id':u'38bf4237efd54095959153ffc2227946',
   u'id':u'ac394112-d245-461b-b660-00cab7c1b51a',
   u'port_id':u'b835ff51-0262-4237-ab52-7b08206bd099'
}

I'm not sure why Tempest says, "is at status: ACTIVE" when the status is clearly DOWN. Maybe it's checking the port_details?