Seen here:
http://logs.openstack.org/63/631363/22/check/nova-grenade-live-migration/1a03cbc/logs/subnode-2/screen-n-cpu.txt.gz?level=WARNING
Mar 11 07:50:38.515198 ubuntu-xenial-ovh-bhs1-0003641906 nova-compute[3321]: WARNING nova.compute.manager [req-883bec65-937b-4ed6-9d05-f0282ed17b75 req-11ffd59a-bf70-4cec-9678-36d3335ef766 service nova] [instance: faf3444e-f788-4ff4-992a-b14ce53ef8f8] Received unexpected event network-vif-unplugged-85392fed-4d68-4e01-818a-e004a33d95b6 for instance with vm_state paused and task_state migrating.
There are 22 instances of that same type of warning in that compute log, and it's all over our CI jobs that run live migration tests:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Received%20unexpected%20event%20network-vif-unplugged%5C%22%20AND%20message%3A%5C%22and%20task_state%20migrating.%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
We don't listen for network-vif-unplugged events during live migration and the unplug events are expected so we shouldn't warn about those.
We see quite a bit of this for other move operations like resize revert and shelve offload as well, and hard reboots, but we could deal with those separately:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Received%20unexpected%20event%20network-vif-unplugged%5C%22%20AND%20NOT%20message%3A%5C%22and%20task_state%20None%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
Fix proposed to branch: master
Review: https:/