-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.12.0, 4.11.z
-
+
-
None
-
MCO Sprint 237
-
1
-
Rejected
-
False
-
Description of problem:
machine config pool selection will be failed when single node has master+custom roles, controller logged the error but node is not marked as degraded, end user does not know this error. no config can be applied on the node
Version-Release number of selected component (if applicable):
4.12. 4.11.z
Steps to Reproduce:
1. setup SNO cluster 2. create custom mcp 3. add custom mcp label on the node 4. check mcc pod log to see the error message about pool selection 5. create mc to apply config
Actual results:
node state is good, the single node cannot be assigned to any mcp
Expected results:
node can be marked as degraded with error message
Additional info: