yahoo-eng-team team mailing list archive

[OpenStack Infra <2102090@xxxxxxxxxxxxxxxxxx>]

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

commit 5841cacecb79ba73a0ba02fd23db75fcc5909502
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Wed Mar 19 12:24:17 2025 +0000

    [OVN][Placement] Placement init config with Chassis create event
    
    Now the initial Placement configuration per Chassis is build when
    a Chassis create event is received. That will happen when:
    * The Neutron API is restarted.
    * When a new Chassis register is created.
    
    Closes-Bug: #2102090
    Change-Id: I9aa8accdcead079fe2e713fe569f8bff7403be92


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

Title:
  [OVN][Placement] With Neutron API WSGI module, the initial chassis
  configuration is not executed

Status in neutron:
  Fix Released

Bug description:
  Since the migration of the Neutron API to the WSGI module, the ML2/OVN
  Placement extension method ``read_initial_chassis_config`` is not
  executed when the Neutron API is restarted. This method is called from
  ``OvnSbSynchronizer.do_sync``, but this class and method is no longer
  called from the Neutron API process but from the maintenance process
  (now these are two separate processes).

  The aim of this bug is to implement the Placement initial
  configuration on the Neutron API.

  **NOTE**: this architectural proposal needs to be agreed upon by the
  Neutron maintainer members. This is NOT a bug but a possible
  improvement.

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