-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.9.z, 4.9.0
-
Low
-
None
-
False
-
This is a clone of issue OCPBUGS-2173. The following is the description of the original issue:
—
Description of problem:
When a custom machineConfigPool is created and no node is associated with it, the mcp remains at 0% progress.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Create a custom mcp: ~~~ cat << EOF | oc create -f - apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfigPool metadata: name: custom spec: machineConfigSelector: matchExpressions: - {key: machineconfiguration.openshift.io/role, operator: In, values: [worker,custom]} nodeSelector: matchLabels: node-role.kubernetes.io/custom: "" EOF ~~~
Actual results:
The mcp is visible from the from "Administrator view > Cluster Settings > Details" at 0% progress
Expected results:
It shouldn't be stuck at 0%
Additional info:
- clones
-
OCPBUGS-2173 [release-4.9] machineConfigPool without nodes assigned stuck at 0% progress
- Closed
- is blocked by
-
OCPBUGS-2173 [release-4.9] machineConfigPool without nodes assigned stuck at 0% progress
- Closed
- links to