+++ This bug was initially created as a clone of Bug #1809368 +++ 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.
This already happened. I just need there to be a bug to appease the bot.
(In reply to Dan Winship from comment #1) > This already happened. I just need there to be a bug to appease the bot. oh, but apparently I don't have to cheat; we can merge the 4.4 fix with this still at MODIFIED so, for QE: the thing to verify is that kube-controller-manager's command-line arguments don't include IPv6DualStack in the --feature-gates
Confirmed with payload: 4.5.0-0.nightly-2020-03-06-190457, the issue has fixed: [root@dhcp-140-138 roottest]# oc rsh -n openshift-kube-controller-manager po/kube-controller-manager-ip-10-0-135-80.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" ],
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 (OpenShift Container Platform 4.5 image release 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:2409