Back to bug 999393
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Julie Pichon | 2013-08-21 09:31:45 UTC | Keywords | Triaged | |
| Assignee | rhos-maint | jpichon | ||
| RHEL Program Management | 2013-08-21 09:38:37 UTC | Target Release | --- | 4.0 |
| Nir Magnezi | 2013-08-21 11:05:19 UTC | Link ID | Launchpad 1214842 | |
| Julie Pichon | 2013-11-14 18:33:10 UTC | Target Release | 4.0 | 5.0 |
| Target Milestone | --- | Upstream M1 | ||
| John Skeoch | 2014-01-13 01:04:18 UTC | CC | hateya | |
| Julie Pichon | 2014-01-21 16:07:24 UTC | Status | NEW | POST |
| Doc Text | Cause: A container that is not empty cannot be deleted. A previous fix added a warning message that non-empty containers couldn't be deleted, but didn't stop the deletion success message from being displayed. Consequence: When deleting a container Horizon would display two contradictory messages: both a success message and a warning that the container couldn't be deleted. Fix: Ensure the success message isn't displayed when encountering conflicts such as the container not being empty on deletion requests. Result: A warning message (and only the warning message) is displayed, if the container couldn't be deleted because it wasn't empty. |
|||
| Julie Pichon | 2014-05-27 09:57:56 UTC | Status | POST | MODIFIED |
| Fixed In Version | python-django-horizon-2014.1-4.el7ost | |||
| Link ID | OpenStack gerrit 51970 | |||
| Alvaro Lopez Ortega | 2014-06-12 15:49:49 UTC | Status | MODIFIED | ON_QA |
| Amit Ugol | 2014-06-18 09:07:00 UTC | Status | ON_QA | VERIFIED |
| CC | augol | |||
| QA Contact | ajeain | augol | ||
| Deepti Navale | 2014-06-25 03:33:18 UTC | CC | dnavale | |
| Doc Text | Cause: A container that is not empty cannot be deleted. A previous fix added a warning message that non-empty containers couldn't be deleted, but didn't stop the deletion success message from being displayed. Consequence: When deleting a container Horizon would display two contradictory messages: both a success message and a warning that the container couldn't be deleted. Fix: Ensure the success message isn't displayed when encountering conflicts such as the container not being empty on deletion requests. Result: A warning message (and only the warning message) is displayed, if the container couldn't be deleted because it wasn't empty. | A container that is not empty cannot be deleted. Previously, two contradictory messages, one for success and one for warning that a non-empty container cannot be deleted were displayed when a user tried to delete a non-empty container. With this fix, only the warning message is displayed. | ||
| errata-xmlrpc | 2014-07-07 15:02:39 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-07-08 15:42:34 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-07-08 11:42:34 UTC | |||
| John Skeoch | 2015-02-15 22:02:29 UTC | CC | athomas |
Back to bug 999393