network connectivity of Xen instances not possible if nova.virt.libvirt.vif.QuantumLinuxBridgeVIFDriver creates tap devices

[Christian Berendt]

The problem is that Xen wants to create a new tap device with the defined vifname but that's not possible because it was already created by QuantumLinuxBridgeVIFDriver. If the device with the defined vifname already exists Xen creates and uses a new device with the name vif$DOMAIN.0. It's ending with a not working network connectiviy.

If QuantumLinuxBridgeVIFDriver is used it should not create a new tap device if libvirt_type = 'xen'.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/7013

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/7013
Committed: http://github.com/openstack/nova/commit/4c4f0b705fb3dbe828b724b2b0e534ee58fd836c
Submitter: Jenkins
Branch: master

commit 4c4f0b705fb3dbe828b724b2b0e534ee58fd836c
Author: Christian Berendt <email address hidden>
Date: Wed May 2 11:47:59 2012 +0200

    Xen has to create it's own tap device if using libvirt and QuantumLinuxBridgeVIFDriver

    fixes bug 993151

    Change-Id: Ibc9c8c7a1e8601d596ace9906c7723f4671029fa