Bug 1598399

Summary: [Netvirt] VM associated to vxlan network is not reachable because of ARP flow missing
Product: Red Hat OpenStack Reporter: Janki <jchhatba>
Component: opendaylightAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED ERRATA QA Contact: Tomas Jamrisko <tjamrisk>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aadam, asuryana, joflynn, jschluet, mkolesni, nyechiel
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Netvirt
Fixed In Version: opendaylight-8.3.0-2.el7ost Doc Type: Bug Fix
Doc Text:
Some flows were missing from the ARP table and the flow programming generated an error due to a missing group. As a result, L2 failed and affected most of the traffic. The flow programming now waits for the group to be added. The group is always present and L2 traffic succeeds.
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2018-08-29 16:20:16 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:
Attachments:
Description Flags
karaf logs, data dumps, ovs logs, flows, OS CLI outputs none

Description Janki 2018-07-05 10:44:46 UTC
Created attachment 1456749 [details]
karaf logs, data dumps, ovs logs, flows, OS CLI outputs

Description of problem:
When a VM is attached to vxlan network, its FIP is pingable.

Version-Release number of selected component (if applicable):
OSP13 + Oxygen

How reproducible:
sometimes

Steps to Reproduce:
1. Deploy ODL + OSP13
2. Create a VM attached to VxLAN network and 1 router
3. Ping FIP of the VM

Actual results:
Ping doesnot work

Expected results:
Ping should work

Additional info:
Initial analysis suggests an ARP flow missing in table=43 for OVS on compute-1 where the VM is hosted.

on datdd umps, grep -irn "arp.check.table.43.arp.request" shows we have five entires in config but only 4 in operational

ovs logs snippet - sending OFPBAC_BAD_OUT_GROUP error reply to OFPT_FLOW_MOD message

Comment 7 Joanne O'Flynn 2018-08-14 09:45:51 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 10 errata-xmlrpc 2018-08-29 16:20:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2598