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

Destroy modal for hosted cluster shows incorrect cluster name and inconsistent wording

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:

      1. When a hosted cluster is being provisioned (before import), and we select "Destroy cluster", the modal appears but it shows "The oidc-cred cluster can only be destroyed through the CLI."

      Should use the hosted cluster's name here.

      2. In step 1, we say

      Have the Amazon Web Services (AWS) credential you used to create the cluster. 

      Any AWS credential with access to the AWS resource should be sufficient, even if its not the same? Or is that overcomplicating it?

      3.  In the code snippet in step 3:

      export CLUSTER_NAME="example"
      SECRET_CREDS="example-aws-credential-secret"  # The credential name defined in step 1. 

      Here we are exporting the CLUSTER_NAME but not SECRET_CREDS. Should be the same.

      4. In the code snippet in step 3, still shows "hypershift" command, we should be using "hcp" now.

      5. Should we link to the documentation for extra arguments that they can see? or note that they can do hcp destroy cluster aws --help ?

      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. create hosted cluster
      2. go to acm ui, cluster list, open options for hosted cluster and select "destroy cluster"
      3. observe modal

      Actual results:

      Expected results:

      Additional info:

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

                Created:
                Updated:
                Resolved: