Bug 1575820

Summary:	logging-curator pods can not be started up
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.1	CC:	anli, aos-bugs, jkarasek, rmeggins, smunilla
Target Milestone:	---	Keywords:	Regression, TestBlocker
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-06-27 07:59:12 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:
Bug Depends On:
Bug Blocks:	1557483, 1559162

Description Junqi Zhao 2018-05-08 03:05:06 UTC

Description of problem:
logging-curator pods can not be started up.
# oc get po
NAME                                      READY     STATUS             RESTARTS   AGE
logging-curator-1-d9l5q                   0/1       CrashLoopBackOff   4          3m
logging-curator-1-deploy                  1/1       Running            0          3m
logging-es-data-master-6ybzgqk7-1-p4qh8   2/2       Running            0          2m
logging-fluentd-h4hgv                     1/1       Running            0          2m
logging-fluentd-svpwj                     1/1       Running            0          2m
logging-kibana-1-svqhk                    2/2       Running            0          3m

# oc logs logging-curator-1-d9l5q
sh: run.sh: No such file or directory

# docker run -it brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-curator:v3.7.46-1 /bin/bash
bash-4.2$ ls
__init__.py  curator_cmd.py  parser.py	run_cron.py  util.py


Version-Release number of selected component (if applicable):
logging-curator/images/v3.7.46-1

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
logging-curator pods can not be started up

Expected results:
logging-curator pods could be started up

Additional info:

Comment 2 Junqi Zhao 2018-05-09 05:40:58 UTC

Blocks curator functions

Comment 3 Anping Li 2018-05-10 09:57:46 UTC

@Samuel, Could you rebuild this curator image to include the fix of this bug. If this bug couldn't be fixed.  we must remove logging-curator image from v3.7 errata.

Comment 4 Anping Li 2018-05-22 07:59:23 UTC

works well with logging-curator:v3.7.48

Comment 6 errata-xmlrpc 2018-06-27 07:59:12 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-2018:2009