Bug 1568311

Summary: [Netvirt] Connectivity from non-FIP instances (snat) to an external IP fails when using multiple routers
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
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, jluhrsen, lmarsh, mkolesni, nyechiel, oblaut, tjamrisk
Target Milestone: z1Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Netvirt
Fixed In Version: opendaylight-8.3.0-1.el7ost Doc Type: Known Issue
Doc Text:
Layer 3 connectivity between nova instances across multiple subnets may fail when an instance without a floating IP tries to reach another instance that has a floating IP on another router. This occurs when nova instances are spread across multiple compute nodes. There is no suitable workaround for this issue.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-19 13:53:05 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:
Bug Depends On:    
Bug Blocks: 1528948    
Description Flags
Robot Log none

Description Itzik Brown 2018-04-17 08:31:41 UTC
Created attachment 1422944 [details]
Robot Log

Description of problem:
When running the OpenDaylight external_network.robot test on HA setup - it fails.
Instances without FIP connected to one router are unable to connect to external IP.
Instance on another router is able to connect to an external IP

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

How reproducible:

Steps to Reproduce:
1. Run https://github.com/opendaylight/integration-test/blob/master/csit/suites/openstack/connectivity/external_network.robot

Actual results:

Expected results:

Additional info:

Comment 17 errata-xmlrpc 2018-07-19 13:53:05 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.