Bug 1309803

Summary:	openvswitch 2.4 Does Not Support IPv6 Endpoints for VXLAN/GRE Tunnels
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	openvswitch	Assignee:	Thadeu Lima de Souza Cascardo <cascardo>
Status:	CLOSED DUPLICATE	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	aloughla, apevec, chrisw, nyechiel, rhos-maint, rkhan, yeylon
Target Milestone:	---
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-03 14:54:53 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:
Bug Depends On:	1100360, 1283886
Bug Blocks:

Description Dan Sneddon 2016-02-18 18:15:07 UTC

Description of problem:
openvswitch does not support IPv6 tunnel endpoints in version 2.4. Although version 2.6 does support IPv6 tunnels, it also requires a new kernel.

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

How reproducible:
100%

Steps to Reproduce:
1. Deploy Red Hat OpenStack Platform with IPv6 network isolation and VXLAN tunnels
2.
3.

Actual results:
Open vSwitch will not start properly, and cannot handle IPv6 endpoints for tunnels.

Expected results:
Open vSwitch should handle an IPv6 underlay network.

Additional info:
The 2.6 version of Open vSwitch will also require a newer kernel, so there is a dependency on bumping the RHEL version in addition to upgrading OVS before we can support IPv6 tunneling endpoints.

The current workaround involves using and isolated IPv4 network for tunneling, even if IPv6 is used on other networks.

Comment 2 Thadeu Lima de Souza Cascardo 2016-03-03 13:44:08 UTC

Hi, Dan.

We track this with a bug of our own, for RHEL. Should someone in your team be assigned to it?

Regards.
Cascardo.

Comment 3 Nir Yechiel 2016-03-03 14:54:53 UTC


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