[NETVIRT-1591] SNAT-DNAT: External IP missing from flow entries Created: 17/Apr/19  Updated: 28/May/19  Resolved: 28/May/19

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Neon
Fix Version/s: Neon, Sodium

Type: Bug Priority: High
Reporter: Jaya Priyadarshini Assignee: Chetan Arakere Gowdru
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days
Original Estimate: Not Specified

Attachments: HTML File snat_dnat_fail_log.html    

 Description   

Steps to reproduce
==============================
1. Create the external network and subnet
2. Create internal networks N1 and N2 with each network having one subnet each.
3. create security group and create ports with this security group.
4. Boot four vms on two computes.
5. Create a router and associate the subnets to router
6. Update the router with external network(associate external gateway with router, SNAT=false, single ExtIP)
7. Create L3vpn and associate external network to VPN
8. Create a floating IP on a neutron port hosted on VSwitch1
9. Access the floating IP from the external network(via DC Gateway)

Pass Criteria:
==================================
Topology created and Open Flow channel is established between VSwitches.
External network and subnets are created successfully
Internal networks are created successfully
Router created successfully and the association of internal network should succeed
L3Vpn gets created association to external network is successful.
Floating ip is
Floating IP is created and updated in the flow table

Check for fixed ip in the flow<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Fails here

 

Logs attached

==================================

 

 Comments   
Comment by Chetan Arakere Gowdru [ 17/Apr/19 ]

FIP created is
openstack server add floating ip nat_net_1_vm_1 100.100.100.10
 
DNAT flows are also there for tis FIP
 cookie=0x8000004, duration=0.023s, table=25, n_packets=0, n_bytes=0, priority=10,ip,dl_dst=fa:16:3e:4b:27:c6,nw_dst=100.100.100.10 actions=set_field:10.1.1.7->ip_dst,write_metadata:0x30d40/0xfffffe,goto_table:27
 cookie=0x8000004, duration=0.023s, table=26, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d40/0xfffffe,nw_src=10.1.1.7 actions=set_field:100.100.100.10->ip_src,write_metadata:0x30d4a/0xfffffe,goto_table:28
 
Can you let me know why you are looking for other IP
 
[jenkins@sandbox-55221-4-2-devstack-queens-0 ~]>' does not contain '100.100.100.24'

Comment by Jaya Priyadarshini [ 22/Apr/19 ]

openstack router set nat_router --external-gateway nat_ext_11 --disable-snat
openstack router show nat_router
openstack subnet show "nat_ext_sub_net_1" | grep " id " | awk '{print $4}'
openstack router set nat_router --external-gateway nat_ext_11 --fixed-ip subnet=04bba026-1050-4758-8a73-8c7da8c37109,ip-address=100.100.100.24
openstack floating ip create nat_ext_11
openstack server add floating ip nat_net_1_vm_1 100.100.100.3

Comment by Jaya Priyadarshini [ 22/Apr/19 ]

Actually, at step 6 in the steps to repro,, we are Updateing the router with external network(associate external gateway with router,SNAT=false, single ExtIP)

we are grepping for this fixed ip in the flows, and this ip is missing.

Comment by Chetan Arakere Gowdru [ 22/Apr/19 ]

ACTUAL_BUNDLE_URL=https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/karaf/0.10.1-SNAPSHOT/karaf-0.10.1-20190422.034344-480.zip

Comment by Jaya Priyadarshini [ 23/Apr/19 ]

Hi Chetan, 

When i see in teardown debugs, we can see that the extip[100.100.100.24] is present and teardown was executed 2-3 minutes after the actual testcase verification.

Comment by Chetan Arakere Gowdru [ 28/May/19 ]

Neon Fix - https://git.opendaylight.org/gerrit/81724

Master(sodium) fix - https://git.opendaylight.org/gerrit/#/c/81926/

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