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

[OCM UI] Suggestion under security group section is confusing when installer role associated to the cluster is missing.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • A-Team
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ACM Console Sprint 251

      Description of problem:

      A ready ROSA cluster was created last day. Some reason the installer role associated to the cluster was deleted/altered from the AWS side. While user tries to add a new machine pool via  "Add machine pool" option , under the security group section inline indication shown.

      The issue will never get solved even after refreshing the machine pool details and the message shown is irrelevant as the API calls to fetch security group fails as below.

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Open a Ready ROSA cluster  installed with custom VPC(VPC should have some Security groups associated).
      3. Make sure the installer roles used cluster creation were altered or deleted.
      4. Go to Machine pool tab.
      5. Click "Add machine pool"
      6. Go to  Security groups.
      7. See the behavior.

      Actual results:

      The security group section shown as VPC can't load and suggesting to refresh the machine pool details. The suggested action never solves the issue and leads to confusion to the user.

      Expected results:

      Show appropriate error message in security group section so that user know what was missing and what steps needs to be taken to solve this issue.

              jswanke@redhat.com John Swanke
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: