Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1587967

Summary:	[Netvirt] Connectivity from non-FIP instances to an external IP fails when using VLAN setup
Product:	Red Hat OpenStack	Reporter:	Itzik Brown <itbrown>
Component:	opendaylight	Assignee:	Aswin Suryanarayanan <asuryana>
Status:	CLOSED ERRATA	QA Contact:	Tomas Jamrisko <tjamrisk>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	aadam, asuryana, lmarsh, mkolesni, nyechiel, tjamrisk, wznoinsk
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Netvirt
Fixed In Version:	opendaylight-8.3.0-1.el7ost	Doc Type:	Bug Fix
Doc Text:	When the NAPT switch is selected on a node without any port in a VLAN network, all flows required are not programmed. External connectivity fails for all VMs in the network that don’t have floating IP addresses. This update adds a pseudo port to create a VLAN footprint in the NAPT switch for VLANs that are part of the router. External connectivity works for VMs without floating IP addresses.	Story Points:	---
Clone Of:		Environment:	N/A
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:
Embargoed:

Description Itzik Brown 2018-06-06 11:25:43 UTC

Description of problem:
When having an instance without floating IP hosted on a node other than the one that the NAPT switch is hosted - there is no connectivity to an external IP.


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

How reproducible:


Steps to Reproduce:
1. Follow the description.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 13 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.

https://access.redhat.com/errata/RHBA-2018:2215