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

commit a37c2d2a1e27266f51259b33c5b2720f41f00b71
Author: Miguel Lavalle <mlava...@redhat.com>
Date:   Wed May 14 19:13:42 2025 -0500

    Fix ovn_db_sync for user defined flavor routers
    
    When ovn_db_sync is executed in repair mode after a Neutron server
    restart, it erronously adds user defined flavor routers to the OVN NBDB.
    Those routers are not managed by OVN. Hereby the issue if fixed.
    
    Change-Id: Iacd78020ee41399c3a8ce6cfdf9e37c4f865c90e
    Closes-Bug: #2110060


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

Title:
  OVN router flavors create OVN router on Neutron restart

Status in neutron:
  Fix Released

Bug description:
  When I create a router using the UserDefined and then restart Neutron,
  it will create the router in OVN.

  2025-05-05 22:20:37.643 16 WARNING 
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovn_db_sync [None 
req-75c6e768-3842-45e0-9ec5-4cf3d6aca434 - - - - - -] Router found in Neutron 
but not in OVN NB DB, router id=87e0e66b-c720-41b2-bd8e-09d00c3563d3
  2025-05-05 22:20:37.643 16 WARNING 
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovn_db_sync [None 
req-75c6e768-3842-45e0-9ec5-4cf3d6aca434 - - - - - -] Creating the router 
87e0e66b-c720-41b2-bd8e-09d00c3563d3 in OVN NB DB

  my neutron.conf has the following:

  [ovn]
  neutron_sync_mode = repair

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


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to