Description of the Problem

User has tried to create a non ccs OSD cluster with autoscaling enabled as well as minimum and  maximum worker or machine pool node limit i.e. 249 from the wizard side. Unfortunately the inline backend error thrown in cluster submission and which is unclear and confusing at the moment. The autoscaler definitions were not allowed to configure in nonccs OSD cluster flow as well as the node count calculation from the error message.  If it is really a restriction from backend then it should be reflected in wizard step i.e especially during the node count selection for the users.

See the recordings Screencast from 2024-11-11 15-24-22.mp4

How reproducible:

always

Steps to Reproduce:

1. Open OCM UI staging.
2. Open OSD wizard.
3. Select  Subscription type as "Annual: Fixed capacity subscription from Red Hat"
4. Select  Infrastructure type as "Red Hat cloud account".
5. Click "Next" and select cloud provider as "AWS" or "GCP"
6. Proceed to "Next" steps after filling required definitions.
7. Reach to "Default machine pool" step.
8. Enable the "Enable autoscaling"
9. Set the minimum node count and maximum node count as "249". (or max limit)
10. Proceed to "Next" steps after filling required definitions.
11. Click "Create cluster" in "Review and create" step.
12. See the behavior.

Actual results:

At step12, the backend has thrown inline error on the node count limit associated to cluster autoscaling. The error seems confusing as osd wizard for nonccs flow doesn't allow to configure any cluster autoscaling definition as well as the maximum node count (244) calculation in this context.

Expected results:

If there is a reason not to allow the max node count 244 by cluster autoscaler (because other backend factors) then, we should limit or restrict the user from selecting the unsupported count at default machine pool selection step in wizard