Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2983

[Edit Cluster Autoscaling settings][Day 2]"Revert all to defaults" button disabled when there is a validation error in any of the fields.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Center-UI-Team, Core UI
    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Center Team Sprint 266

      Description of problem:

      The "Revert all to defaults" button that allow to reset the cluster autoscaling values to default value is disabled when there is any field contains validation error from the "Edit cluster autoscaling settings" model. This issue is only happens with day 2 i.e. the "Edit cluster autoscaling settings" model opened from machine pool tab of a cluster. The behavior is wrong. The "Revert all to defaults" button should be enabled for the user irrespective of the value of the fields and user should have an option to revert it back to the default ones including the value of the field(s) contains validation issue.

      See the attached recording Screen Recording 2025-01-27 at 3.17.45 PM.mov

      The issue hasn't reproduced in production env and hence suspecting it could be the change related to multiregion or recent fix went towards cluster autoscaler definitions. 

      How reproducible:

       Always

      Steps to reproduce:

      1. Launch OCM UI staging.
      2. Open a a cluster (ex: OSD or ROSA classic cluster)
      3. Go to Machine pool tab  , click "Edit Cluster autoscaling settings" button.
      4. In the newly opened dialog or model, Input some invalid values in the field (for example, keep 
        the max-node-provision-time value to 15 or -15m)
      5. Try to click "Revert all to defaults" to revert all the field values to default or valid ones.
      6. See the behavior of "Revert all to defaults" button

      Actual results:

      At step 6, "Revert all to defaults" button is disabled for the user and couldn't able to revert the values to default including the fields throws validation error. This is not correct behavior.

      Expected results:

      At step 6, "Revert all to defaults" button should be enabled for the user and user should be able to revert the field values to default values.

              rh-ee-daznauro David Aznaurov
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: