Bug 1843271
| Summary: | The fluentd couldn't be started when using init-container | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Logging | Assignee: | ewolinet |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.5 | CC: | aos-bugs, bparees, jcantril, mifiedle, scuppett |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:42:56 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: | 1840274 | ||
| Bug Blocks: | |||
|
Comment 1
Jeff Cantrill
2020-06-03 15:36:49 UTC
raising to high since this bug has loss of data associated with it. The CSV bundles are not ready. oc logs fluentd-k6t8c -c fluentd-init ./wait_for_es_version.sh: line 3: ruby: command not found wait_for_es_version.sh should be executed when deploying fluentd only too. should be executed ---> shouldn't be executed @Anping, https://bugzilla.redhat.com/show_bug.cgi?id=1843271#c11 seems to be covered by https://bugzilla.redhat.com/show_bug.cgi?id=1850076 https://bugzilla.redhat.com/show_bug.cgi?id=1843271#c10 seems to be an issue with sourcing ruby for our downstream image, i'll investigate. The fix has been verified on 4.6. Waiting for the PR merge. *** Bug 1850725 has been marked as a duplicate of this bug. *** Verified on elasticsearch-operator.4.5.0-202006241631.p0 clusterlogging.4.5.0-202006241631.p0 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:2409 |