VIRT VMs deployment does not work with VXLAN + all interfaces with VLAN tagging

Bug #1669667 reported by Luca Cervigni
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining

Bug Description

FUEL COMMUNITY 10.0

The same as the bug reported more than a year ago for fuel 7 and 8. https://bugs.launchpad.net/fuel/+bug/1488617

with VXLAN and all interfaces tagged with a VLAN the VIRT hypervisor is deployed with the br-ex, br-mgmt, br-stor and br-mesh bridged to the TAGGED vlan. I have 6 10gbps interfaces bridged together, and on top of those, my interfaces VLAN tagged. When the VMs are deployed they incorrectly try to assign to the virtual network interface a VLAN id, though the bridged physical interface on the hypervisor is already tagged!

It is exactly the same as the old bug,though on community 10.

Could you please check it out and if possible provide a workaround? in the old ticket the documentation should have been updated, though did not find anything that described the configuration with VLANs.

Thanks

Revision history for this message
Luca Cervigni (cervigni) wrote :

After talking with Bartosz Kupidura, this behaviour is by design.
It would be nice though to implement something to correct this, in a way to avoid a network template creation only because I have to spun up two virtual machines and the VLAN is double tagged, both in hypervisor and in the VM.

Changed in fuel:
milestone: none → 10.x-updates
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.