-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15.0
-
+
-
No
-
MCO Sprint 246
-
1
-
False
-
-
N/A: tech preview feature fix in same release
-
Release Note Not Required
-
In Progress
When we apply a machine config with additional ssh key info, this action only needs to uncordon the node, when uncordon is happening, condition Cordoned = True. it will make the user confuse. maybe we can refine this design to show status of cordon/uncordon separately
lastTransitionTime: '2023-11-28T16:53:58Z' message: 'Action during previous iteration: (Un)Cordoned node. The node is reporting Unschedulable = false' reason: UpdateCompleteCordoned status: 'False' type: Cordoned
- relates to
-
MCO-452 [tech-preview] Proper state reporting when the MCO changes state
- Closed
-
MCO-795 Merge Upgrade Monitoring into the MCO
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update