[ovn]Gateway port is down after gateway chassis changed

[ZhouHeng]

ml2 driver: ovn
gateway chassis: nodeA, nodeB, nodeC

step 1: create a router and set gateway, the gateway port status is active, and bound nodeA.
step 2: down nodeA, gateway port status change to down, and bound nodeB.
step3: down nodeB, gateway port status change to active, and bound nodeC.

Gateway port status should always be active!

[Oleg Bondarev (obondarev)]

Fix: https://review.opendev.org/c/openstack/neutron/+/825041

[OpenStack Infra (hudson-openstack)]

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

commit 6636f65663446d939a9e3379468bfbca6c9a4f7b
Author: zhouhenglc <email address hidden>
Date: Tue Jan 18 15:17:04 2022 +0800

    [OVN]Ensure gateway port is running after gateway chassis changed

    During normal operation of a router, its gateway port state is running.
    When the gateway chassis of the router binding changes, the host bound
    to the gateway port will be updated(call core_plugin.update_port).
    at this time, the status of the router gateway port will become down,
    and we need to update it to active(call core_plugin.update_port_status).

    Closes-bug: #1958353

    Change-Id: I4c10904d716abb4482898c08f9fd72ad5b106906

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 20.0.0.0rc1 release candidate.