Bug 1851381
Summary: | logStore stanza is required to deploy fluentd standalone | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Periklis Tsirakidis <periklis> |
Component: | Logging | Assignee: | Periklis Tsirakidis <periklis> |
Status: | CLOSED ERRATA | QA Contact: | Giriyamma <gkarager> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | aos-bugs, oarribas, ocasalsa |
Target Milestone: | --- | ||
Target Release: | 4.4.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Missing reconciliation of a collector dead end condition when none of log store or logforwarding status is provided by the user in the ClusterLogging and/or LogFowarding custom resources.
Consequence:
Fluentd is crashlooping because no configuraiton is provided.
Fix:
Provide am empty configuration for fluentd to enable pods startup. In addition report DeadEnd condition in Logfowarding custom restource status to inform users of manual intervention demand.
Result:
Fluentd starts as expected given a ClusterLogging custom resource with only a collection stanza. In addition if a LogFowarding custom resource provided with zero valid outputs a condition named DeadEnd will be reported in the status field.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-14 01:43:54 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: | 1850076 | ||
Bug Blocks: |
Comment 4
Giriyamma
2020-07-06 13:22:37 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:2871 |