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
at the end of the process a few nodes (not all of them) still contains:
after a successful update UpdateInProgress taint is correctly removed
on the node we see:
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.
Ravi, can you please look at this bug as this seems like regression from PR https://github.com/openshift/machine-config-operator/pull/2686
in machine-config-controller logs we see:
I1222 06:42:29.011398 1 status.go:90] Pool worker: All nodes are updated with rendered-worker-f283e2dd057330b8c4d288348ae5b5cb
*** Bug 2034901 has been marked as a duplicate of this bug. ***
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days