yahoo-eng-team team mailing list archive

[Assaf Muller <amuller@xxxxxxxxxx>]

Let admins be... I also don't like the possibility of adding yet another
configuration value for this. The current behavior makes sense.

** Changed in: neutron
       Status: In Progress => Opinion

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

Title:
  When vlan id is out range of config_file, creating network still
  success.

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  In neutron ml2 config file /etc/neutron/plugins/ml2/ml2_conf.ini,
  specify vlan range from 1002 to 1030,

  [ml2_type_vlan]
  network_vlan_ranges =physnet2:1002:1030

  When I specifying vlan id 1070 , the vlan id is out range of ml2
  config file. But the network creates success.

  In the bug fix, I will check the vlan segement id with config_file's
  vlan range.

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