Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I hit this problem either. I don' think it has any relation with bridge-mapping. In my experice, I found that vm spawn has two scheduling process. In the first one, the tap interfacein ovs has been created by nova-compute, and the port status in neutron db is active. But then, the compute node meet qemu error (CPU feature are not found). The exception make nova-scheduler to reschedule. The second process would also create port and ovs interface in a new compute node. As a result, it has two port in neutron. After I closed the broken nova-compute, the problem was dissappeared.

I hit this problem either. I don' think it has any relation with bridge-mapping. In my experice, I found that vm spawn has two scheduling process. In the first one, the tap interfacein interface in ovs has been created by nova-compute, and the port status in neutron db is was active. But then, the compute node meet met qemu error (CPU feature are were not found). The exception make made nova-scheduler to reschedule. The second process would also create port and ovs interface in by a new compute node. As a result, it has two port in neutron. After I closed the broken nova-compute, fault one, the problem was dissappeared.dissappeared. All new created vm had only one port.