Bug 1843271 - The fluentd couldn't be started when using init-container
Summary: The fluentd couldn't be started when using init-container
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
: 1850725 (view as bug list)
Depends On: 1840274
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-02 23:18 UTC by OpenShift BugZilla Robot
Modified: 2020-07-13 17:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:42:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 567 0 None closed [release-4.5] Bug 1843271: creating init container to block waiting for es version 6+ 2020-11-10 16:02:57 UTC
Github openshift origin-aggregated-logging pull 1913 0 None closed [release-4.5] Bug 1843271: Add script to let fluentd check ES version 2020-11-10 16:02:56 UTC
Github openshift origin-aggregated-logging pull 1930 0 None closed [release-4.5] Bug 1843271: Enable ruby from scl if exists 2020-11-10 16:02:57 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:43:17 UTC

Comment 1 Jeff Cantrill 2020-06-03 15:36:49 UTC 
Upgrading severity since workaround can be annoying.  We should attempt to address in 4.5.0
Comment 2 Ben Parees 2020-06-11 13:41:45 UTC 
raising to high since this bug has loss of data associated with it.
Comment 7 Anping Li 2020-06-22 07:22:38 UTC 
The CSV bundles are not ready.
Comment 10 Anping Li 2020-06-23 02:52:41 UTC 
oc logs fluentd-k6t8c -c fluentd-init
./wait_for_es_version.sh: line 3: ruby: command not found
Comment 11 Anping Li 2020-06-23 03:39:13 UTC 
 wait_for_es_version.sh should be executed when deploying fluentd only too.
Comment 12 Anping Li 2020-06-23 03:46:43 UTC 
should be executed ---> shouldn't be executed
Comment 13 ewolinet 2020-06-23 16:51:38 UTC 
@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.
Comment 15 Anping Li 2020-06-24 02:32:06 UTC 
The fix has been verified on 4.6. Waiting for the PR merge.
Comment 17 Jeff Cantrill 2020-06-25 11:15:23 UTC 
*** Bug 1850725 has been marked as a duplicate of this bug. ***
Comment 18 Anping Li 2020-06-25 14:56:40 UTC 
Verified on elasticsearch-operator.4.5.0-202006241631.p0 clusterlogging.4.5.0-202006241631.p0
Comment 19 errata-xmlrpc 2020-07-13 17:42:56 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:2409
Note You need to log in before you can comment on or make changes to this bug.