yahoo-eng-team team mailing list archive

[OpenStack Infra <1573828@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/310490
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=0ec8c1c29bec9cda5f1ebb2f843b935715dc93e0
Submitter: Jenkins
Branch:    master

commit 0ec8c1c29bec9cda5f1ebb2f843b935715dc93e0
Author: Elena Ezhova <eezhova@xxxxxxxxxxxx>
Date:   Wed Apr 27 17:25:02 2016 +0300

    Validate that subnet exists before adding member to pool
    
    Providing nonexistent subnet_id on pool member create leads
    to LB getting stuck in PENDING_UPDATE state. subnet_id is validated
    in neutronclient only on CLI level, so this problem takes place
    for all API calls.
    
    Change-Id: I9c9f790b6661cc7b15a8883bb5b7e45e69898d99
    Closes-Bug: #1573828


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

Title:
  Neutron-LBaaS v2: Providing invalid subnet_id to add member causing LB
  to go into pending_update indefinitely

Status in neutron:
  Fix Released

Bug description:
  1.  Create Load Balancer
  2.  Create Listener
  3.  Create Pool
  4.  Add member to Pool with a subnet_id that does not exist (but has a valid uuid format)
  5.  Check Load Balancer provisioning_status

  Result:  Load Balancer stays in provisioning_status PENDING_UPDATE for
  more than 10 minutes.

  Expected:  Load Balancer should give an error that the subnet_id does
  not exist.

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