Description of problem: Failed to start Kibana pod # oc get po NAME READY STATUS RESTARTS AGE logging-curator-1-9c8fh 1/1 Running 0 10h logging-es-data-master-j5cf6q7g-1-pq9wk 1/1 Running 0 10h logging-fluentd-08xjz 1/1 Running 0 10h logging-fluentd-8dvzx 1/1 Running 0 10h logging-kibana-1-0mh0z 1/2 CrashLoopBackOff 70 10h # oc logs logging-kibana-1-0mh0z -c kibana container_linux.go:247: starting container process caused "exec: \"./run.sh\": permission denied" Version-Release number of selected component (if applicable): # openshift version openshift v3.6.169 kubernetes v1.6.1+5115d708d7 etcd 3.2.1 Images from brew registry logging-kibana v3.6.170-1 15078dfaeef7 2 hours ago 342.4 MB How reproducible: Always Steps to Reproduce: 1. Deploy logging 3.6.0 2. 3. Actual results: Failed to start Kibana pod Expected results: All pods should be healthy Additional info:
Cases related to kibana are blocked
A 3.6 merge origin with downstream causes run.sh to have file permissions as 0644 (without executable bit) [1] First parent of mentioned merge has ./run.sh permissions set to 0644 and entrypoint is CMD ["sh", "/run.sh"] [2] while second parent to 0755 and entrypoint is CMD ["./run.sh"] [3]. Merge became an unfortunate combination of these two approaches, the only non-runnable. Someone with a write access to downstream repos could fix by simply 'chmod +x run.sh' and commit. [1] http://pkgs.devel.redhat.com/cgit/rpms/logging-kibana-docker/commit/?h=rhaos-3.6-rhel-7&id=c2eeba2f087fdf280f9c4f0b17c14680fbb44aba [2] http://pkgs.devel.redhat.com/cgit/rpms/logging-kibana-docker/tree/?h=rhaos-3.6-rhel-7&id=ce5c66327427d0e6af17fb76f4ad0a115f5a61af [3] http://pkgs.devel.redhat.com/cgit/rpms/logging-kibana-docker/tree/?h=rhaos-3.6-rhel-7&id=5b709bf2f8b5a0319d63a52f303c30f831f47175
Jan - you should have permission to do this. Have you used the rhpkg command line tool? If not, https://mojo.redhat.com/docs/DOC-140221 Once you have that installed, I can show you how to do this.
It's fixed, verified with this latest image: logging-kibana v3.6 429262be200e 6 hours ago logging UI is back with log entries inside. Set to verified. Test env: # openshift version openshift v3.6.171 kubernetes v1.6.1+5115d708d7 etcd 3.2.1
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-2017:3188