VM live migration tests are flaky where they fail to live migrate in some randomly set timeouts(I am guessing based on some empirical data).
On top of that some tests have different timeouts.

The goal is to updated all these tests with one timeout, something higher like 60 or 90seconds. We have discussed that ML2/OVS is not as high priority so this will be ok. Also, we have never concluded or agreed what the "maximum threshod" should be. I think keeping these tests running is still valid, incase the timeout takes more than 1 minute, because it that scenario something really went wrong

Jobs where the test tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedServerOps.test_server_connectivity_live_migration is set to timeout of either 10s, 15s, 5s

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-all-unified-17.1_d-rhel-vhost-3cont_2comp-ipv4-vxlan-lvm/

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-all-unified-17.1_d-rhel-vhost-3cont_2comp-ipv4-vxlan-lvm/

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-network-neutron-17.1_director-rhel-virthost-3cont_2comp-ml2ovs-ipv6-all-gre-tempest/

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-network-neutron-17.1_director-rhel-virthost-3cont_2comp-ml2ovs-ipv6-all-vxlan-tempest/

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-network-neutron-17.1_director-rhel-virthost-3cont_2comp_1freeipa-ml2ovs-ipv4-vxlan-tempest-tlseverywhere/

https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/QE/view/OSP17.1/job/DFG-network-ffu-17.1-from-16.2-latest_cdn-3cont_3net_2comp_cfme-ipv4-ovn_vlan-provider-network/50/testReport/junit/tempest.scenario.test_network_advanced_server_ops/TestNetworkAdvancedServerOps/test_server_connectivity_live_migration_compute_id_03fd1562_faad_11e7_9ea0_fa163e65f5ce_network_slow_/