yahoo-eng-team team mailing list archive

[OpenStack Infra <1850292@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/692135
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3c9b0a5fac2e3a1321eadc272c8ed46aa61efd3e
Submitter: Zuul
Branch:    master

commit 3c9b0a5fac2e3a1321eadc272c8ed46aa61efd3e
Author: elajkat <lajos.katona@xxxxxxxx>
Date:   Wed Oct 30 13:38:30 2019 +0100

    [fullstack] find ip based on allocation_pool
    
    _find_available_ips tried to find available ips based on the given
    subnet's cidr field, which can be misleading if random selection goes
    out-of allocation-pool. This patch changes this behaviour to use
    cidr's allocation_pool field.
    
    Closes-Bug: #1850292
    Change-Id: Ied2ffb5ed58007789b0f5157731687dc2e0b9bb1


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

Title:
  Fullstack test can try to use IP address from outside the subnet's
  allocation pool

Status in neutron:
  Fix Released

Bug description:
  Example of failure
  https://storage.gra1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_076/679399/22/gate
  /neutron-fullstack/07671c7/testr_results.html.gz

  It seems that in method _find_available_ips: https://github.com/openstack/neutron/blob/94f69ab407d081ce49fa5a93946c4cd41bf6ee89/neutron/tests/fullstack/base.py#L130
  it may happen that as random IP will be chosen address from outside of allocation pool defined in neutron db.

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