Bug 957841
| Summary: | Not able to delete an application | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Nam Duong <nduong> |
| Component: | Master | Assignee: | Rajat Chopra <rchopra> |
| Status: | CLOSED WORKSFORME | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.x | CC: | bemoelle, jofernan, lmeyer, sannam |
| 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-07-11 22:18:25 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: | |||
|
Description
Nam Duong
2013-04-29 16:58:40 UTC
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. |