yahoo-eng-team team mailing list archive

[OpenStack Infra <1591380@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/328515
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=41ec2ff5e3ea0578dac628176a0c464d1763b3c7
Submitter: Jenkins
Branch:    master

commit 41ec2ff5e3ea0578dac628176a0c464d1763b3c7
Author: Stephen Balukoff <stephen@xxxxxxxxxxxx>
Date:   Fri Jun 10 15:24:58 2016 -0700

    Fix test assumptions about IP allocation
    
    Several tests in the neutron-lbaas code tree make assumptions about how
    IP addresses in Neutron subnets will be allocated without actually
    specifying the IP addresses explictly. Neutron's behavior recently
    changed on this front, and these tests started failing in the gate. This
    commit updates these tests to explicitly specify the IP address they
    should be testing against for allocation purposes, or to dynamically
    detect the IP address Neutron has assigned during a previous call.
    
    Change-Id: I0afc3acfff96f85622495364240e1e60f9fd5d7c
    Closes-Bug: #1591380


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

Title:
  neutron-lbaas: broken tests after vip allocation behavior changed

Status in neutron:
  Fix Released

Bug description:
  In the last couple of days, gate checks for neutron-lbaas have started
  to consistently fail on tests that have not been altered recently.
  Digging futher into this, it appears that neutron's subnet IP address
  allocation behavior has changed, and there are several neutron-lbaas
  tests which hard code assumptions about which VIP address for a given
  load balancer will be assigned when it isn't actually specified in the
  test. These tests need to be updated to either specify the IP address
  to be used directly (ie. over-riding Neutron's IP address allocation
  behavior which can indeed change at any time), or updated to more
  dynamically detect the VIP address that gets assigned when the value
  isn't specified directly.

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