yahoo-eng-team team mailing list archive

[OpenStack Infra <2101998@xxxxxxxxxxxxxxxxxx>]

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

commit de237bc92f56bd99c7021ebd79cdbbd8dfe5f450
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Mar 11 14:52:08 2025 +0000

    [OVN] Delete a resource provider removed from the agent config
    
    In ML2/OVN, The Placement information per compute node is stored in the
    local OVS database, in the Open vSwitch register. Each time this
    information changes, ML2/OVN receives this event and updates the OVN
    agent child registers assigned to devices.
    
    Since this patch, if a resource provider is removed, the corresponding
    Placement resource provider register (and its inventory) is removed too.
    
    NOTE: if a resource provider has allocations, the delete operation will
    fail with HTTP 409 (Conflict) and the Neutron API will log this error.
    The error message will be:
      Unable to delete resource provider <UUID>: Resource provider has
      allocations.
    
    Closes-Bug: #2101998
    Change-Id: I78319cc3c94bf869383ecfaf14cb276b46086b8e


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

Title:
  [OVN][Placement] Deleting a configured resource provider does not
  remove the Placement entry

Status in neutron:
  Fix Released

Bug description:
  In ML2/OVN, the resource provider information is retrieved from the
  local OVS Open vSwitch register, in the "external_ids" field [1]. This
  configuration is dynamic: every time the local OVS register is
  updated, the Neutron API parses the resource provider information
  (traits, RP, inventories) and updates the Placement API for this agent
  (the event is received per register, that represents one compute node,
  thus only one parent agent RP and its children are updated).

  If a resource provider is removed (for example, a physical network or
  the generic tunnelled network definition), the Placement API still
  shows it. The goal of this bug is to be able to delete a removed
  resource provider from the Placement database when removed from a
  compute node local OVS configuration.

  Jira reference (RHOSO18): https://issues.redhat.com/browse/OSPRH-14597

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