Description of problem: free-int cluster, logging-curator pod is in CrashLoopBackOff status, same error with Bug 1589635 # oc get pod -n logging NAME READY STATUS RESTARTS AGE logging-curator-6-kgpqt 0/1 CrashLoopBackOff 5111 18d logging-es-data-master-f26an8nv-5-5rct4 2/2 Running 0 18d # oc logs logging-curator-6-kgpqt -n logging Enter passphrase for key '/home/fedora/online/id_rsa': Traceback (most recent call last): File "run_cron.py", line 112, in <module> ccj.run() File "run_cron.py", line 39, in run if self.server_ready(): File "run_cron.py", line 72, in server_ready if es.ping(): AttributeError: 'bool' object has no attribute 'ping' Version-Release number of selected component (if applicable): logging-curator:v3.10.0-0.66.0 How reproducible: Always Steps to Reproduce: 1. Check logging pods status 2. 3. Actual results: logging-curator pod is in CrashLoopBackOff status Expected results: Additional info:
OCP version: OpenShift Master:v3.10.0-0.66.0 Kubernetes Master:v1.10.0+b81c8f8 OpenShift Web Console:v3.10.0-0.66.0
Bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1589635 which requires v3.10.0-0.67.0.0 or better
@jupierce See Comment 2, please update logging image versions
*** This bug has been marked as a duplicate of bug 1589635 ***