Fedora Account System
Red Hat Associate
Red Hat Customer
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.
Created attachment 954812 [details] development.log
(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!
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"
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
reassigning and reducing severity in light of this not affecting the unified push cartridge, only the community cart.
> /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.
Test on latest devenv_5345 aerogear app could be started/stopped/force_close/restart normally without any error. Move bug to verified.