Verified with v4.1.3 and testing passed.
Verified in 4.1.0-0.nightly-2019-06-27-204847, not v4.1.3 [root@dhcp-41-193 FILE]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.1.0-0.nightly-2019-06-27-204847 True False 73m Cluster version is 4.1.0-0.nightly-2019-06-27-204847 [root@dhcp-41-193 FILE]# oc get deployment dns-operator -o yaml -n openshift-dns-operator <---snip---> terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError <---snip---> [root@dhcp-41-193 FILE]# oc get ds dns-default -o yaml -n openshift-dns <---snip---> terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError <---snip---> terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError <---snip--->
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:1635