[NETVIRT-1361] [HA] Invalid dpnId configured as NAPT Switch in router-to-napt-switch model Created: 05/Jul/18  Updated: 04/Oct/18  Resolved: 04/Oct/18

Status: Resolved
Project: netvirt
Component/s: natservice
Affects Version/s: None
Fix Version/s: Oxygen-SR3, Fluorine

Type: Bug Priority: Medium
Reporter: Sridhar Gaddam Assignee: Sridhar Gaddam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Description of problem:
-----------------------------
3 ODL Controllers and 2 Compute nodes.

Create an external-flat-network, router and vxlan tenant network.
Associate the router to the external-network and tenant subnet.
Spawn couple of VMs and associate FIPs to each of the VMs.

Take down the compute nodes, start them again and create new VMs, assign FIPs and try to reach them

How reproducible:
Random

Observations:
-------------
The reason why some of the flows were missing for FIP/SNAT is that an invalid dpnId (i.e., 0) was selected as an NAPT Switch.
Ideally a dpnId of zero should not be configured as an NAPT switch in the router-to-napt-switch models and the missing flows are only a side-effect of this.

{
"napt-switches": {
"router-to-napt-switch": [

{ "router-name": "7c126d70-8033-49b0-a473-aa9cdaa07566", "primary-switch-id": 0 }

]
}
}


Generated at Wed Feb 07 20:23:52 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.