-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The day2 machinepool's instance and machineset is not created for classic cluster
How reproducible:
100%
Env: int and stage
Steps
- create a classic ROSA cluster with 4.18.7
- Wait for it ready
- Create a machinepool for it
- Wait for 5 mins
- Check the machine set
Actual result:
There is no instance/machineset for the new created machinepool
rosa create machinepool -c ying-test W: The current version (1.2.51) is not up to date with latest rosa cli released version (1.2.52). W: It is recommended that you update to the latest version. I: Enabling interactive mode ? Machine pool name: mp-1 ? Enable autoscaling: No ? Replicas: 1 I: Checking available instance types for machine pool 'mp-1' ? Instance type (default = 'm5.xlarge'): m5.xlarge ? Labels (optional): ? Taints (optional): ? Use spot instances: No ? Tags (optional): ? Root disk size (GiB or TiB): 300 GiB I: Machine pool 'mp-1' created successfully on cluster 'ying-test' I: To view the machine pool details, run 'rosa describe machinepool --cluster ying-test --machinepool mp-1' I: To view all machine pools, run 'rosa list machinepools --cluster ying-test' oc get machineset -n openshift-machine-api --kubeconfig=kubeconfig NAME DESIRED CURRENT READY AVAILABLE AGE ying-test-tcgns-worker-us-west-2a 2 2 2 2 46m
Expected result:
There should be machine set for the new machine pool in reasonable time.
Additional information:
Wait for about 30 mins, the machine set is created
oc get machineset -n openshift-machine-api --kubeconfig=kubeconfig NAME DESIRED CURRENT READY AVAILABLE AGE ying-test-tcgns-infra-us-west-2a 2 2 2 2 27m ying-test-tcgns-mp-1-us-west-2a 1 1 1 1 14m ying-test-tcgns-worker-us-west-2a 2 2 2 2 68m
The result is same for GCP/AWS OSD clusters
