Bug 1033700 - Unable to stop nodejs app when not using supervisor
Summary: Unable to stop nodejs app when not using supervisor
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Paul Morie
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 16:28 UTC by Paul Morie
Modified: 2015-05-15 00:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-30 00:50:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Paul Morie 2013-11-22 16:28:26 UTC 
When the changes to use supervisor only when hot_deploy is enabled went in, it introduced a bug where the nodejs cartridge cannot be stopped if not using supervisor.  The expected behavior is to be able to stop the application.
Comment 1 openshift-github-bot 2013-11-22 21:01:11 UTC 
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/d446d0fd9fb1f721337df351a1bf5a27f77e4a3c
Fix bug 1033700
Comment 2 Yan Du 2013-11-25 05:48:39 UTC 
Test on devenv_4067, issue can't be reproduced.

Steps:
1. Create nodejs-0.6/0.10 app and check the process in app, no supervisor running, and app can be controlled(stop/start/restart/force-stop/reload).
2. Add hot_deploy marker, supervisor running in app.
3. Remove hot_deploy marker, nodejs running without supervisor, app can be controlled normally too.

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