Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-7442

Destroy clusters bulk modal shows warning for valid clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • MCE 2.4.0
    • MCE 2.4.0
    • HyperShift
    • False
    • None
    • False
    • Moderate
    • No

      Description of problem:

      When destroying valid clusters via the bulk actions menu, we see the warning:
      "You selected 0 clusters that cannot be destroyed
      They will not be destroyed when you perform this action."

      If there aren't any clusters that are non-destroyable, this warning should not show as both statements are not relevant and distracting.

       

      Contrast this to existing behaviour, such as trying to hibernate a cluster that does not support it:

      Version-Release number of selected component (if applicable):

      ACM 2.9.0-DOWNSTREAM-2023-09-08-21-11-02

      How reproducible:

      always

      Steps to Reproduce:

      1. in acm cluster list, select a cluster that can be destroyed
      2. select "actions" menu > destroy clusters
      3. observe warning appears, although we can destroy the cluster

      Actual results:

      Expected results:

      Additional info:

      this does not block destroy itself, so not as severe.

        1. image-2023-09-11-11-26-03-126.png
          211 kB
          David Huynh
        2. image-2023-09-11-11-28-17-624.png
          105 kB
          David Huynh
        3. image-2023-09-19-09-23-40-959.png
          50 kB
          David Huynh
        4. image-2023-09-19-09-24-02-390.png
          75 kB
          David Huynh

              magchen@redhat.com Maggie Chen
              rhn-support-dhuynh David Huynh
              David Huynh David Huynh
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: