← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2083832] Re: [OVN] Host_id value on lsp for router gateway is not updated on failover

 

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

commit 4b032bdbb2a6843b776c367486d1620ea6ae71a5
Author: Aleksandr <silentirk@xxxxxx>
Date:   Mon Oct 7 13:06:59 2024 +0300

    [OVN] Update lsp host id when cr port is updated with chassis
    
    When a chassisredirect port is updated with chassis, the
    PortBindingChassisEvent event would only update the binding
    host id in the neutron database, while it is also usefull to keep the
    information in the OVN database up to date with the host information.
    
    Similar to change [1], but for router's gateway ports.
    
    [1] https://review.opendev.org/c/openstack/neutron/+/896883
    
    Other plugins that connect to the OVN database can then also rely on the
    information stored in the OVN DB's
    
    Closes-Bug: #2083832
    
    Change-Id: Ibe8bda2f81bda7a89e3a994db55cd394a18decb8


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

Title:
  [OVN] Host_id value on lsp for router gateway is not updated on
  failover

Status in neutron:
  Fix Released

Bug description:
  Neutron fills neutron:host_id within external_ids values for router gateway OVN logical switch ports with the hostname of the chassis.
  If a failover happens, binding_host_id in router gateway port is updated with new host in neutron DB, while external_ids:neutron:host_id in OVN database remains old.

  Steps to reproduce:
  1. Create a router with external gateway set
  2. Check binding_host_id for router gateway port in neutron and external_ids:neutron:host_id on lsp in OVN database
  3. Initiate failover (for example turn off the host where port was binded)
  4. Check binding_host_id for router gateway port and external_ids:neutron:host_id

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



References