Hmm, the libvirt vif code deletes the port here:
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-n-cpu.txt.gz#_2015-01-02_15_44_15_554
The vif plugged event is received back from neutron here:
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-n-cpu.txt.gz#_2015-01-02_15_44_23_938
Here neutron is saying the port is active:
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-n-cpu.txt.gz#_2015-01-02_15_44_24_849
Here is another nova network info cache update, there are 3 mac addresses at that point:
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-n-cpu.txt.gz#_2015-01-02_15_44_33_737
When the instance is being destroyed we see the port status as 'BUILD':
http://logs.openstack.org/12/142412/3/gate/gate-tempest-dsvm-neutron-full/9990c84/logs/screen-n-cpu.txt.gz#_2015-01-02_15_44_56_420
Hmm, the libvirt vif code deletes the port here:
http:// logs.openstack. org/12/ 142412/ 3/gate/ gate-tempest- dsvm-neutron- full/9990c84/ logs/screen- n-cpu.txt. gz#_2015- 01-02_15_ 44_15_554
The vif plugged event is received back from neutron here:
http:// logs.openstack. org/12/ 142412/ 3/gate/ gate-tempest- dsvm-neutron- full/9990c84/ logs/screen- n-cpu.txt. gz#_2015- 01-02_15_ 44_23_938
Here neutron is saying the port is active:
http:// logs.openstack. org/12/ 142412/ 3/gate/ gate-tempest- dsvm-neutron- full/9990c84/ logs/screen- n-cpu.txt. gz#_2015- 01-02_15_ 44_24_849
Here is another nova network info cache update, there are 3 mac addresses at that point:
http:// logs.openstack. org/12/ 142412/ 3/gate/ gate-tempest- dsvm-neutron- full/9990c84/ logs/screen- n-cpu.txt. gz#_2015- 01-02_15_ 44_33_737
When the instance is being destroyed we see the port status as 'BUILD':
http:// logs.openstack. org/12/ 142412/ 3/gate/ gate-tempest- dsvm-neutron- full/9990c84/ logs/screen- n-cpu.txt. gz#_2015- 01-02_15_ 44_56_420