Description of problem: When the dnses.operator.openshift.io/default object exists but its corresponding DaemonSet is not available, clusteroperators/dns reports the "Available" condition with status "False" (which is correct), reason "NoDNS" (which is wrong), and message "No DNS resource exists" (which is also wrong). Version-Release number of selected component (if applicable): The erroneous logic was added in OpenShift 4.2: https://github.com/openshift/cluster-dns-operator/pull/109/commits/540ab8bca50b50880a4eb44feaddee8352f565bf How reproducible: Readily. Steps to Reproduce: 1. Launch a cluster. 2. Delete the default DNS's DaemonSet: oc -n openshift-dns delete daemonsets/dns-default 3. Check the clusteroperator: oc get clusteroperators/dns -o yaml Actual results: The clusteroperator reports the following: "No DNS resource exists": - lastTransitionTime: "2020-05-14T11:52:05Z" message: No DNS resource exists reason: NoDNS status: "True" type: Degraded Expected results: The clusteroperator should report the following: "Not all desired DNS DaemonSets available". Additional info: Observed in CI: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_router/113/pull-ci-openshift-router-master-e2e-aws/373
verified with 4.5.0-0.nightly-2020-05-27-202943 and the issue has been fixed. status: conditions: - lastTransitionTime: "2020-05-28T08:26:34Z" message: Not all desired DNS DaemonSets available reason: NotAllDNSesAvailable status: "True" type: Degraded
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. https://access.redhat.com/errata/RHBA-2020:2409