Bug 1033700

Summary:	Unable to stop nodejs app when not using supervisor
Product:	OpenShift Online	Reporter:	Paul Morie <pmorie>
Component:	Image	Assignee:	Paul Morie <pmorie>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	bmeng, yadu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-30 00:50:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.