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

commit 5cfc1d5414762af3d382edb5dafc47433ab3b025
Author: Rodolfo Alonso Hernandez <[email protected]>
Date:   Mon Jun 2 11:05:25 2025 +0000

    [OVN] Set OVN bridge in Chassis_Private in OVN agent
    
    The method ``MetadataAgent._update_chassis_private_config`` is called in
    the OVN metadata agent to update the corresponding Chassis_Private
    register; in this case, with the OVN bridge used (that by default is
    usually "br-int").
    
    This call was missing from the OVN agent "metadata" extension, both
    in the initialization method and in the resync.
    
    Closes-Bug: #2112314
    Change-Id: Ia22572d8953c3bade5bfd9950a2d83e050847d65


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

Title:
  [OVN] Missing call to update the 'neutron:ovn-bridge' in the OVN agent
  "metadata" extension

Status in neutron:
  Fix Released

Bug description:
  Right now we have some duplicated code between the OVN Metadata agent
  and the OVN agent "metadata" extension.

  In [1] it was introduced a method that updates the "Chassis_Private"
  register ("external_ids" field) with the OVN bridge name. This method
  is called during the initialization and the resync process. This is
  missing in the OVN agent "metadata" extension.

  
[1]https://review.opendev.org/c/openstack/neutron/+/903494/9/neutron/agent/ovn/metadata/agent.py

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


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to