Description of problem: because new drain controller is introduced, node drain logs are moved to mcc pod from mcd pod , but in alert message, mcd pod info is still there, customer cannot use command in that message to checkout drain error details "annotations": { "message": "Drain failed on ip-10-0-50-132.us-east-2.compute.internal , updates may be blocked. For more details: oc logs -f -n openshift-machine-config-operator machine-config-daemon-98d6b -c machine-config-daemon" } Version-Release number of MCO (Machine Config Operator) (if applicable): 4.11.0-0.nightly-2022-05-20-153751 Platform (AWS, VSphere, Metal, etc.): All Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)? (Y/N/Not sure): Yes How reproducible: Steps to Reproduce: https://polarion.engineering.redhat.com/polarion/redirect/project/OSE/workitem?id=OCP-43279 Actual results: alert message contains the command that get error detail from mcd pod log Expected results: alert message should be updated to get drain error details from mcc pod log
*** Bug 2089686 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. https://access.redhat.com/errata/RHSA-2022:5069