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

[OSD Wizard] Empty fields are shown instead of default value i.e. zero on "Edit cluster autoscaling settings" dialog.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Core UI
    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      In OSD wizard flow, the empty fields are shown when the default value is zero for those fields from " Edit cluster autoscaling settings" dialog.

      Screenshot from staging as below

      Screenshot from production as below (works as expected)

      Steps to reproduce:

      1. Launch OCM Staging UI.
      2. Open OSD wizard.
      3. Select subscription as "Annual fixed capacity subscription" and Infrastructure type as "Red Hat account"
      4. Click "Next" and choose any of the cloud provider.
      5. Proceed to "Next" steps and reach to "Cluster Settings"> "Machine pool".
      6. Enable "Enable autoscaling" checkbox.
      7. Click on "Edit cluster autoscaling settings".
      8. See the fields having default value as zero.

      Actual results:

      The fields with default value as zero are shown empty from theĀ "Edit cluster autoscaling settings" dialog.

      User can't enter the value zero to those fields as well.

      Expected results:

      The fields with default value as zero shouldn't be empty and it should keep the value as zero from the "Edit cluster autoscaling settings" dialog.
      The user should allow to enter the value zero to those supported fields.

      This was happening across all the browsers and tested with chrome, edge and firefox.

              jschuler_kafka_devexp Joachim Schuler
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: