Description of problem: duplicated tolerations in the DNS operator deployment Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-06-19-210910 How reproducible: 100% Steps to Reproduce: 1. fresh install a cluster 2. oc get deployment/dns-operator -o yaml -n openshift-dns-operator 3. Actual results: <---snip---> - effect: NoSchedule key: node.kubernetes.io/not-ready operator: Exists - effect: NoSchedule key: node.kubernetes.io/not-ready operator: Exists <---snip---> Expected results: https://github.com/openshift/cluster-dns-operator/blob/master/manifests/0000_70_dns-operator_02-deployment.yaml#L48-L53 Additional info: seems it didn't cause any functional issue so far.
verified with 4.2.0-0.nightly-2019-08-08-002434 and issue has been fixed. <---snip---> tolerations: - effect: NoSchedule key: node-role.kubernetes.io/master operator: Exists - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 120 - effect: NoExecute key: node.kubernetes.io/not-ready operator: Exists tolerationSeconds: 120
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-2019:2922