← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1576054] Re: [lbaasv2] listener and member can be created with protocol_port 0

 

Reviewed:  https://review.openstack.org/311631
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=4b6858902faefba5c0aa7abbacb7978a2e9a0801
Submitter: Jenkins
Branch:    master

commit 4b6858902faefba5c0aa7abbacb7978a2e9a0801
Author: Joseph Bajin <josephbajin@xxxxxxxxx>
Date:   Sun May 1 13:26:08 2016 -0400

    Updated port validation to not allow port 0
    
    The default port validation allowed ports 0-65535
    to be created on members and listeners. Port 0 is not
    a valid port 0 to listen on.
    
    Modified the extenstions for both v1 and v2 loadbalancer
    to validate starting at port 1 and not port 0.
    
    Change-Id: I204e0032d0fa59776b3a5bc6be03a23991a5aeeb
    Closes-Bug: #1576054


** 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/1576054

Title:
  [lbaasv2] listener and member can be created with protocol_port 0

Status in neutron:
  Fix Released

Bug description:
  protocol_port 0 is reserved.But in lbaasv2,users can create listener or member with protocol_port 0. 
  For example:
  Created a new member:
  +----------------+--------------------------------------+
  | Field          | Value                                |
  +----------------+--------------------------------------+
  | address        | 1.1.1.2                              |
  | admin_state_up | True                                 |
  | id             | 72eab0e7-f51f-4927-aaf3-71177a0ed34a |
  | protocol_port  | 0                                    |
  | subnet_id      | 1b86ca37-738c-4ada-8026-cf65acd20a27 |
  | tenant_id      | be58eaec789d44f296a65f96b944a9f5     |
  | weight         | 1                                    |
  +----------------+--------------------------------------+

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


References