Reviewed: https://review.openstack.org/440609 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ae8e6095f9c15f9d1012427c0b098c98fdc154fa Submitter: Jenkins Branch: master
commit ae8e6095f9c15f9d1012427c0b098c98fdc154fa Author: rtmdk <[email protected]> Date: Thu Mar 2 22:21:47 2017 -0700 add 4094 to fix the range of available local vlans in fact the range of available local vlan is 1-4094, but when initialization of the local vlan in ovs_neutron_agent, self.available_local_vlans is set([1,2,3...4093]),omit 4094 This causes a problem that ovs-agent will not use 4094 as local vlan modify moves.range(p_const.MIN_VLAN_TAG, p_const.MAX_VLAN_TAG+1) Closes-Bug: #1668908 Change-Id: Ic25929cad89ab2e31fdf5b70875b84491dfc52ed ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1668908 Title: available_local_vlans miss 4094 Status in neutron: Fix Released Bug description: p_const.MIN_VLAN_TAG=1 p_const.MAX_VLAN_TAG=4094 self.available_local_vlans = set(moves.range(p_const.MIN_VLAN_TAG,p_const.MAX_VLAN_TAG)) the value of self.available_local_vlans is ([1,2.....4093]),omit 4094 when ovs-agent set the local vlan，4094 is valid To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1668908/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
