Description of problem:
Deleting a custom ingress controller with a bad domain name hangs on DNS record deletion (at least on GCP, need to test other platforms).
Version-Release number of selected component (if applicable): 4.7 (and prior)
Steps to Reproduce:
Create a trivial ingress controller with spec.Domain set to an invalid domain (ie, use a mutated version of the default ingress controller's domain)
example on GCP via cluster-bot:
2. Observe the ingress operator fail to create the DNS record for the ingress controller.
3. Delete the ingress controller via oc.
The busted ingress controller cannot be deleted via `oc delete ingresscontroller ...`. The DNS record finalizer has to be removed by hand so the delete operation can be completed (this is safe to do since no DNS record was never created).
Deleting an ingress controller with a bad domain works without delays or user interventions.
Observed this bug when accidentally creating an ingress controller on GCP with the base domain of a prior cluster.
Verified with 4.7.0-0.nightly-2021-01-19-095812 and passed
can delete the ingress controller with a bad domain successfully (without removing finalizers by hand).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.