+++ This bug was initially created as a clone of Bug #1809372 +++ 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 machine-config-operator so we were still setting that flag for kubelet
*** This bug has been marked as a duplicate of bug 1809372 ***
not a dup, this was the 4.4 clone
Verified to get fixed on $ oc version Client Version: openshift-clients-4.3.0-201910250623-79-g5d15fd52 Server Version: 4.4.0-0.nightly-2020-03-16-034024 Kubernetes Version: v1.17.1 No more `IPv6DualStack feature flag ` $ oc get nodes -o name | xargs -I % sh -c 'oc debug % -- chroot /host cat /etc/kubernetes/kubelet.conf' Starting pod/ip-10-0-137-17us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ... Starting pod/ip-10-0-141-12us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ... Starting pod/ip-10-0-144-96us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ... Starting pod/ip-10-0-158-32us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ... Starting pod/ip-10-0-170-78us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ... Starting pod/ip-10-0-175-115us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1 authentication: x509: clientCAFile: /etc/kubernetes/kubelet-ca.crt anonymous: enabled: false cgroupDriver: systemd cgroupRoot: / clusterDNS: - 172.30.0.10 clusterDomain: cluster.local containerLogMaxSize: 50Mi maxPods: 250 kubeAPIQPS: 50 kubeAPIBurst: 100 rotateCertificates: true runtimeCgroups: /system.slice/crio.service serializeImagePulls: false staticPodPath: /etc/kubernetes/manifests systemCgroups: /system.slice systemReserved: cpu: 500m memory: 1Gi ephemeral-storage: 1Gi featureGates: LegacyNodeRoleBehavior: false NodeDisruptionExclusion: true RotateKubeletServerCertificate: true SCTPSupport: true ServiceNodeExclusion: true SupportPodPidsLimit: true serverTLSBootstrap: true Removing debug pod ...
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