[NETVIRT-129] External network group entry not installed on new DPN Created: 09/Sep/16  Updated: 25/Oct/16  Resolved: 25/Oct/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Tomer Pearl Assignee: Ravit Peretz
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Duplicate
duplicates NETVIRT-141 Output to external network group entr... Resolved
External issue ID: 6682

 Description   

I'm using Devstack to bring up one control+compute and another compute.
Devstack configures the external network and router before the second compute (and it's OVS) is configured

When the OVS on the second compute goes up, it is missing the group entry responsible for external network. (group id is 200000, external port is OF port 1)

OVS1

OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=200000,type=all,bucket=actions=set_field:00:1c:73:4e:d3:31->eth_dst,load:0x200->NXM_NX_REG6[],resubmit(,220)
group_id=209999,type=all,bucket=actions=set_field:0x1->tun_id,resubmit(,55),bucket=actions=set_field:0x4->tun_id,resubmit(,55)
group_id=150002,type=all,bucket=actions=set_field:fa:16:3e:3e:e9:1e->eth_dst,load:0x400->NXM_NX_REG6[],resubmit(,220)
group_id=150000,type=all,bucket=actions=set_field:fa:16:3e:65:08:3f->eth_dst,load:0x100->NXM_NX_REG6[],resubmit(,220)
group_id=210000,type=all,bucket=actions=group:209999,bucket=actions=set_field:0x1388->tun_id,output:4
group_id=210002,type=all,bucket=actions=group:210001,bucket=actions=load:0x200->NXM_NX_REG6[],resubmit(,220)
group_id=210001,type=all

cookie=0x8000007, duration=1191.945s, table=220, n_packets=890, n_bytes=210, priority=7,reg6=0x200 actions=output:1
cookie=0x8000007, duration=1191.564s, table=220, n_packets=50, n_bytes=5204, priority=7,reg6=0x100 actions=output:2
cookie=0x8000007, duration=720.422s, table=220, n_packets=69, n_bytes=7093, priority=7,reg6=0xe0000400 actions=output:3
cookie=0x6900000, duration=720.422s, table=220, n_packets=69, n_bytes=7093, priority=6,reg6=0x400 actions=load:0xe0000400->NXM_NX_REG6[],write_metadata:0xe000040000000000/0xfffffffffffffffe,goto_table:251

OVS2

OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=200001,type=all,bucket=actions=output:3
group_id=150001,type=all,bucket=actions=set_field:fa:16:3e:9c:c2:be->eth_dst,load:0x300->NXM_NX_REG6[],resubmit(,220)
group_id=209999,type=all,bucket=actions=set_field:0x3->tun_id,resubmit(,55)
group_id=210000,type=all,bucket=actions=group:209999,bucket=actions=set_field:0x1388->tun_id,output:3

cookie=0x6900000, duration=659.040s, table=220, n_packets=70, n_bytes=7163, priority=6,reg6=0x300 actions=load:0xe0000300->NXM_NX_REG6[],write_metadata:0xe000030000000000/0xfffffffffffffffe,goto_table:251
cookie=0x8000007, duration=659.039s, table=220, n_packets=70, n_bytes=7163, priority=7,reg6=0xe0000300 actions=output:2

Analysis of the class ExternalNetworkGroupInstaller shows that it is triggered by one of two events:
1. gw mac changed
2. subnet (of the external network, i guess) changed

My assumption is that the first OVS is configured properly because it is up before configuring the external network.

Couldn't find any code that handles new OVS after external network is configured.

This issue blocks VMs on this OVS from using floating IP, and may also block all VMs using NAPT if this OVS is chosen as the "NAPT SWITCH".



 Comments   
Comment by Ravit Peretz [ 18/Sep/16 ]

The ovs restart scenario is now worked around thanks to a code in patch (specifically in ExternalNetworkGroupInstaller):
https://git.opendaylight.org/gerrit/#/c/45133/3/vpnservice/natservice/natservice-impl/src/main/java/org/opendaylight/netvirt/natservice/internal/ExternalNetworkGroupInstaller.java

the validation for router existence was removed and it seems like now we do not miss the external group installation for the new DPN.

Comment by Ravit Peretz [ 21/Sep/16 ]

Adding a new DPN though still does'nt work

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