Bug 824356 - Nodejs not reachable or restartable
Summary: Nodejs not reachable or restartable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ram Ranganathan
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 10:30 UTC by Rob Millner
Modified: 2015-05-14 22:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-08 17:58:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rob Millner 2012-05-23 10:30:57 UTC
Description of problem:
The nodejs cartridge tests fail to reach nodejs and pushes hang.

Version-Release number of selected component (if applicable):
cartridge-nodejs-0.6-0.8.4

How reproducible:
Always

Steps to Reproduce:
1. cucumber li-test/tests/cartridge-lifecycle-nodejs.feature

  
Actual results:
Fails to become reachable.  And pushes timeout.


Expected results:
Tests run successfully.


Additional info:
npm appears to start and Apache gets a 503.  Git pushes get hung up on "npm install -d".

Comment 1 Ram Ranganathan 2012-05-23 20:03:02 UTC
Fixed with git commit 286291969d1003f49e79c5d68ae4a196e30f44f8 

selinux policies modifications removed the ability to use anonymous inodes. Added a policy back in.

Comment 2 Meng Bo 2012-05-28 09:55:48 UTC
verified on devenv_1806, issue fixed.

Comment 3 Meng Bo 2012-05-28 10:12:13 UTC
To verify this bug, because I cannot find the script, so I operated the following steps,
1, control the nodejs app with basic controls, like stop,start,restart,reload.
2, modify the deplist.txt in the repo and push it to server to trigger server side bundling, and npm install processing.

None of the operations cause the issue reproduced.
So mark this as verified.


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