Back to bug 1842741

Who When What Removed Added
OpenShift BugZilla Robot 2020-06-02 02:41:03 UTC Status ASSIGNED POST
OpenShift BugZilla Robot 2020-06-02 02:41:04 UTC Link ID Github openshift/cluster-dns-operator/pull/174
Miciah Dashiel Butler Masters 2020-06-18 19:20:55 UTC Keywords UpcomingSprint
Miciah Dashiel Butler Masters 2020-06-21 05:43:38 UTC Doc Text Cause: When the DNS operator reconciles a DNS or Service object, the operator determines whether it needs to update the object by constructing an expected object in memory, getting the actual object from the API, and comparing the two. The operator leaves some values unspecified in its expected DNS and Service objects. When the API set default values for these unspecified values, the comparison would return a false positive.

Consequence: The operator was repeatedly trying to update DNS and Service objects in response to the API's setting default values.

Fix: The operator now considers unspecified values and default values to be equal when comparing DNS and Service objects.

Result: The operator should no longer update a DNS or Service object in response to API defaulting.
Doc Type If docs needed, set a value Bug Fix
Eric Paris 2020-06-22 13:30:29 UTC Keywords UpcomingSprint
OpenShift BugZilla Robot 2020-07-08 23:09:54 UTC Status POST MODIFIED
Andrew McDermott 2020-07-09 12:03:36 UTC Keywords UpcomingSprint
CC amcdermo
errata-xmlrpc 2020-07-10 09:33:14 UTC Status MODIFIED ON_QA
Eric Paris 2020-07-13 13:34:54 UTC Keywords UpcomingSprint
Hongan Li 2020-07-16 06:45:09 UTC Status ON_QA VERIFIED
errata-xmlrpc 2020-10-26 00:09:53 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2020-10-27 16:03:33 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2020-10-27 16:03:33 UTC
errata-xmlrpc 2020-10-27 16:03:36 UTC Link ID Red Hat Product Errata RHBA-2020:4196
Miciah Dashiel Butler Masters 2022-08-04 22:39:38 UTC Sub Component DNS
Component DNS Networking

Back to bug 1842741