yahoo-eng-team team mailing list archive

[Rodolfo Alonso <ralonsoh@xxxxxxxxxx>]

Public bug reported:

As reported by some users [1], the Neutron table "ml2_vlan_allocations"
contains allocations with vlan_id=0.

A VLAN ID with value 0 is not accepted by Neutron during the parsing of
config option "network_vlan_ranges". "NetworkVlanRangeError" exception
is raised.

Despite of this check, the DB, somehow, has a register with vlan_id=0:

> select * from ml2_vlan_allocations;
+------------------+---------+-----------+
| physical_network | vlan_id | allocated |
+------------------+---------+-----------+
| tenant ......... | ..... 0 | ....... 1 |
...

A DB backend check should disable any writing operation with vlan_id out
of the allowed VLAN tags [1, 4094]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1716857

** Affects: neutron
     Importance: Undecided
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: In Progress

** Description changed:

  As reported by some users [1], the Neutron table "ml2_vlan_allocations"
  contains allocations with vlan_id=0.
  
  A VLAN ID with value 0 is not accepted by Neutron during the parsing of
  config option "network_vlan_ranges". "NetworkVlanRangeError" exception
  is raised.
  
  Despite of this check, the DB, somehow, has a register with vlan_id=0:
  
  > select * from ml2_vlan_allocations;
  +------------------+---------+-----------+
  | physical_network | vlan_id | allocated |
  +------------------+---------+-----------+
  | tenant           |       0 |         1 |
- | tenant           |    1000 |         1 | 
+ | tenant           |    1000 |         1 |
  | tenant           |    1001 |         1 |
  ...
  
  A DB backend check should disable any writing operation with vlan_id out
  of the allowed VLAN tags [1, 4094]
  
- 
  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1716857

** Description changed:

  As reported by some users [1], the Neutron table "ml2_vlan_allocations"
  contains allocations with vlan_id=0.
  
  A VLAN ID with value 0 is not accepted by Neutron during the parsing of
  config option "network_vlan_ranges". "NetworkVlanRangeError" exception
  is raised.
  
  Despite of this check, the DB, somehow, has a register with vlan_id=0:
  
  > select * from ml2_vlan_allocations;
  +------------------+---------+-----------+
  | physical_network | vlan_id | allocated |
  +------------------+---------+-----------+
- | tenant           |       0 |         1 |
- | tenant           |    1000 |         1 |
- | tenant           |    1001 |         1 |
+ | tenant ......... | ..... 0 | ....... 1 |
  ...
  
  A DB backend check should disable any writing operation with vlan_id out
  of the allowed VLAN tags [1, 4094]
  
  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1716857

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1870400

Title:
  "ml2_vlan_allocations.vlan_id" value should be checked in the DB
  backend

Status in neutron:
  In Progress

Bug description:
  As reported by some users [1], the Neutron table
  "ml2_vlan_allocations" contains allocations with vlan_id=0.

  A VLAN ID with value 0 is not accepted by Neutron during the parsing
  of config option "network_vlan_ranges". "NetworkVlanRangeError"
  exception is raised.

  Despite of this check, the DB, somehow, has a register with vlan_id=0:

  > select * from ml2_vlan_allocations;
  +------------------+---------+-----------+
  | physical_network | vlan_id | allocated |
  +------------------+---------+-----------+
  | tenant ......... | ..... 0 | ....... 1 |
  ...

  A DB backend check should disable any writing operation with vlan_id
  out of the allowed VLAN tags [1, 4094]

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1716857

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1870400/+subscriptions