LBaaS allows multiple members with same IP/port combination in the same pool

Bug #1251867 reported by Stephen Gran
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Stephen Gran

Bug Description

This should probably be enforced at the schema level.

Tags: lbaas
Changed in neutron:
assignee: nobody → Eugene Nikanorov (enikanorov)
tags: added: lbaas
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/56815

Changed in neutron:
assignee: Eugene Nikanorov (enikanorov) → Stephen Gran (sgran)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/56815
Committed: http://github.com/openstack/neutron/commit/218c249b0dea094944aead116cf07fc19f029852
Submitter: Jenkins
Branch: master

commit 218c249b0dea094944aead116cf07fc19f029852
Author: Stephen Gran <email address hidden>
Date: Sun Nov 17 11:35:29 2013 +0000

    Enforce unique constraint on neutron pool members

    Neutron loadbalancer pool members should not be allowed to have
    duplicate address/port tuples in the same pool.

    Change-Id: Ie52c6033217ec05ee4f59bcf8a0e4167c7b13663
    Closes-Bug: #1251867

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → icehouse-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-1 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.