Description of problem: Deploy logging 3.6.0 on OCP, after other components are all started up, the kibana container can't be started because readiness probe failed: # oc get event | grep kibana ... Readiness probe failed: rpc error: code = 13 desc = invalid header field value "oci runtime error: exec failed: container_linux.go:247: starting container process caused \"exec: \\\"/usr/share/kibana/probe/readiness.sh\\\": stat /usr/share/kibana/probe/readiness.sh: no such file or directory\"\n" # oc get po NAME READY STATUS RESTARTS AGE logging-curator-1-vs9sj 1/1 Running 0 6m logging-es-data-master-lfw1lt94-1-8k1vg 1/1 Running 0 6m logging-fluentd-lkv5r 1/1 Running 0 6m logging-fluentd-zkfxz 1/1 Running 0 6m logging-kibana-1-7bdgz 1/2 Running 0 6m logging-kibana-1-deploy 1/1 Running 0 6m Version-Release number of selected component (if applicable): openshift3/logging-kibana v3.6 b2ee235a5512 2 days ago 342.4 MB openshift-ansible-playbooks-3.6.94-1.git.0.fff177b.el7.noarch # openshift version openshift v3.6.85 kubernetes v1.6.1+5115d708d7 etcd 3.1.0 How reproducible: Always Steps to Reproduce: 1.Deploy logging 3.6.0 on OCP 2.After other components are all started up, check kibana pod status Actual results: 2.the kibana container can't be started because readiness probe failed Expected results: 2.kibana should be started up successfully Additional info:
This issue blocked logging UI tests.
Likely the same as https://bugzilla.redhat.com/show_bug.cgi?id=1452807
(In reply to Mike Fiedler from comment #2) > Likely the same as https://bugzilla.redhat.com/show_bug.cgi?id=1452807 Yes, I think so.
Marking this urgent since logging UI testing is still blocked for 3.6