Uploaded image for project: 'Managed Service - API'
  1. Managed Service - API
  2. MGDAPI-5995

Investigate how to resolve CRO not being able to reach AWS.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • None
    • False
    • No

      WHY
      We had a recent customer issue, OHSS-24889 

      Summary of cluster issue: 

      • STS: true, PrivateLink: true, 
      • the RDS was gone from aws
      • VPCs were showing error setting connection rules
      • the postgres crd instance on the cluster was not removed and was blocking addon uninstallation
      • we had to manually remove the finalizer to unblock the uninstallation
      • we ask whether it is necessary to create RDS before vpc connection rules are set successfully

      WHAT
      Investigate how this scenario might occur and steps to resolve.

      We also need to understand how a clean uninstall can proceed. 

      One theory was the following:

      • The Postgres CR created but never reconciled as it could not reach AWS
      • On uninstall, it could not delete the Postgres CR as it could not reach AWS

      However, this does not explain how the VPC may have been created.

              Unassigned Unassigned
              bgallagh@redhat.com Brian Gallagher
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: