Bug 1553707

Summary: run.sh is missing in curator image
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7.1CC: aos-bugs, dyocum, mbarnes, rmeggins
Target Milestone: ---Keywords: OpsBlocker, Regression
Target Release: 3.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-29 14:36:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
curator dc info none

Description Junqi Zhao 2018-03-09 11:40:35 UTC 
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:
Comment 1 Junqi Zhao 2018-03-09 12:12:45 UTC 
Created attachment 1406251 [details]
curator dc info
Comment 3 Jeff Cantrill 2018-03-09 18:26:53 UTC 
*** Bug 1553858 has been marked as a duplicate of this bug. ***
Comment 4 Dan Yocum 2018-03-09 18:50:51 UTC 
*** Bug 1553858 has been marked as a duplicate of this bug. ***
Comment 6 Junqi Zhao 2018-04-17 01:12:35 UTC 
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
Comment 11 errata-xmlrpc 2018-04-29 14:36:36 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/RHSA-2018:1231