yahoo-eng-team team mailing list archive

[OpenStack Infra <1929190@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/792559
Committed: https://opendev.org/openstack/neutron/commit/05ce5a1f9409d9fdd4ef92133f38d7ec9084b1c5
Submitter: "Zuul (22348)"
Branch:    master

commit 05ce5a1f9409d9fdd4ef92133f38d7ec9084b1c5
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Fri May 21 09:44:22 2021 +0000

    VLAN "allocate_partially_specified_segment" can return any physnet
    
    When allocating a partially defined segment with VLAN type driver, any
    physical network can be returned. The method will select randomly any
    VLAN segment available, independently of the physnet configured order.
    
    Change-Id: I4d344f5ca6673b70b69a03503ec0f267bf0cadf7
    Closes-Bug: #1929190


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

Title:
  "test_reserve_provider_segment_without_physical_network" failing
  randomly

Status in neutron:
  Fix Released

Bug description:
  Since [1], the VLAN segment allocation using
  "get_random_unallocated_segment" does not enforce a priority in the
  physical network selection, depending on the configuration order. All
  available physical network segments can be selected randomly; that
  means any physical network can be chosen.

  The occurrence of this error was low because "phys_net1" has 4096 VLAN
  IDs and "phys_net2" only 10.

  Error:
  https://1a46c32c0fda8a65ef95-6c47599ea81a63bd28f7b62c07ab0c76.ssl.cf5.rackcdn.com/792015/2/check
  /openstack-tox-cover/c3222cd/testr_results.html

  Snippet: http://paste.openstack.org/show/805543/

  [1]https://review.opendev.org/c/openstack/neutron/+/780802

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