Bug 1843347 - The machineconfig does not process when some nodes' status is set SchedukeDisabled in advance.
Summary: The machineconfig does not process when some nodes' status is set SchedukeDis...
Keywords:
Status: CLOSED DUPLICATE of bug 1780318
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Antonio Murdaca
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-03 05:26 UTC by ryoji noma
Modified: 2023-10-06 20:23 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-23 16:50:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description ryoji noma 2020-06-03 05:26:07 UTC 
The machineconfig does not process when some node status is set ScheduleDisabled by oc adm cordon in advance.
 
Version-Release number of selected component (if applicable):
 
ocp4.2
 
How reproducible:
 
Steps to Reproduce:
1.$ oc adm cordon ${node}
2.$ oc apply -f ${MachineConfigFile}
 
Actual results:
 
The machineconfig does not process updating.
 
Expected results:
 
The machineconfig should process updating. Or it should output some errors if this behavior is intended.
 
Additional info:
 
The machineconfig resumes processing when executing oc adm uncordon.
Comment 1 Antonio Murdaca 2020-06-16 12:58:00 UTC 
Adding UpcomingSprint as this won't make the current sprint. We'll try to work on this bug in the next sprint.
Comment 2 Antonio Murdaca 2020-06-23 16:50:30 UTC 
it's very likely because the MCD wasn't running on the node you performed the cordon on. This might be a duplicate of, so check with latest releases please.

*** This bug has been marked as a duplicate of bug 1780318 ***
Note You need to log in before you can comment on or make changes to this bug.