-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13.z, 4.12.z, 4.14.z
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-14859. The following is the description of the original issue:
—
Description of problem:
When the OIDC provider is deleted on the customer side, AWS resource deletion is not skipped in cases that the ValidAWSIdentityProvider state is on 'Unknown'. This results in clusters being stuck during deletion.
Version-Release number of selected component (if applicable):
4.12.z, 4.13.z, 4.14.z
How reproducible:
Irregular
Steps to Reproduce:
1. 2. 3.
Actual results:
Cluster stuck in uninstallation
Expected results:
Clusters not stuck in uninstallation, AWS customer resources being skipped for removal
Additional info:
Added MG for all hypershift related NS Bug seems to be at https://github.com/openshift/hypershift/pull/2281/files#diff-f90ab1b32c9e1b349f04c32121d59f5e9081ccaf2be490f6782165d2960bc6c7R295 : 'Unknown' needs to be added to the check if OIDC is valid or not.
- clones
-
OCPBUGS-14859 CPO doesn't skip AWS resource deletion for 'Unknown' OIDC state
- Closed
- is blocked by
-
OCPBUGS-14859 CPO doesn't skip AWS resource deletion for 'Unknown' OIDC state
- Closed
- links to