Bug 1723936
| Summary: | [4.1] no termination message provided by failing dns-operator pods | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Paris <eparis> |
| Component: | Networking | Assignee: | Dan Mace <dmace> |
| Networking sub component: | DNS | QA Contact: | Hongan Li <hongli> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aos-bugs, bbennett, dmace, hongli, mmasters, sanchezl, weliang, xtian |
| Version: | 4.1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.1.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | 4.1.4 | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1707062 | Environment: | |
| Last Closed: | 2019-07-04 09:01:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1707062 | ||
| Bug Blocks: | |||
|
Comment 2
Weibin Liang
2019-06-27 13:35:15 UTC
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 |