++

Hi Srinivas,

Since this TC is related to Floating IP “Verify Floating Ip Provision And Reachability From External Network Via Neutron Router Through L3vpn”,  It will looks for Floating IP(100.100.100.7) flow installation on the VM’s DPN(which is associated with Floating-ip).

Currently, it grep our flows on SNAT-IP(100.100.100.24) and the SNAT-IP can be installed on any on the DPN(which gets elected as Napt-Switch).

Request this script requires to be updated accordingly.

Thanks,

Chetan

Raised a review.

https://git.opendaylight.org/gerrit/c/integration/test/+/86837

Hi Chetan,

Thanks for the analysis.

What I see here is 100.100.100.24 is configured for the router:

openstack router set nat_router --external-gateway nat_ext_11 --fixed-ip subnet=aa694004-353f-400d-b54c-e44babc1a454,ip-address=100.100.100.24

So checking for 100.100.100.24 is correct, but as you said there needs to be a delay.

In post logs I do see the entry:

cookie=0x8000003, duration=15.636s, table=21, n_packets=0, n_bytes=0, priority=42,ip,metadata=0x30d52/0xfffffe,nw_dst=100.100.100.24 actions=goto_table:44

I will correct the script.

Hi Srinivas,

I see two issue here.

I think we need to a little delay before checking the flow post “openstack floating-ip set”. I can see the required flows present in PostRun logs as part of the same TC failure and not seen on the flow-dumps collected immediately.

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1-t4-k13-k2-k1-k2-k1-k12-k5

cookie=0x8000004, duration=5.523s, table=25, n_packets=0, n_bytes=0, priority=10,ip,dl_dst=fa:16:3e:9f:35:8f,nw_dst=100.100.100.7 actions=set_field:10.1.1.9->ip_dst,write_metadata:0x30d40/0xfffffe,goto_table:27

cookie=0x8000004, duration=5.523s, table=26, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d40/0xfffffe,nw_src=10.1.1.9 actions=set_field:100.100.100.7->ip_src,write_metadata:0x30d52/0xfffffe,goto_table:28

cookie=0x8000006, duration=17.447s, table=26, n_packets=0, n_bytes=0, priority=5,ip,metadata=0x30d40/0xfffffe actions=set_field:0x11171->tun_id,group:225000

cookie=0x8000004, duration=5.523s, table=27, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d40/0xfffffe,nw_dst=10.1.1.9 actions=load:0->NXM_OF_IN_PORT[],resubmit(,21)

cookie=0x8000004, duration=5.523s, table=28, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d52/0xfffffe,nw_src=100.100.100.7 actions=load:0->NXM_OF_IN_PORT[],set_field:fa:16:3e:9f:35:8f->eth_src,resubmit(,21)

Also, Can you check why script looking for ip '100.100.100.24' as the VM is associated with floating-ip ‘100.100.100.7’.

openstack floating ip set --port 59174530-c19f-445c-b75e-2f94be2f5bdf 100.100.100.7

[jenkins@releng-18075-227-2-devstack-rocky-0 ~]>' does not contain '100.100.100.24'

Thanks,

Chetan

Hi Chetan,

Can you please see the failure:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1

Thanks,

Srinivas

+91-9243478719

Right. Should be looking for Floating IP flows(100.100.100.7) on the DPN where the VM having IP(10.1.1.9 in this case) resides and its port got associated with floating-ip.

openstack server show nat_net_1_vm_1 | grep "addresses" | awk '{print $4}' | cut -d"=" -f 2

output - 10.1.1.9

openstack port list | grep "ip_address='10.1.1.9'" | awk '{print $2}' | cut -d"=" -f 2

output - 59174530-c19f-445c-b75e-2f94be2f5bdf

openstack floating ip set --port 59174530-c19f-445c-b75e-2f94be2f5bdf 100.100.100.7

Thanks,

Chetan

Hi Chetan,

You mean to say that I should be looking for VM IP (here 100.100.100.7) for this testcase and not the SNAT IP.

++

Hi Srinivas,

Since this TC is related to Floating IP “Verify Floating Ip Provision And Reachability From External Network Via Neutron Router Through L3vpn”,  It will looks for Floating IP(100.100.100.7) flow installation on the VM’s DPN(which is associated with Floating-ip).

Currently, it grep our flows on SNAT-IP(100.100.100.24) and the SNAT-IP can be installed on any on the DPN(which gets elected as Napt-Switch).

Request this script requires to be updated accordingly.

Thanks,

Chetan

Raised a review.

https://git.opendaylight.org/gerrit/c/integration/test/+/86837

Hi Chetan,

Thanks for the analysis.

What I see here is 100.100.100.24 is configured for the router:

openstack router set nat_router --external-gateway nat_ext_11 --fixed-ip subnet=aa694004-353f-400d-b54c-e44babc1a454,ip-address=100.100.100.24

So checking for 100.100.100.24 is correct, but as you said there needs to be a delay.

In post logs I do see the entry:

cookie=0x8000003, duration=15.636s, table=21, n_packets=0, n_bytes=0, priority=42,ip,metadata=0x30d52/0xfffffe,nw_dst=100.100.100.24 actions=goto_table:44

I will correct the script.

Hi Srinivas,

I see two issue here.

I think we need to a little delay before checking the flow post “openstack floating-ip set”. I can see the required flows present in PostRun logs as part of the same TC failure and not seen on the flow-dumps collected immediately.

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1-t4-k13-k2-k1-k2-k1-k12-k5

cookie=0x8000004, duration=5.523s, table=25, n_packets=0, n_bytes=0, priority=10,ip,dl_dst=fa:16:3e:9f:35:8f,nw_dst=100.100.100.7 actions=set_field:10.1.1.9->ip_dst,write_metadata:0x30d40/0xfffffe,goto_table:27

cookie=0x8000004, duration=5.523s, table=26, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d40/0xfffffe,nw_src=10.1.1.9 actions=set_field:100.100.100.7->ip_src,write_metadata:0x30d52/0xfffffe,goto_table:28

cookie=0x8000006, duration=17.447s, table=26, n_packets=0, n_bytes=0, priority=5,ip,metadata=0x30d40/0xfffffe actions=set_field:0x11171->tun_id,group:225000

cookie=0x8000004, duration=5.523s, table=27, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d40/0xfffffe,nw_dst=10.1.1.9 actions=load:0->NXM_OF_IN_PORT[],resubmit(,21)

cookie=0x8000004, duration=5.523s, table=28, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x30d52/0xfffffe,nw_src=100.100.100.7 actions=load:0->NXM_OF_IN_PORT[],set_field:fa:16:3e:9f:35:8f->eth_src,resubmit(,21)

Also, Can you check why script looking for ip '100.100.100.24' as the VM is associated with floating-ip ‘100.100.100.7’.

openstack floating ip set --port 59174530-c19f-445c-b75e-2f94be2f5bdf 100.100.100.7

[jenkins@releng-18075-227-2-devstack-rocky-0 ~]>' does not contain '100.100.100.24'

Thanks,

Chetan

Hi Chetan,

Can you please see the failure:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/227/robot-plugin/log_full.html.gz#s1-s1

Thanks,

Srinivas

+91-9243478719