Bug 1336263 - Image built out from nodejs-010-rhel7 cannot startup
Summary: Image built out from nodejs-010-rhel7 cannot startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Troy Dawson
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks: 1339174
TreeView+ depends on / blocked
 
Reported: 2016-05-16 02:21 UTC by Wang Haoran
Modified: 2016-06-27 04:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1339174 (view as bug list)
Environment:
Last Closed: 2016-06-01 09:11:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1189 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise Node.js image bug fix update 2016-06-01 13:09:39 UTC

Description Wang Haoran 2016-05-16 02:21:51 UTC
Description of problem:
After using the nodejs-010-rhel7 builder image build runtime image, pod cannot startup  due to /opt/app-root/etc/generate_container_user script exit with permission denied

Version-Release number of selected component (if applicable):
openshift3/nodejs-010-rhel7      latest              e0f62ad5808a

How reproducible:
always

Steps to Reproduce:
1.Create project
2. Create app
  $oc new-app openshift/nodejs~https://github.com/openshift/nodejs-ex
3.after build complete , check the runtime pod status
  $ oc get pod
4. check the pod log:
  $oc logs <pod>
   
Actual results:
pod keeps restart , cannot startup
NAME                READY     STATUS             RESTARTS   AGE
nodejs-ex-1-k6wcf   0/1       CrashLoopBackOff   2          32s
oc logs nodejs-ex-1-k6wcf -n haowang
/opt/app-root/etc/generate_container_user: line 10: /opt/app-root/etc/passwd: Permission denied
Expected results:
pod should startup successfully

Additional info:

Comment 1 Ben Parees 2016-05-16 02:44:37 UTC
Troy i'll look into this tomorrow but i guess we'll need a respin of the rhel image.

Comment 2 Ben Parees 2016-05-16 15:59:10 UTC
what registry is that image from? i can't locate it.

Comment 3 Ben Parees 2016-05-16 16:53:13 UTC
and do you have the same issue with the centos image?

Comment 5 Ben Parees 2016-05-17 02:48:41 UTC
fix (I think, i'm not able to reproduce this issue building the image myself which makes me think it has something to do with the base rhel image that OSBS uses): https://github.com/openshift/s2i-nodejs/pull/100

over to Troy to move to ON_QA once the image gets rebuilt.

Comment 6 Troy Dawson 2016-05-18 13:12:01 UTC
Updated image is built.  It is

openshift3/nodejs-010-rhel7:0.10-36

Comment 7 Wang Haoran 2016-05-19 02:33:51 UTC
verified with:
openshift3/nodejs-010-rhel7     latest              ce2a4369aff3

Comment 9 errata-xmlrpc 2016-06-01 09:11:29 UTC
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-2016:1189

Comment 10 Clayton Coleman 2016-06-26 20:35:37 UTC
I see this happening on OpenShift Online Preview, have we rev'd the images?

Comment 11 Steve Speicher 2016-06-27 04:39:39 UTC
I used to see this occasionally in the past but haven't seen it recently.


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