When we enable OCL in the worker pool, and we apply a new MC the MC is correctly applied,  but some MCNs are not reporting the right MC in their .spec.configVersion.desired field.

If we don't use OCL the MCN field is correctly updated.

    

$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.nightly-2024-08-19-165854   True        False         6h4m    Cluster version is 4.17.0-0.nightly-2024-08-19-165854

    

Always
    

    1. Enable OCL in the worker pool
    2. Wait until the OCL image is applied
    3. Create a MC, for example
    
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: worker
  name: test-machine-config-1
spec:
  config:
    ignition:
      version: 3.1.0
    storage:
      files:
      - contents:
          source: data:text/plain;charset=utf-8;base64,dGVzdA==
        filesystem: root
        mode: 420
        path: /etc/test-file-1.test

    3. Check the value that the MCN are reporting in the field .spec.configVersion.desired 
    

    The value of .spec.confi.gVersion.desired is not updated in some MCN
    
$ oc --kubeconfig=/tmp/aa4 get node ip-10-0-64-142.us-east-2.compute.internal -o jsonpath='{.metadata.annotations.machineconfiguration\.openshift\.io/desiredConfig}'
rendered-worker-58863917c8b42a0cffab0c9639f31d35
$ oc --kubeconfig=/tmp/aa4 get machineconfignode ip-10-0-64-142.us-east-2.compute.internal -o jsonpath='{.spec.configVersion.desired}'
rendered-worker-d7b9167918f0dbb3f752919bb33a4271 
    
$ oc get machineconfignode
NAME                                        UPDATED   UPDATEPREPARED   UPDATEEXECUTED   UPDATEPOSTACTIONCOMPLETE   UPDATECOMPLETE   RESUMED
ip-10-0-31-25.us-east-2.compute.internal    True      False            False            False                      False            True
ip-10-0-44-74.us-east-2.compute.internal    True      False            False            False                      False            True
ip-10-0-64-142.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-82-233.us-east-2.compute.internal   True      False            False            False                      False            False
ip-10-0-91-230.us-east-2.compute.internal   True      False            False            False                      False            True

    

    The values should be updated in MCN
    

The machineconfignode resources are not included in the must-gather file, so we added it manually to the tar file.