Bug 871569 - IPv6 support for OpenShift Enterprise
Summary: IPv6 support for OpenShift Enterprise
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.10.0
Assignee: Ben Bennett
QA Contact:
URL:
Whiteboard:
: 1369726 1398359 (view as bug list)
Depends On: 1198780
Blocks: 1267746
TreeView+ depends on / blocked
 
Reported: 2012-10-30 18:02 UTC by Brenton Leanhardt
Modified: 2023-09-14 23:57 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-18 20:54:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1063381 1 None None None 2023-09-14 02:03:25 UTC
Red Hat Bugzilla 1080725 0 medium CLOSED [RFE][Tracker] RHEV IPv6 support 2021-04-13 18:00:32 UTC
Red Hat Bugzilla 1080726 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1081021 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Knowledge Base (Solution) 2807071 0 None None None 2018-06-22 20:55:17 UTC

Internal Links: 1063381 1080725 1080726 1081021

Description Brenton Leanhardt 2012-10-30 18:02:29 UTC
Description of problem:
Several packages have been flagged for possible incompatibility with ipv6.  This bug will document those packages.

Comment 12 Eric Rich 2014-03-27 12:36:48 UTC
Can OSE be considered IPv6 tolerant:  meaning your product does not create or use the addresses, but your product will not break if someone introduces an IPv6 
in manually.

- IE: will it break if a Node or Broker has an external IPv6 address? 
    - I think so, base on assumptions we make in the underling code on IPv4 address. 

However if this works in theory the Broker's and Nodes could be IPv6 to IPv4 gateways (in a way).

Comment 22 Brenton Leanhardt 2014-10-27 18:31:08 UTC
php-pecl-xdebug	 	usr/lib/php/modules/xdebug.so on i686 uses function gethostbyname, which may impact IPv6 support

php-pecl-xdebug	 	usr/lib/php/modules/xdebug.so on i686 uses function inet_aton, which may impact IPv6 support

php-pecl-xdebug	 	usr/lib64/php/modules/xdebug.so on x86_64 uses function gethostbyname, which may impact IPv6 support

php-pecl-xdebug	 	usr/lib64/php/modules/xdebug.so on x86_64 uses function inet_aton, which may impact IPv6 support

Comment 23 Josep 'Pep' Turro Mauri 2015-03-04 20:29:06 UTC
Bug 1198780 refers to a problem with Java based cartridges: Java apparently relies on /proc/net/if_inet6 being readable to determine if it can talk IPv6, and this is forbidden by SELinux in OSE

Comment 26 Dan McPherson 2016-08-24 11:19:22 UTC
*** Bug 1369726 has been marked as a duplicate of this bug. ***

Comment 27 Dan McPherson 2016-11-24 14:53:10 UTC
*** Bug 1398359 has been marked as a duplicate of this bug. ***

Comment 28 Flavio Percoco 2016-11-24 15:01:08 UTC
I didn't realize this bug existed already and I went ahead and opened one, which was of course closed as duplicated :D

Here's the description I used in the one that I created (just adding it here as complementary info):

What is the nature and description of the request?  

IPv6 is a critical feature for OpenStack. It was a release feature for OSP8 and there are several customers relying on it. Kubernetes doesn’t fully support IPv6 yet. There’s ongoing work but it is still very rough. The initial support for IPv6 was released as part of Kubernetes 1.3, which allows pods to be addressed via IPv6 addresses. Support for services has yet to be added.

The ami is to have end-to-end support for IPv6.

Why does the customer need this? (List the business requirements here)

OpenStack has end-to-end support for IPv6 and its customers rely on it. For OpenStack to be successfully deployed and shipped on OpenShift, it needs to be able to process IPv6 requests properly using OpenShift network layer.

Comment 29 wibrown@redhat.com 2016-11-24 21:24:51 UTC
I want to just expand on what Flavio has said, and ask that IPV6 *only* be a requirement of this feature. Too often we see systems get IPV4/IPV6 dual stack working, but IPV6 only is ignored and doesn't work. IE a requirement for this feature to be considered complete is the ability to run a cluster only with IPV6 addressing.

Comment 40 Red Hat Bugzilla 2023-09-14 23:57:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.