Description of problem: Deploy logging 3.7, curator pod failed to start up, it seems run.sh is missing in curator image # oc get po NAME READY STATUS RESTARTS AGE logging-curator-1-zvjgz 0/1 CrashLoopBackOff 7 14m logging-es-data-master-ghxfljba-1-zmd5h 2/2 Running 0 13m logging-fluentd-gr5p8 1/1 Running 0 14m logging-fluentd-v48q8 1/1 Running 0 14m logging-fluentd-vpf55 1/1 Running 0 14m logging-kibana-1-95h8l 2/2 Running 0 14m # oc logs logging-curator-1-zvjgz sh: run.sh: No such file or directory Version-Release number of selected component (if applicable): logging-kibana/images/v3.7.37-1 logging-auth-proxy/images/v3.7.37-1 logging-curator/images/v3.7.37-1 logging-fluentd/images/v3.7.37-1 logging-elasticsearch/images/v3.7.37-1 How reproducible: Always Steps to Reproduce: 1. Deploy logging 3.7 2. 3. Actual results: curator pod failed to start up Expected results: Additional info:
Created attachment 1406251 [details] curator dc info
*** Bug 1553858 has been marked as a duplicate of this bug. ***
run.sh is in curator image now, and pod could be started up # oc get po | grep curator logging-curator-1-zklnd 1/1 Running 0 6m # openshift version openshift v3.7.44 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8 logging-curator/images/v3.7.42-3 logging-kibana/images/v3.7.42-3 logging-elasticsearch/images/v3.7.42-4 logging-auth-proxy/images/v3.7.42-3 logging-fluentd/images/v3.7.42-3
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/RHSA-2018:1231