Public bug reported: When ItemAllocator.allocate[1] called with same key again, it is returning different value.
So in dvr, if allocate_rule_priority() called again with same key, it is returning different priority value. So trying to add same ip rule again is succeeding as we got different priority from allocate_rule_priority(for same key). As a consequence we will have same ip rule in router namespace but with different priorities. [1] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/item_allocator.py#L51 ** Affects: neutron Importance: Undecided Assignee: venkata anil (anil-venkata) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => venkata anil (anil-venkata) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1533216 Title: item allocator should return same value for same key Status in neutron: In Progress Bug description: When ItemAllocator.allocate[1] called with same key again, it is returning different value. So in dvr, if allocate_rule_priority() called again with same key, it is returning different priority value. So trying to add same ip rule again is succeeding as we got different priority from allocate_rule_priority(for same key). As a consequence we will have same ip rule in router namespace but with different priorities. [1] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/item_allocator.py#L51 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1533216/+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
