Bug 1945091

Summary: In k8s 1.21 bump Feature:IPv6DualStack tests are disabled
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: NetworkingAssignee: Dan Winship <danw>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: anbhat, trozet
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:56:48 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:

Description Maciej Szulik 2021-03-31 10:40:16 UTC
In https://github.com/openshift/kubernetes/pull/641 which brings k8s 1.21 I disabled all of IP dual stack tests, since the current setup we have is not supporting it.

Comment 1 Maciej Szulik 2021-03-31 11:17:23 UTC
Similar skips were added in https://github.com/openshift/origin/pull/26039

Comment 3 Dan Winship 2021-04-01 13:29:36 UTC
(The tests were already skipped, but the skip rule is being moved from [Disabled:Alpha] to [Disabled:Broken], since the feature is no longer alpha.)

https://github.com/openshift/origin/pull/25818 adds support to openshift-tests for autodetecting whether the cluster is IPv4/IPv6/dual-stack, and once that merges we can merge https://github.com/openshift/kubernetes/pull/565, which un-annotates the tests, while also explicitly skipping them in the local openshift/kubernetes e2e.

Comment 7 zhaozhanqi 2021-06-01 08:05:21 UTC
Move to verified

Comment 10 errata-xmlrpc 2021-07-27 22:56:48 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

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