Driver VLAN do not create the VlanAllocation registers if "network_vlan_ranges" only specify the network

Bug #1918274 reported by Rodolfo Alonso
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Committed
Rodolfo Alonso

Bug Description

"network_vlan_ranges" allows to define a list of physical networks and VLAN ranges [1]. But is possible to just define the physical network without the VLAN ID ranges; in that case, the VLAN driver should take all valid VLAN IDs (from 1 to 4094).

If no VLAN range is defined, when "VlanTypeDriver._sync_vlan_allocations" is called, the "ranges" variable is:
  ranges = {'physical_net': []}

We have two options here:
- Modify the sync method.
- Change the parser to populate, in case of not passing any VLAN range, the whole list of possible VLAN IDs for this physnet (I think last option is better).


Changed in neutron:
assignee: nobody → Rodolfo Alonso (rodolfo-alonso-hernandez)
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :
Hongbin Lu (
Changed in neutron:
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-lib 2.10.0

This issue was fixed in the openstack/neutron-lib 2.10.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers