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

Bug 1809368

Summary: [4.4] bump openshift/api to remove IPv6DualStack feature flag
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: kube-controller-managerAssignee: Maciej Szulik <maszulik>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1809369 1809372 (view as bug list) Environment:
Last Closed: 2020-05-04 11:44:14 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: 1809369    
Bug Blocks:    

Description Dan Winship 2020-03-02 23:30:24 UTC 
There are bugs with the IPv6DualStack feature flag in 1.17/4.4 even in single-stack clusters. Bug 1794376 removed it from openshift/api and updated cluster-kube-apiserver-operator but didn't update cluster-kube-controller-manager-operator so we were still setting that flag for kcm.
Comment 4 zhou ying 2020-03-09 01:45:09 UTC 
Confirmed with payload: 4.4.0-0.nightly-2020-03-08-213224, the issue has fixed:

[root@dhcp-140-138 ~]# oc rsh -n openshift-kube-controller-manager po/kube-controller-manager-ip-10-0-136-132.us-east-2.compute.internal

sh-4.2# cat  /etc/kubernetes/static-pod-resources/configmaps/config/config.yaml | python -m json.tool
{
 ...
        "feature-gates": [
            "RotateKubeletServerCertificate=true",
            "SupportPodPidsLimit=true",
            "NodeDisruptionExclusion=true",
            "ServiceNodeExclusion=true",
            "SCTPSupport=true",
            "LegacyNodeRoleBehavior=false"
        ],
Comment 6 errata-xmlrpc 2020-05-04 11:44:14 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-2020:0581