Bug 1707062
Summary: | no termination message provided by failing dns-operator pods | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Luis Sanchez <sanchezl> | |
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, mmasters | |
Version: | 4.1.0 | |||
Target Milestone: | --- | |||
Target Release: | 4.2.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1723936 (view as bug list) | Environment: | ||
Last Closed: | 2019-10-16 06:28:30 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: | ||||
Bug Blocks: | 1723936 |
Description
Luis Sanchez
2019-05-06 17:39:24 UTC
Moving to 4.2 since this should not block the release. But if it lands soon, please change it back to 4.2. verified with 4.2.0-0.nightly-2019-06-25-003324 and issue has been fixed. $ oc get deployment dns-operator -o yaml -n openshift-dns-operator spec: template: spec: containers: - command: - dns-operator terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError $ oc get ds dns-default -o yaml -n openshift-dns spec: template: spec: containers: name: dns terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError <---snip---> name: dns-node-resolver terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError 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 |