Bug 1473330 - openshift-auth-proxy segmentation fault
Summary: openshift-auth-proxy segmentation fault
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-nodejs4-container
Version: rh-nodejs4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Zuzana Svetlikova
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-20 13:51 UTC by Jan Wozniak
Modified: 2018-03-05 12:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-05 12:11:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (3.17 KB, application/zip)
2017-07-20 13:51 UTC, Jan Wozniak
no flags Details

Description Jan Wozniak 2017-07-20 13:51:49 UTC
Created attachment 1301746 [details]
logs

Description of problem:
Trying to use the nodejs image as a base image for openshift-auth-proxy ends in segmentation fault within 10 seconds of running the container inside OpenShift.


Version-Release number of selected component (if applicable):
- base image: nodejs-{4,6}-{centos7,rhel7}
- OpenShift Origin v1.5.0
- openshift-ansible - current master [1]


How reproducible:
Always, as a docker image


Steps to Reproduce:
1. Deploy OpenShift logging using openshift-ansible
2. Apply a PR to change the base image for openshift-auth-proxy [2]
3. Build the image and deploy to own registry
4. In OpenShift logging project, point openshift/logging-auth-proxy image to the own registry
5. oc rollout latest logging-kibana


Actual results:
Starting up the proxy with auth mode "oauth2" and proxy transform "user_header,token_header".
/var/tmp/scl63Ncam: line 8:   395 Segmentation fault      (core dumped) node openshift-auth-proxy.js


Expected results:
No segmentation fault and running openshift-auth-proxy


Additional info:
Entering the container and installing nodejs from upstream [3] results in a successfully running proxy in the same image. I tried to verify in a standalone virtual machine using CentOS7 and KVM/QEMU but I was unable to reproduce the entire environment necessary for openshift-auth-image.



[1] https://github.com/openshift/openshift-ansible/tree/e29eab4e9813c46f4738a81e8698b001bd5981b9
[2] https://github.com/wozniakjan/openshift-auth-proxy/pull/1/files
[3] https://nodejs.org/en/download/package-manager/#enterprise-linux-and-fedora

Comment 3 Zuzana Svetlikova 2018-02-21 12:22:02 UTC
Is this bug still present?

Comment 4 Joe Orton 2018-02-21 16:08:19 UTC
Red Hat does not currently plan to provide any further changes to this collection in a Red Hat Software Collections update release.

This software collection is nearing the retirement date (April 2018) after which customers are encouraged to upgrade to a later release.

Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/

Comment 5 Jan Wozniak 2018-03-05 12:11:51 UTC
we no longer plan to use this, using the upstream images has been working for us better than using scl images.


Note You need to log in before you can comment on or make changes to this bug.