In a centralized VLAN network, when gateway Chassis and HA Chassis are not one node, layer 3 fails

Bug #1947073 reported by Reason li
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
New
Undecided
Unassigned

Bug Description

Cluster environment: two gateway nodes and one compute node (SRIOv)
1、Creating an internal VLAN 123.45.67.0/24
2、Create an external Flat network 192.168.1.0/24
3、Create a route, select the newly created VLAN and set the IP address of the subinterface to 123.45.67.1
4、Add an external gateway 192.168.1.10 to the router
5、Create an external port 123.45.67.10 based on the VLAN network for the SRIOv VM
6、The router external gateway port has a gateway chassis priority, and the default ha-chassis-group has a chassis priority
7、When the chassis priority of the external gateway of the router is inconsistent with that of the ha-chassis priority, SRIOV VM cannot carry out Layer 3 forwarding because it cannot learn the MAC of gateway 123.45.67.1.

For example,
(ovn-nb-db)#ovn-nbctl show
switch 67ada1b-aef9-4ab0-9f02-15a016fd159d (neutron-370f1129-abc1-ef14-e84e-fb17b9f0a912)(aka vlan333)
        port test-sriov
            type:external
            addresses:["fa:16:3e:8a:1d:0a 123.45.67.111"]
        port provnet-3cda99014-a891-e918-341f-fb87691e478a
            type:localnet
            tag:333
            addresses:["unknown"]
        port dof2db65-2c58-4bc1-816d-9148be1ae6fd
            type:localport
            addresses:["fa:16:3e:6b:ab:4b 123.45.67.11"]
        port route-interface1
            type:router
            router-port:lrp-route-interface1
switch 8910ae14-f1b8-c135-3618-145ae89134da (neutron-fb17b9f0-ef14-e84e-abc1-9f0a370f1129) (aka flat)
        port provnet-e9189014-341f-fb87-a891-f8913cda99014
            type:localnet
            addresses:["unknow"]
        port route-external-gateway
            type:router
            router-port:lrp-route-external-gateway
router a9589135-78a2-134a-89e1-98a1b2c4157a (neutron-7c1134a6-1239-0871-c12e-f1951098a214) (aka route)
       port lrp-route-interface1
            mac: "fa:16:3e:91:e1:f1"
            networks:["123.45.67.1/24"]
       port lrp-route-external-gateway
            mac: "fa:16:3e:89:13:ae"
            networks:["192.168.1.10/24"]
            gateway chassis:[network-node1,network-node2]
       nat 0f11292-ef14-e84e-abc1-134a670f1129
            external ip: "192.169.1.10"
            logical ip: "123.45.67.0/24"
            type: "snat"
(ovn-nb-db)#ovn-nbctl lrp-get-gateway-chasssis lrp-route-external-gateway
lrp-route-external-gateway_network-node1 2
lrp-route-external-gateway_network-node2 1

(ovn-nb-db)#ovn-nbctl list ha-chassis
_uuid : bd2345c5-8913-1234-1176-a1235917e1f
chassis_name : "network-node1"
external_ids : {}
priority : 32764

_uuid : bd2345c5-8913-1234-1176-a1235917e1f
chassis_name : "network-node2"
external_ids : {}
priority : 32765

The sriov VM (123.45.67.111) to 123.45.67.1 fails because network-node2 does not respond to ARP requests

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.