Bug 1669290

Summary: Wildcard DNS zones are not deleted along with a ClusterIngress
Product: OpenShift Container Platform Reporter: Dan Mace <dmace>
Component: NetworkingAssignee: Dan Mace <dmace>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs
Version: 4.1.0   
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:42:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan Mace 2019-01-24 21:05:49 UTC
Description of problem:

Deleting a ClusterIngress using the Cloud highAvailability type (e.g. the default router) orphans any corresponding wildcard DNS records in the cluster's public and private zones.

Version-Release number of selected component (if applicable):


How reproducible:

Create a new cluster and `oc delete -n openshift-ingress-operator clusteringresses/default`

Actual results:

Wildcard DNS records for the ingress domain still exist in the Route53 public and private zones for the cluster.

Expected results:

The wildcard DNS records should be deleted when the clusteringress is deleted.

Additional info:

Comment 2 Hongan Li 2019-02-21 03:26:16 UTC
verified with 4.0.0-0.nightly-2019-02-20-194410 and the issue has been fixed.

Comment 5 errata-xmlrpc 2019-06-04 10:42:15 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.