Here are the state changes I'm seeing in that failure log while n-cpu is waiting for the network-vif-plugged event and after it's plugged the vif on the host:
Aug 20 12:52:06.006477 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: DEBUG nova.virt.driver [-] Emitting event <LifecycleEvent: 1534769526.01, 9797a641-8925-4f74-abbf-c6111d47f91d => Started> {{(pid=27062) emit_event /opt/stack/nova/nova/virt/driver.py:1545}}
Aug 20 12:52:06.006973 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: INFO nova.compute.manager [-] [instance: 9797a641-8925-4f74-abbf-c6111d47f91d] VM Started (Lifecycle Event)
--
Aug 20 12:52:06.065415 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: DEBUG nova.virt.driver [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] Emitting event <LifecycleEvent: 1534769526.01, 9797a641-8925-4f74-abbf-c6111d47f91d => Paused> {{(pid=27062) emit_event /opt/stack/nova/nova/virt/driver.py:1545}}
Aug 20 12:52:06.065642 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: INFO nova.compute.manager [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] [instance: 9797a641-8925-4f74-abbf-c6111d47f91d] VM Paused (Lifecycle Event)
--
Aug 20 12:52:07.636565 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: DEBUG nova.virt.driver [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] Emitting event <LifecycleEvent: 1534769527.63, 9797a641-8925-4f74-abbf-c6111d47f91d => Resumed> {{(pid=27062) emit_event /opt/stack/nova/nova/virt/driver.py:1545}}
Aug 20 12:52:07.636911 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: INFO nova.compute.manager [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] [instance: 9797a641-8925-4f74-abbf-c6111d47f91d] VM Resumed (Lifecycle Event)
--
Aug 20 12:52:07.680184 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: DEBUG nova.virt.driver [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] Emitting event <LifecycleEvent: 1534769527.64, 9797a641-8925-4f74-abbf-c6111d47f91d => Resumed> {{(pid=27062) emit_event /opt/stack/nova/nova/virt/driver.py:1545}}
Aug 20 12:52:07.680790 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: INFO nova.compute.manager [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] [instance: 9797a641-8925-4f74-abbf-c6111d47f91d] VM Resumed (Lifecycle Event)
--
Aug 20 12:52:07.721266 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: DEBUG nova.virt.driver [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] Emitting event <LifecycleEvent: 1534769527.64, 9797a641-8925-4f74-abbf-c6111d47f91d => Paused> {{(pid=27062) emit_event /opt/stack/nova/nova/virt/driver.py:1545}}
Aug 20 12:52:07.721592 ubuntu-xenial-ovh-gra1-0001411231 nova-compute[27062]: INFO nova.compute.manager [None req-27237dca-57e7-488d-aa47-f8f53ad60fc9 None None] [instance: 9797a641-8925-4f74-abbf-c6111d47f91d] VM Paused (Lifecycle Event)
And then that's it. So it looks like we go from resumed (running) back to paused in the guest and then never get back to running.
Here are the state changes I'm seeing in that failure log while n-cpu is waiting for the network-vif-plugged event and after it's plugged the vif on the host:
Aug 20 12:52:06.006477 ubuntu- xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: DEBUG nova.virt.driver [-] Emitting event <LifecycleEvent: 1534769526.01, 9797a641- 8925-4f74- abbf-c6111d47f9 1d => Started> {{(pid=27062) emit_event /opt/stack/ nova/nova/ virt/driver. py:1545} } xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: INFO nova.compute. manager [-] [instance: 9797a641- 8925-4f74- abbf-c6111d47f9 1d] VM Started (Lifecycle Event)
Aug 20 12:52:06.006973 ubuntu-
--
Aug 20 12:52:06.065415 ubuntu- xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: DEBUG nova.virt.driver [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] Emitting event <LifecycleEvent: 1534769526.01, 9797a641- 8925-4f74- abbf-c6111d47f9 1d => Paused> {{(pid=27062) emit_event /opt/stack/ nova/nova/ virt/driver. py:1545} } xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: INFO nova.compute. manager [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] [instance: 9797a641- 8925-4f74- abbf-c6111d47f9 1d] VM Paused (Lifecycle Event)
Aug 20 12:52:06.065642 ubuntu-
--
Aug 20 12:52:07.636565 ubuntu- xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: DEBUG nova.virt.driver [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] Emitting event <LifecycleEvent: 1534769527.63, 9797a641- 8925-4f74- abbf-c6111d47f9 1d => Resumed> {{(pid=27062) emit_event /opt/stack/ nova/nova/ virt/driver. py:1545} } xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: INFO nova.compute. manager [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] [instance: 9797a641- 8925-4f74- abbf-c6111d47f9 1d] VM Resumed (Lifecycle Event)
Aug 20 12:52:07.636911 ubuntu-
--
Aug 20 12:52:07.680184 ubuntu- xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: DEBUG nova.virt.driver [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] Emitting event <LifecycleEvent: 1534769527.64, 9797a641- 8925-4f74- abbf-c6111d47f9 1d => Resumed> {{(pid=27062) emit_event /opt/stack/ nova/nova/ virt/driver. py:1545} } xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: INFO nova.compute. manager [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] [instance: 9797a641- 8925-4f74- abbf-c6111d47f9 1d] VM Resumed (Lifecycle Event)
Aug 20 12:52:07.680790 ubuntu-
--
Aug 20 12:52:07.721266 ubuntu- xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: DEBUG nova.virt.driver [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] Emitting event <LifecycleEvent: 1534769527.64, 9797a641- 8925-4f74- abbf-c6111d47f9 1d => Paused> {{(pid=27062) emit_event /opt/stack/ nova/nova/ virt/driver. py:1545} } xenial- ovh-gra1- 0001411231 nova-compute[ 27062]: INFO nova.compute. manager [None req-27237dca- 57e7-488d- aa47-f8f53ad60f c9 None None] [instance: 9797a641- 8925-4f74- abbf-c6111d47f9 1d] VM Paused (Lifecycle Event)
Aug 20 12:52:07.721592 ubuntu-
And then that's it. So it looks like we go from resumed (running) back to paused in the guest and then never get back to running.