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):
Steps to Reproduce:
Cluster stuck in uninstallation
Clusters not stuck in uninstallation, AWS customer resources being skipped for removal
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.