Red Hat Bugzilla – Bug 966418
Unable to delete application from rhc
Last modified: 2013-07-11 10:51:34 EDT
Created attachment 752050 [details]
This is the most recent error in /var/log/openshift/broker/httpd/error_log after trying to delete the application
Description of problem:
When an application is created with rhc, and then interrupted (i.e. ctrl-c), the application will create, but one is not able to delete it using rhc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create any app using rhc
2.Interrupt the creation of the app
3.Use rhc to delete the app
The app is unable to be deleted, giving the error:
The server did not respond correctly. This may be an issue with the server configuration or with your connection to
the server (such as a Web proxy or firewall). Please verify that you can access the OpenShift server
The app should be deleted
I have attached some relevant log files, particularly /var/log/openshift/broker/httpd/error_log
I've been able to reproduce this so far.
Is there a specific cartridge type that you are seeing this with?
I see the reproducibility is intermittent, how frequently is it able to be reproduced? I tried creating, ctrl-c'ing, and deleting 20+ php-5.3 apps and didn't see the error when trying to reproduce.
Could you provide the mcollective and node related logs when you are able to reproduce this? (/var/log/mcollective.log and /var/log/openshift/node/*) These will give more detail into what steps are causing the failure, the Node Execution Failure is being returned by mcollective.
(In reply to Jason DeTiberus from comment #2)
> I've been able to reproduce this so far.
That should be I have not been able to reproduce this so far.
I'll spend some time this weekend and try to replicate it again. It's an intermittent issue, but it invariably has happened to each install we have locally.
Have you had any luck re-creating this with the latest code? If not, we should close this.
If you do get a chance to reproduce, in addition to the node logs mentioned, the broker production.log could have helpful information.
Thanks for the reminder to close this out. I've been unable to reproduce this with newer versions. If it does happen again, I'll be sure to post the logs. Thanks!