← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2051729] Re: issue dhcp cleaning stale devices process when enable action

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/907250
Committed: https://opendev.org/openstack/neutron/commit/06bc855dcf9521ac9c0be1ad7a2fa9bd115a1fd3
Submitter: "Zuul (22348)"
Branch:    master

commit 06bc855dcf9521ac9c0be1ad7a2fa9bd115a1fd3
Author: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@xxxxxxxxxxxxxxxxxxxxxxxx>
Date:   Mon Mar 25 10:26:44 2024 +0100

    dhcp: fix dhcp cleaning stale devices process when enable action
    
    This commit addresses an issue with the DHCP cleaning stale devices
    getting called at the end of enable action.
    
    The cleanup_stale_devices function is invoked to remove stale devices
    within the namespace. The method cleanup_stale_devices examines the
    ports in the network to prevent the unintentional removal of
    legitimate devices.
    
    In a multisegment context, the initial device created might be deleted
    during the second iteration. This occurs because the network variable
    used in the loop is not a singular reference to the same object,
    resulting in its ports not being updated by the ones created during
    previous iterations.
    
    Closes-Bug: #2051729
    Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@xxxxxxxxxxxxxxxxxxxxxxxx>
    Change-Id: I3042df1e2f86070dbc575e7f3b4e3334f037141d


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

Title:
  issue dhcp cleaning stale devices process when enable action

Status in neutron:
  Fix Released

Bug description:
  When call driver enable is called. the cleanup_stale_devices function is invoked to remove stale devices
  within the namespace. The method cleanup_stale_devices examines the
  ports in the network to	prevent the unintentional removal of
  legitimate devices.

  In a multisegment context, the initial device created might be deleted
  during the second iteration. This occurs because the network variable
  used in the loop is not a singular reference to the same object,
  resulting in its ports not being updated by the ones created during
  previous iterations.

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



References