Bug 1018134

Summary:	Can not restart after force-stop the app for nodejs-0.6 and nodejs-0.10 after migration in STG
Product:	OpenShift Online	Reporter:	Yan Du <yadu>
Component:	Containers	Assignee:	Paul Morie <pmorie>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	xtian
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:	2013-10-17 13:35:14 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 Yan Du 2013-10-11 10:14:32 UTC

Description of problem:
Can not restart after force-stop the app for nodejs-0.6 and nodejs-0.10 after migration


Version-Release number of selected component (if applicable):
STG(devenv-stage_493)


How reproducible:
Always


Steps to Reproduce:

1. Create a nodejs app (nodejs-0.6 or nodje-0.10)
#rhc app create n6 nodejs-0.6
2. do migration
3. rhc app-force-stop n6
4. rhc app restart n6


Actual results:

[root@Daphne test]# arestart n6 -d
Unable to complete the requested operation due to: Failed to correctly execute all parallel
operations.


Expected results:
should restart app normally after force-stop


Additional info:

rhc ssh the app to check the control script, found the code in https://github.com/openshift/origin-server/commit/fe4b4d708bf48abc6d2961502fee16da5a66d779  didn't update to old nodejs app.

Comment 1 Xiaoli Tian 2013-10-11 10:34:53 UTC

I guess we have not bumped up cartridge versions for all  cartridges having changes for sprint 34 yet, that will cause most changes for cartridges can not be upgraded successfully in STG since STG is running oo-admin-upgrade without --ignore-cartridge-version option

Comment 2 Yan Du 2013-10-12 02:58:46 UTC

Test on STG(devenv-stage_496), the issue can't be reproduced. nodejs app can be controlled normally.

Comment 3 Yan Du 2013-10-16 08:14:37 UTC

Move bug to verified according to #Comment 2