Bug 1838266 - DNS Operator Reports Confusing Status Conditions
Summary: DNS Operator Reports Confusing Status Conditions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Daneyon Hansen
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-20 19:06 UTC by Daneyon Hansen
Modified: 2022-08-04 22:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:40:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-dns-operator pull 173 0 None closed Bug 1838266: Updates Progressing status condition message 2021-02-16 07:31:00 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:40:43 UTC

Description Daneyon Hansen 2020-05-20 19:06:42 UTC
Description of problem:
From [1], dns operator may report confusing status conditions:

config/clusteroperator/dns
    operator 4.3.18
    coredns quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:50ef63040a0e46976a6e92401cccba84df77c4886d0ee7cdfa1a88270d767303
    openshift-cli quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0a70026a8b193e61356054ab92ec825aac23c52ac5410c5e49c2412f92fe195b
  2020-05-19T06:59:27Z Degraded=False AsExpected: All desired DNS DaemonSets available and operand Namespace exists
  2020-05-19T07:04:04Z Progressing=True Reconciling: Not all DNS DaemonSets available.
  2019-12-05T18:24:26Z Available=True AsExpected: At least 1 DNS DaemonSet available

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

How reproducible:
Always

Steps to Reproduce:
1. N/A

Actual results:
Conditions referenced above.

Expected results:
A Progressing condition that states at least 1 dns daemonset is still progressing.

Additional info:
[1] https://coreos.slack.com/archives/CDCP2LA9L/p1589953544126800

Comment 4 Hongan Li 2020-05-27 09:08:53 UTC
verified with 4.5.0-0.nightly-2020-05-27-010813 and issue has been fixed.

$ oc get co/dns -o yaml
<---snip--->
status:
  conditions:
  - lastTransitionTime: "2020-05-27T04:06:44Z"
    message: All desired DNS DaemonSets available and operand Namespace exists
    reason: AsExpected
    status: "False"
    type: Degraded
  - lastTransitionTime: "2020-05-27T09:01:20Z"
    message: At least 1 DNS DaemonSet is progressing.
    reason: Reconciling
    status: "True"
    type: Progressing
  - lastTransitionTime: "2020-05-27T03:55:44Z"
    message: At least 1 DNS DaemonSet available
    reason: AsExpected
    status: "True"
    type: Available

Comment 5 errata-xmlrpc 2020-07-13 17:40:29 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.

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


Note You need to log in before you can comment on or make changes to this bug.