Duplicate with
https://bugs.launchpad.net/neutron/+bug/1269926
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1318881
Title:
network with VLAN ID not in network_vlan_ranges shouldn't be created
successfully for ml2
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
I have network_vlan_ranges = physnet1:1000:2999 in ml2_conf.ini. I can create
a net with '--provider:segmentation_id 4000' which is out of the range
1000:2999.
I found a debug log in the method reserve_provider_segment in type_vlan.py,
but I think this is not enough because this makes the VLAN range in
network_vlan_ranges no sense.
In reserve_provider_segment type_vlan.py,
except sa.orm.exc.NoResultFound:
LOG.debug(_("Reserving specific vlan %(vlan_id)s on physical "
"network %(physical_network)s outside pool"),
{'vlan_id': vlan_id,
'physical_network': physical_network})
alloc = VlanAllocation(physical_network=physical_network,
vlan_id=vlan_id,
allocated=True)
session.add(alloc)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1318881/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
