Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1553858

Summary:	logging-curator enters CrashLoopBackOff
Product:	OpenShift Container Platform	Reporter:	Dan Yocum <dyocum>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.7.1	CC:	aos-bugs, rmeggins
Target Milestone:	---	Keywords:	OpsBlocker, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-09 18:50:51 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:

Description Dan Yocum 2018-03-09 17:35:02 UTC

Description of problem:

When deploying logging on 3.7.23, the curator fails to start.

logging-curator-4-wkp2n                   0/1       CrashLoopBackOff   1          25s

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

image: registry.reg-aws.openshift.com:443/openshift3/logging-curator:v3.7

# rpm -q atomic-openshift
atomic-openshift-3.7.23-1.git.0.8edc154.el7.x86_64


How reproducible:

Every

Steps to Reproduce:
1. Deploy logging using o-a playbooks.

Actual results:

Fails

Expected results:

Succeeds

Comment 1 Dan Yocum 2018-03-09 17:43:25 UTC

The oc logs logging-curator output is this:

sh: run.sh: No such file or directory

Comment 2 Jeff Cantrill 2018-03-09 18:26:53 UTC


*** This bug has been marked as a duplicate of bug 1553707 ***

Comment 4 Dan Yocum 2018-03-09 18:50:51 UTC


*** This bug has been marked as a duplicate of bug 1553707 ***