Bug 1843347
| Summary: | The machineconfig does not process when some nodes' status is set SchedukeDisabled in advance. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | ryoji noma <rnoma> |
| Component: | Machine Config Operator | Assignee: | Antonio Murdaca <amurdaca> |
| Status: | CLOSED DUPLICATE | QA Contact: | Michael Nguyen <mnguyen> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.z | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-23 16:50:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Adding UpcomingSprint as this won't make the current sprint. We'll try to work on this bug in the next sprint. 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 *** |
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.