Bug 1161467

Summary: Got error sometimes during start a stopped aerogear app
Product: OpenShift Online Reporter: Yan Du <yadu>
Component: ImageAssignee: Vojtech Vitek <vvitek>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 2.xCC: bparees, hripps, jokerman, kpiwko, matzew, mmccomas, vvitek
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: 2015-02-18 16:52:53 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:
Embargoed:
Attachments:
Description Flags
development.log none

Description Yan Du 2014-11-07 08:04:45 UTC
Description of problem:

[root@Daphne test]# rhc app stop push1
RESULT:
push1 stopped

[root@Daphne test]# rhc app start push1
A gear start did not complete on 1 gear. Please try again and contact support if the issue persists.


[root@Daphne test]# rhc app force-stop push1
RESULT:
push1 force stopped

[root@Daphne test]# rhc app start push1
A gear start did not complete on 1 gear. Please try again and contact support if the issue persists.



Version-Release number of selected component (if applicable):
devenv_5284



How reproducible:
70%



Steps to Reproduce:
1.Create an aerogear app from website
2.rhc app stop/force stop $app
3.rhc app start $app



Actual results:
when start an stopped aerogear app, the start process last a long time, and got some error like "A gear start did not complete on 1 gear. Please try again and contact support if the issue persists." sometimes.



Expected results:
App could start/stop normally in a short time without any error



Additional info:
Got some error in development.log, please check the attachment.

Comment 1 Yan Du 2014-11-07 08:07:22 UTC
Created attachment 954812 [details]
development.log

Comment 2 Andrea Vibelli 2014-11-11 09:07:09 UTC
(In reply to Yan Du from comment #1)
> Created attachment 954812 [details]
> development.log

Hi, 
could you please confirm me that the issue was found on the aerogear cartridge, not the jboss-unified-push?

I have tried to reproduce the issue with the jboss-unified-push cartridge, and after 20 tries I could not get any error with the steps above.

Looking at the log, I see both openshift-origin-cartridge-aerogear-push and jboss-unified-push-openshift-cartridge cartridges, however the error "A gear start did not complete on 1 gear" seems related only to aerogear-push/bin/control start.

If you can confirm this, we will focus on the openshift-origin-cartridge-aerogear-push version (which runs on WildFly).
Thanks!

Comment 3 matzew 2014-11-11 12:57:35 UTC
Hi Ben, Yan,

the aerogear/openshift-origin-cartridge-aerogear-push has sosme issues
https://bugzilla.redhat.com/show_bug.cgi?id=1158830

I tested a few times (start/stop) with this cartridge:
https://github.com/jboss-mobile/jboss-unified-push-openshift-cartridge

and it worked great.

If as a consequence the "aerogear/openshift-origin-cartridge-aerogear-push" is "removed" disabled, that's fine. As said, I reported other issues already against the broker, based on tests with "aerogear/openshift-origin-cartridge-aerogear-push"

Comment 4 Karel Piwko 2014-11-11 14:59:50 UTC
Hi guys,

I've performed same testing with jboss-mobile cartridge and it's working fine. So I guess this affect only aerogear community cartridge.

kpiwko@kpiwko-x220 ~/devel/mobile/jbossqe-mobile ±master⚡ » for i in `seq 0 20`; do for task in stop start force-stop start; do rhc app $task manualtesting -n mobileqa; done; done
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started
RESULT:
manualtesting stopped
RESULT:
manualtesting started
RESULT:
manualtesting force stopped
RESULT:
manualtesting started

Comment 5 Ben Parees 2014-11-11 17:56:28 UTC
reassigning and reducing severity in light of this not affecting the unified push cartridge, only the community cart.

Comment 6 Vojtech Vitek 2014-12-05 05:02:35 UTC
> /bin/sh -c \"set -e; /var/lib/openshift/545c782c1cb5f3858a00001c/aerogear-push/bin/control start \""' exceeded timeout of 204 (pid:126)

I could only see the above timeout error in the provided development.log. Since this bug seems to be related to (or duplicate of) bug 1158830, which is VERIFIED now, I'm moving this ON_QA as well.

Comment 7 Yan Du 2014-12-08 08:37:35 UTC
Test on latest devenv_5345

aerogear app could be started/stopped/force_close/restart normally without any error.

Move bug to verified.