Bug 1609334

Summary: [Netvirt] ping to floating IP doesn't work, table=26 on compute doesn't get any packets
Product: Red Hat OpenStack Reporter: Waldemar Znoinski <wznoinsk>
Component: opendaylightAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED DUPLICATE QA Contact: Noam Manos <nmanos>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aadam, mkolesni, nyechiel
Target Milestone: z3Keywords: ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Netvirt
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2018-07-31 06:34:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldemar Znoinski 2018-07-27 15:30:27 UTC 
Description of problem:
Some Tempest tests fail reporting ping to floating IP of a VMs not working after 120seconds. In the same CI run some other scenario tests succeed.

Version-Release number of selected component (if applicable):
osp13, opendaylight-8.3.0-1

How reproducible:
In 20% of d/s CI tempest jobs

Steps to Reproduce:
1. deploy OSP13 z1
2. run tempest scenario tests 
3.

Actual results:
ping to tempest VMs fail

Expected results:
ping to work

Additional info:
log of a failing tempest test ran in CI:
https://url.corp.redhat.com/3bb4bfb

the rest of the logs in undercloud-0.tar.gz:/var/log/overcloud_capture or on the controller-0/1/2,compute-0/1 tar.gz files (too big files to attach here)

on a working setup the table=26 on copute the VM was spawned on receives packets, i.e.:
 cookie=0x8000004, duration=62595.014s, table=26, n_packets=20, n_bytes=1157, priority=10,ip,metadata=0x324b6/0xfffffe,nw_src=192.168.0.5 actions=set_field:10.0.0.219->ip_src,write_metadata:0x324b2/0xfffffe,goto_table:28


but during this failure:
 cookie=0x8000004, duration=140.585s, table=26, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x325ae/0xfffffe,nw_src=10.100.0.9 actions=set_field:10.0.0.218->ip_src,write_metadata:0x324b2/0xfffffe,goto_table:28
Comment 1 Aswin Suryanarayanan 2018-07-31 06:34:34 UTC 
The issue seems to be same as 1597236 . The flow is programmed with VPN id  -1. 

table=21, n_packets=0, n_bytes=0, priority=10,ip,metadata=0xfffffe/0xfffffe actions=goto_table:26

installInboundTerminatingServiceTblEntry : creating entry for Terminating Service Table for switch 106464498830738, routerId -1

*** This bug has been marked as a duplicate of bug 1597236 ***