← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2122107] Re: [FT] Test ``test_initialize_network_segment_range_support_parallel_execution`` failing in the eventlet-removal patch

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/960006
Committed: https://opendev.org/openstack/neutron/commit/09ed4df066c565928b5d9366b651ca888194d588
Submitter: "Zuul (22348)"
Branch:    master

commit 09ed4df066c565928b5d9366b651ca888194d588
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Mon Sep 8 07:07:17 2025 +0000

    [FT] Randomize the network segment init method starting time
    
    The network segment range initialization method in the test
    ``test_initialize_network_segment_range_support_parallel_execution``
    needs to have a random starting time for each thread. This is similar
    to what will happen in a real environment. With kernel threads, these
    workers perform the same operation on the DB at the same time.
    
    NOTE: the network segment range initialization needs to be improved.
    That will done in [1], in 2026.1.
    
    [1]https://review.opendev.org/c/openstack/neutron/+/947898
    
    Closes-Bug: #2122107
    Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
    Change-Id: I79020a3ad4d0e7db60849939a4030bffe4427834


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

Title:
  [FT] Test
  ``test_initialize_network_segment_range_support_parallel_execution``
  failing in the eventlet-removal patch

Status in neutron:
  Fix Released

Bug description:
  The test
  ``test_initialize_network_segment_range_support_parallel_execution``
  is failing only in the eventlet-removal patch [1]. The execution of
  the threads that in parallel try to update the ``NetworkSegmentRange``
  table are now executed by kernel threads. If the code doesn't block
  the table for the update, that could lead to an real issue in the
  tested code.

  Not only the test should be updated (in particular the method
  ``_initialize_network_segment_range_support`` that replicated the
  running code method) but also the VLAN and tunnelled type drivers
  implementation.

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

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



References