Description of problem: While debugging the 1.18 rebase Stefan found: Mar 25 07:17:51 ip-10-0-158-139 hyperkube[1300]: W0325 07:17:51.773950 1300 codec.go:118] using lenient decoding as strict decoding failed: strict decoder error for kind: KubeletConfiguration Mar 25 07:17:51 ip-10-0-158-139 hyperkube[1300]: : v1beta1.KubeletConfiguration.SerializeImagePulls: ReadObject: found unknown field: runtimeCgroups, error found in #10 byte of ...|meCgroups":"/system.|..., bigger context ...|ds":250,"ro> This is a serialization issue, and a misconfiguration in: https://github.com/openshift/machine-config-operator/pull/1540/files Version-Release number of selected component (if applicable): 4.5 and 4.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
verified with 4.5.0-0.nightly-2020-03-30-163144 >>>>>>>>>>>>>>>> pruan@desktop ~ $ oc debug node/ip-10-0-165-193.us-east-2.compute.internal Starting pod/ip-10-0-165-193us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` chroot /host Pod IP: 10.0.165.193 If you don't see a command prompt, try pressing enter. sh-4.2# chroot /host sh-4.4# cat /etc/kubernetes/kubelet.conf 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 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
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:2409