Description of problem:

Version-Release number of MCO (Machine Config Operator) (if applicable):

Platform (AWS, VSphere, Metal, etc.):

Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)?
(Y/N/Not sure): Y

How reproducible: ? (not on all the nodes)

Did you catch this issue by running a Jenkins job? If yes, please list:
1. Jenkins job: https://main-jenkins-csb-cnvqe.apps.ocp-c1.prod.psi.redhat.com/view/Upgrade-Pipelines/job/Upgrade-CNV-4.10-Scheduled/17/

2. Profile: ?

Steps to Reproduce:
1. during our tests we apply an ICSP that causes a new config to be rendered for our nodes
2. MCP starts applying it
3.

Actual results:
at the end of the process a few nodes (not all of them) still contains:

        "taints": [
            {
                "effect": "PreferNoSchedule",
                "key": "UpdateInProgress"
            }
        ]



Expected results:
after a successful update UpdateInProgress taint is correctly removed

Additional info:

on the node we see:
            "machineconfiguration.openshift.io/currentConfig": "rendered-worker-f283e2dd057330b8c4d288348ae5b5cb",
            "machineconfiguration.openshift.io/desiredConfig": "rendered-worker-f283e2dd057330b8c4d288348ae5b5cb",

on MCD logs:
I1222 06:34:39.073411    3396 update.go:1956] Update completed for config rendered-worker-f283e2dd057330b8c4d288348ae5b5cb and node has been successfully uncordoned
I1222 06:34:39.120947    3396 daemon.go:1283] In desired config rendered-worker-f283e2dd057330b8c4d288348ae5b5cb

but the node is still tainted.