Bug 1878148

Summary: Ingress Operator Fails to Delete DNSRecord
Product: OpenShift Container Platform Reporter: Stephen Greene <sgreene>
Component: NetworkingAssignee: Stephen Greene <sgreene>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: aos-bugs, dhansen, hongli, jeder, mmasters, nmalik, wking
Version: 4.5Keywords: ServiceDeliveryBlocker, UpcomingSprint
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1850813 Environment:
Last Closed: 2020-09-21 17:42:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1850813    
Bug Blocks: 1877928    

Comment 2 Hongan Li 2020-09-14 06:51:19 UTC
verified with 4.5.0-0.nightly-2020-09-12-040057 and issue has been fixed.

the default ingresscontroller can be deleted and no error "failed to delete dnsrecord" in the logs

Comment 4 Stephen Greene 2020-09-14 18:20:53 UTC
*** Bug 1876919 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2020-09-21 17:42:07 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 (OpenShift Container Platform 4.5.11 bug fix 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.

https://access.redhat.com/errata/RHBA-2020:3719