If you grep for req-624df130-b4cd-4e2e-bd9a-cfcbe0b502a8 you can see that it is a terminate_instance
If you see who did a brctl delif just before this failed, you find:
dims@dims-laptop:~/junk$ grep "brctl delif qbrf4e6ce85-9f" screen-n-cpu.txt.gz
2013-10-30 21:48:26.574 DEBUG nova.openstack.common.processutils [req-72ee662b-b1ed-47b6-b4aa-b880530629e9 ServerActionsTestXML-tempest-1320742179-user ServerActionsTestXML-tempest-1320742179-tenant] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f execute /opt/stack/new/nova/nova/openstack/common/processutils.py:147
2013-10-30 22:01:46.059 DEBUG nova.openstack.common.processutils [req-624df130-b4cd-4e2e-bd9a-cfcbe0b502a8 ServerActionsTestXML-tempest-1320742179-user ServerActionsTestXML-tempest-1320742179-tenant] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f execute /opt/stack/new/nova/nova/openstack/common/processutils.py:147
2013-10-30 22:01:46.123 2087 TRACE nova.virt.libvirt.vif [instance: d39887ee-f76f-4682-b51a-06dcd3a6ea4f] Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f
so looking for req-72ee662b-b1ed-47b6-b4aa-b880530629e9 you will see that it is a rebuild_instance
SO, a rebuild_instance is going on which has just issued delif and we get a terminate_instance which also tries to cleanup the same thing and ends up with the trace shown in the bug report
Taking this example: org/92/ 54092/1/ gate/gate- tempest- devstack- vm-neutron- pg-isolated/ d7ae6d4/ logs/screen- n-cpu.txt. gz
logs.openstack.
we see the following problem: common. processutils [req-624df130- b4cd-4e2e- bd9a-cfcbe0b502 a8 ServerActionsTe stXML-tempest- 1320742179- user ServerActionsTe stXML-tempest- 1320742179- tenant] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/ rootwrap. conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f execute /opt/stack/ new/nova/ nova/openstack/ common/ processutils. py:147 common. processutils [req-624df130- b4cd-4e2e- bd9a-cfcbe0b502 a8 ServerActionsTe stXML-tempest- 1320742179- user ServerActionsTe stXML-tempest- 1320742179- tenant] Result was 1 execute /opt/stack/ new/nova/ nova/openstack/ common/ processutils. py:172 libvirt. vif [req-624df130- b4cd-4e2e- bd9a-cfcbe0b502 a8 ServerActionsTe stXML-tempest- 1320742179- user ServerActionsTe stXML-tempest- 1320742179- tenant] [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Failed while unplugging vif libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Traceback (most recent call last): libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] File "/opt/stack/ new/nova/ nova/virt/ libvirt/ vif.py" , line 636, in unplug_ovs_hybrid libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] utils.execute( 'brctl' , 'delif', br_name, v1_name, run_as_root=True) libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] File "/opt/stack/ new/nova/ nova/utils. py", line 174, in execute libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] return processutils. execute( *cmd, **kwargs) libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] File "/opt/stack/ new/nova/ nova/openstack/ common/ processutils. py", line 178, in execute libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] cmd=' '.join(cmd)) libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] ProcessExecutio nError: Unexpected error while running command. libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Command: sudo nova-rootwrap /etc/nova/ rootwrap. conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Exit code: 1 libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Stdout: '' libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Stderr: 'interface qvbf4e6ce85-9f does not exist!\n' libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f]
2013-10-30 22:01:46.059 DEBUG nova.openstack.
2013-10-30 22:01:46.122 DEBUG nova.openstack.
2013-10-30 22:01:46.123 ERROR nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
If you grep for req-624df130- b4cd-4e2e- bd9a-cfcbe0b502 a8 you can see that it is a terminate_instance
If you see who did a brctl delif just before this failed, you find: laptop: ~/junk$ grep "brctl delif qbrf4e6ce85-9f" screen-n-cpu.txt.gz common. processutils [req-72ee662b- b1ed-47b6- b4aa-b880530629 e9 ServerActionsTe stXML-tempest- 1320742179- user ServerActionsTe stXML-tempest- 1320742179- tenant] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/ rootwrap. conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f execute /opt/stack/ new/nova/ nova/openstack/ common/ processutils. py:147 common. processutils [req-624df130- b4cd-4e2e- bd9a-cfcbe0b502 a8 ServerActionsTe stXML-tempest- 1320742179- user ServerActionsTe stXML-tempest- 1320742179- tenant] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/ rootwrap. conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f execute /opt/stack/ new/nova/ nova/openstack/ common/ processutils. py:147 libvirt. vif [instance: d39887ee- f76f-4682- b51a-06dcd3a6ea 4f] Command: sudo nova-rootwrap /etc/nova/ rootwrap. conf brctl delif qbrf4e6ce85-9f qvbf4e6ce85-9f
dims@dims-
2013-10-30 21:48:26.574 DEBUG nova.openstack.
2013-10-30 22:01:46.059 DEBUG nova.openstack.
2013-10-30 22:01:46.123 2087 TRACE nova.virt.
so looking for req-72ee662b- b1ed-47b6- b4aa-b880530629 e9 you will see that it is a rebuild_instance
SO, a rebuild_instance is going on which has just issued delif and we get a terminate_instance which also tries to cleanup the same thing and ends up with the trace shown in the bug report