Description of problem: After reviewing this forum thread: https://www.openshift.com/forums/openshift/i-am-not-able-to-access-and-even-not-able-to-delete-one-of-app-out-of-3-app-in-my and reaching out for more details of the application that the user is unable to delete, I went ahead and tried to delete all my applications as well. I ran into one application that I was not able to delete: openshiftdebug2-macdomain.rhcloud.com In attempting to delete (then subsequently force-stop) the application, the rhc client tools and web console doesn't respond. I also tried with the -d flag and didn't get anything back. --- rhc app delete openshiftdebug2 -d DEBUG: Authenticating with RHC::Auth::Token DEBUG: Connecting to https://openshift.redhat.com/broker/rest/api DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/api DEBUG: code 200 430 ms DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains DEBUG: code 200 130 ms DEBUG: Getting all domains DEBUG: Request GET https://openshift.redhat.com/broker/rest/domains/macdomain/applications/openshiftdebug2 DEBUG: code 200 162 ms This is a non-reversible action! Your application code and data will be permanently deleted if you continue! Are you sure you want to delete the application 'openshiftdebug2'? (yes|no): yes Deleting application 'openshiftdebug2' ... DEBUG: Deleting application openshiftdebug2 DEBUG: Request DELETE https://openshift.redhat.com/broker/rest/domains/macdomain/applications/openshiftdebug2 ^CInterrupted Nams-MacBook-Pro:sonar nduong$ ls README README.md webapps Nams-MacBook-Pro:sonar nduong$ cd .. Nams-MacBook-Pro:express nduong$ ls sonar Nams-MacBook-Pro:express nduong$ rhc app force-stop openshiftdebug2 Application is currently busy performing another operation. Please try again in a minute. ---
Just checked my account and the app is gone now. Please note that this is the second time I've seen this problem, as the first was reported here: https://bugzilla.redhat.com/show_bug.cgi?id=957440 Not sure how reproducible this is, but the app eventually gets deleted without any user intervention; although during the time, I tried to delete the app many times.
Reducing to medium given the latest info
Is it possible mcollective on the node was being restarted at the time of the delete request? This could wait for a long timeout and then retry, blocking other actions in the meantime.
I respectfully disagree with setting priority to low. The product appears broken. If we start charging for gears, and users can't delete an application, I sense some strong comments coming our way. Also, for any action that takes longer then a few seconds, we should have some kind of indicator of progress/status. I can't imagine anyone getting a sense of a good user experience when retrying after being stuck in this scenario.
Rather "severity" instead of "priority"
No recent reports of this issue. Likely issue was that lock was taken, and a retry was expected after 10 minutes.