Description of problem: Checked the ingress operator's log and it keep printing the logs: 2020-05-19T09:22:44.324Z INFO operator.dns azure/dns.go:89 upserted DNS record {"record": {"metadata":{"name":"default-wildcard","namespace":"openshift-ingress-operator","selfLink":"/apis/ingress.operator.openshift.io/v1/namespaces/openshift-ingress-operator/dnsrecords/default-wildcard","uid":"0dae357b-f565-48ff-86d7-80149fcf7d9d","resourceVersion":"188426","generation":1,"creationTimestamp":"2020-05-19T02:09:28Z","labels":{"ingresscontroller.operator.openshift.io/owning-ingresscontroller":"default"},"ownerReferences":[{"apiVersion":"operator.openshift.io/v1","kind":"IngressController","name":"default","uid":"45621f7d-4d7c-4e16-bb51-370da3d550fe","controller":true,"blockOwnerDeletion":true}],"finalizers":["operator.openshift.io/ingress-dns"],"managedFields":[{"manager":"ingress-operator","operation":"Update","apiVersion":"ingress.operator.openshift.io/v1","time":"2020-05-19T09:22:42Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:finalizers":{".":{},"v:\"operator.openshift.io/ingress-dns\"":{}},"f:labels":{".":{},"f:ingresscontroller.operator.openshift.io/owning-ingresscontroller":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"45621f7d-4d7c-4e16-bb51-370da3d550fe\"}":{".":{},"f:apiVersion":{},"f:blockOwnerDeletion":{},"f:controller":{},"f:kind":{},"f:name":{},"f:uid":{}}}},"f:spec":{".":{},"f:dnsName":{},"f:recordTTL":{},"f:recordType":{},"f:targets":{}},"f:status":{".":{},"f:zones":{}}}}]},"spec":{"dnsName":"*.apps.hongli-pl907.qe.azure.devcluster.openshift.com.","targets":["40.65.51.200"],"recordType":"A","recordTTL":30},"status":{"zones":[{"dnsZone":{"id":"/subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/hongli-pl907-26gjt-rg/providers/Microsoft.Network/privateDnsZones/hongli-pl907.qe.azure.devcluster.openshift.com"},"conditions":[{"type":"Failed","status":"False","lastTransitionTime":"2020-05-19T09:22:42Z","reason":"ProviderSuccess","message":"The DNS provider succeeded in ensuring the record"}]},{"dnsZone":{"id":"/subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/os4-common/providers/Microsoft.Network/dnszones/qe.azure.devcluster.openshift.com"},"conditions":[{"type":"Failed","status":"False","lastTransitionTime":"2020-05-19T09:22:43Z","reason":"ProviderSuccess","message":"The DNS provider succeeded in ensuring the record"}]}]}}} Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-18-225907 How reproducible: 100% Steps to Reproduce: 1. Launch a new cluster in Azure 2. Check the ingress operator's log $ oc -n openshift-ingress-operator logs deploy/ingress-operator -c ingress-operator | grep "upserted DNS record" | wc -l 1702 $ oc -n openshift-ingress-operator logs deploy/ingress-operator -c ingress-operator | grep "upserted DNS record" | wc -l 1740 Actual results: The ingress operator's logs have "upserted DNS record" repeated. Expected results: should not upsert DNS record repeatedly. Additional info:
https://github.com/openshift/cluster-ingress-operator/pull/390 should fix this.
*** This bug has been marked as a duplicate of bug 1809354 ***