Bug 2089686 - alert message of MCDDrainError needs to be updated for new drain controller
Summary: alert message of MCDDrainError needs to be updated for new drain controller
Keywords:
Status: CLOSED DUPLICATE of bug 2089687
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: MCO Bug Bot
QA Contact: Rio Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 09:00 UTC by Rio Liu
Modified: 2022-05-24 09:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-24 09:36:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rio Liu 2022-05-24 09:00:42 UTC
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

Comment 1 Sinny Kumari 2022-05-24 09:36:32 UTC

*** This bug has been marked as a duplicate of bug 2089687 ***


Note You need to log in before you can comment on or make changes to this bug.