Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-3507

[Hypershift ROSA] Edit node count action set wrong node count when a machine pool with autoscaling enabled has updated without autoscaling option.

XMLWordPrintable

    • 1
    • False
    • False
    • None

      Description

      In a Hypershift ROSA cluster, a machine pool with autoscaling enabled (for ex, minimum, maximum node count is 1). Once the user edit the machine pool i.e. disabled auto scaling ,node count is 2 and saved the changes. The node count wrongly set to 1 instead of 2.

       

      Steps to reproduce:

      1. Install Hypershift ROSA cluster.( use CLI)
      2. Wait for installation is successful. (note: there will be machine pool with node count > 2 already)
      3. Create a machine pool via CLI ($ $ rosa create machinepools --enable-autoscaling --min-replicas=1 --max-replicas=1 --name q1 -c jayam15hypr )
      4. Launch OCM.
      5. Locate Hypershift ROSA cluster > Navigate to "Machine pool" tab.
      6. Click on scale option for the machine pool added in step 3.
      7. On "Edit node count" dialog ,
      8. Disable auto-scaling , keep the node count as 2 and click on save.
      9. View the node count of machine pool after save operation.

      Actual results:
      After step 8, The node count is set wrongly as 1. It looks like default node count value is not considered while saving the new definitions.

      Expected results:
      After step 8, The node count should set to 2 .

      See the screen capture NodeCountIssue.mp4

        1. NodeCountIssue.mp4
          1.46 MB
          Jayakrishnan Mekkattillam

            zherman Zac Herman
            jmekkatt@redhat.com Jayakrishnan Mekkattillam
            Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: