Description of problem: Deploy logging 3.10, kibana-proxy container failed to start up, error in logs error while loading shared libraries: libuv.so.0.10 find libuv.so.0.10 path is "/opt/rh/nodejs010/root/usr/lib64/libuv.so.0.10", which should be "/usr/lib64/libuv.so.0.10" This blocks the usage of kibana UI logging-kibana-5-bkgq6 1/2 CrashLoopBackOff 7 11m ******************************************************************************** # oc logs -c kibana-proxy logging-kibana-5-bkgq6 + BYTES_PER_MEG=1048576 + BYTES_PER_GIG=1073741824 + DEFAULT_MIN=67108864 + echo 268435456 + grep -qE '^([[:digit:]]+)([GgMm])?i?$' ++ echo 268435456 ++ grep -oE '^[[:digit:]]+' + num=268435456 ++ echo 268435456 ++ grep -oE '[GgMm]' ++ echo '' Using NODE_OPTIONS: '--max_old_space_size=256' Memory setting is in MB + unit= + '[' '' = G ']' + '[' '' = g ']' + '[' '' = M ']' + '[' '' = m ']' + '[' 268435456 -lt 67108864 ']' + export NODE_OPTIONS=--max_old_space_size=256 + NODE_OPTIONS=--max_old_space_size=256 + cd /usr/lib/node_modules/openshift-auth-proxy + echo 'Using NODE_OPTIONS: '\''--max_old_space_size=256'\'' Memory setting is in MB' ++ pwd Running from directory: '/usr/lib/node_modules/openshift-auth-proxy' + echo 'Running from directory: '\''/usr/lib/node_modules/openshift-auth-proxy'\''' + exec node --max_old_space_size=256 openshift-auth-proxy.js node: error while loading shared libraries: libuv.so.0.10: cannot open shared object file: No such file or directory ******************************************************************************** create debug pod to debug, and find libuv.so.0.10 path is "/opt/rh/nodejs010/root/usr/lib64/libuv.so.0.10", which should be "/usr/lib64/libuv.so.0.10" # oc rsh logging-kibana-5-bkgq6-debug sh-4.2$ find / -name libuv.so.0.10 find: '/proc/tty/driver': Permission denied find: '/run/secrets/rhsm': Permission denied find: '/var/lib/yum/history/2018-08-01/1': Permission denied find: '/var/lib/yum/history/2018-08-01/2': Permission denied find: '/var/lib/yum/history/2018-08-01/3': Permission denied find: '/var/lib/machines': Permission denied find: '/var/cache/ldconfig': Permission denied /opt/rh/nodejs010/root/usr/lib64/libuv.so.0.10 Version-Release number of selected component (if applicable): logging-auth-proxy-container-v3.10.14-12 logging-curator-container-v3.10.14-10 logging-elasticsearch-container-v3.10.14-12 logging-fluentd-container-v3.10.14-8 logging-kibana-container-v3.10.14-13 How reproducible: Always Steps to Reproduce: 1. Deploy logging 3.10 2. 3. Actual results: kibana-proxy container failed to start up Expected results: kibana-proxy container should be able to start up Additional info:
I see when looking through our image build info that logging auth proxy is the only one using this suspiciously relevant looking content source > $ grep -r rhel-server-ose-OLD_NODE_JS-rpms groups/*/images/* > groups/openshift-3.10/images/logging-auth-proxy.yml:- rhel-server-ose-OLD_NODE_JS-rpms > groups/openshift-3.11/images/logging-auth-proxy.yml:- rhel-server-ose-OLD_NODE_JS-rpms > ... Which is mapped as such: > rhel-server-ose-OLD_NODE_JS-rpms: > conf: > baseurl: http://download.lab.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift-signed/3.2/building/RH7-RHAOS-3.2/x86_64/os/ > content_set: > default: rhel-7-server-ose-3.2-rpms Pinging my team to see if they have any more insight.
Not a TestBlocker for logging-auth-proxy:v3.10.34
No such issue in logging:v3.10.44
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:2660