-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
False
-
None
Description of issue:
User has randomly invoked the "Edit machine pool" option for OSD,ROSA HCP clusters from cluster list. The compute node count drop-down shown as either disabled or holding a wrong definition as zero from the Edit machine pools.
See the recordings.ComputeNodeCountWrongDefinition.mp4
How reproducible:
Always
Steps to reproduce:
- Launch OCM Staging.
- Go to cluster list and select a ready HCP cluster.
- Click on "Edit machine pools" menu and close it.
- Repeat step 2 & 3 with OSD or OSD trail cluster.
- See the compute node definitions from the "Edit machine pools".
- Repeat step 2 & 3 with HCP cluster again.
- See the compute node definitions from the "Edit machine pools".
Actual results:
When user randomly invoked "Edit machine pools" dialog from OSD, HCP clusters,
in step 5, wrong compute node count definition as zero for OSD.
in step 7, the compute node count field itself disabled for HCP.
Expected results:
Compute node count definition should be loaded freshly in "Edit machine pool" dialog according to the selected Cluster.
There should be any wrong definition in Compute node count value or field shouldn't be disabled.