Bug 1850725 - fluentd crash looping on latest 4.5 downstream images. ruby not found
Summary: fluentd crash looping on latest 4.5 downstream images. ruby not found
Keywords:
Status: CLOSED DUPLICATE of bug 1843271
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-24 19:52 UTC by Mike Fiedler
Modified: 2020-06-25 20:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-25 11:15:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike Fiedler 2020-06-24 19:52:02 UTC 
Description of problem:

Fluentd is crash looping installing the latest downstream, ART-provided operators and images:

2020-06-24T19:36:44.103835267+00:00 stderr F ./wait_for_es_version.sh: line 3: ruby: command not found



Version-Release number of selected component (if applicable):

NAME                                           DISPLAY                  VERSION                 REPLACES   PHASE
clusterlogging.4.5.0-202006231303.p0           Cluster Logging          4.5.0-202006231303.p0              Succeeded
elasticsearch-operator.4.5.0-202006231303.p0   Elasticsearch Operator   4.5.0-202006231303.p0              Succeeded

ose-logging-fluentd@sha256:afe6ccfcd7348e6118c4e81d80a201844a862edfd800fd004bcf2a9249d28ba7


How reproducible: Always


Steps to Reproduce:
1.  Installed CLO and EO from latest ART builds
2.  Create clusterlogging


Actual results:

fluentd is stuck crash looping with a container log message that ruby cannot be found.
Comment 1 Sergey Yedrikov 2020-06-25 04:08:16 UTC 
Reported in https://bugzilla.redhat.com/show_bug.cgi?id=1843271#c10
Comment 2 Jeff Cantrill 2020-06-25 11:15:23 UTC 

*** This bug has been marked as a duplicate of bug 1843271 ***
Note You need to log in before you can comment on or make changes to this bug.