Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-7726

WMCO kubelet version not matching OCP payload's one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Minor Minor
    • 4.11.z
    • 4.12
    • Windows Containers
    • None
    • Low
    • No
    • 0
    • WINC - Sprint 232, WINC - Sprint 233
    • 2
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-7336. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-6635. The following is the description of the original issue:
      —
      Description of problem:

      When displaying the cluster nodes (oc get nodes), we can observe that the Windows workers have a different "patch" version than the Linux workers/master nodes:

$ oc get nodes
NAME                                STATUS   ROLES                  AGE    VERSION
vsrasouli-2601-skvvn-master-0       Ready    control-plane,master   136m   v1.25.4+77bec7a
vsrasouli-2601-skvvn-master-1       Ready    control-plane,master   136m   v1.25.4+77bec7a
vsrasouli-2601-skvvn-master-2       Ready    control-plane,master   136m   v1.25.4+77bec7a
vsrasouli-2601-skvvn-worker-cwpxb   Ready    worker                 123m   v1.25.4+77bec7a
vsrasouli-2601-skvvn-worker-x42w6   Ready    worker                 123m   v1.25.4+77bec7a
winworker-mjwmg                     Ready    worker                 99m    v1.25.0-2653+a34b9e9499e6c3
winworker-nz4fb                     Ready    worker                 96m    v1.25.0-2653+a34b9e9499e6c3

The issue seems to be caused by the fact that openshift/kubernetes (https://github.com/openshift/kubernetes/tags) is not synchronizing the tags from the upstream kubernetes repository (https://github.com/kubernetes/kubernetes/tags), which causes the display of a wrong kubelet version even though the code is pointing at the right branch and dependencies (so it is more of a cosmetic error, but it needs to be solved as it might impact to several releases)

      Version-Release number of selected component (if applicable):

      $ oc get clusterversion
NAME      VERSION       AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-rc.8   True        False         122m    Cluster version is 4.12.0-rc.8

$ oc get cm -n openshift-windows-machine-config-operator 
NAME                                   DATA   AGE
kube-root-ca.crt                       1      109m
openshift-service-ca.crt               1      109m
windows-machine-config-operator-lock   0      108m
windows-services-7.0.0-c9c49be         2      108m

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy a OVN hybrid overlay IPI cluster
2. Install WMCO and deploy a Windows Machineset
3. Wait for the nodes to join the cluster
4. Display the nodes: oc get nodes

      Actual results:

      Linux workers/masters have a kubelet version v1.25.4+77bec7a while the Windows workers use v1.25.0-2653+a34b9e9499e6c3

      Expected results:

      Both, Linux and Windows nodes have the very same kubelet version: v1.25.4+77bec7a and v1.25.4-2653+a34b9e9499e6c3

      Additional info:

       

              paravindh Aravindh Puthiyaparambil (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Aharon Rasouli Aharon Rasouli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: