Back to bug 1786457
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Madhavi Kasturi | 2019-12-30 05:31:55 UTC | Keywords | TestBlocker | |
| Jason Dillaman | 2020-01-06 17:17:07 UTC | CC | jdillama | |
| Ernesto Puerta | 2020-01-08 13:48:53 UTC | Target Release | 4.0 | 4.1 |
| Link ID | Ceph Project Bug Tracker 43524 | |||
| Yaniv Kaul | 2020-01-08 14:07:37 UTC | Severity | urgent | high |
| Ernesto Puerta | 2020-01-14 10:18:12 UTC | Status | NEW | ASSIGNED |
| Link ID | Ceph Project Bug Tracker 38332 | |||
| Ernesto Puerta | 2020-01-14 10:21:57 UTC | Link ID | Github ceph/ceph/pull/32304 | |
| Madhavi Kasturi | 2020-01-21 11:13:49 UTC | Blocks | 1730176 | |
| Bara Ancincova | 2020-01-22 09:32:53 UTC | CC | epuertat | |
| Docs Contact | asriram | bancinco | ||
| Doc Type | If docs needed, set a value | Known Issue | ||
| Flags | needinfo?(epuertat) | |||
| Ernesto Puerta | 2020-01-22 16:27:56 UTC | Doc Text | Cause: If Ceph iSCSI returns an error (e.g.: 400 HTTP code when trying to delete an iSCSI target while a user is logged in), Ceph-Dashboard doesn't forward that error code and message to the Dashboard user (via pop-up notification), but displays a generic "500 Internal Server Error". Consequence: A Ceph-Dashboard user working with iSCSI will receive a poorly informative, and even misleading, message: an expected behaviour ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). Workaround (if any): The actual error message can be checked in Ceph Dashboard Logs. Result: | |
| Flags | needinfo?(epuertat) | |||
| Bara Ancincova | 2020-01-27 09:16:04 UTC | Doc Text | Cause: If Ceph iSCSI returns an error (e.g.: 400 HTTP code when trying to delete an iSCSI target while a user is logged in), Ceph-Dashboard doesn't forward that error code and message to the Dashboard user (via pop-up notification), but displays a generic "500 Internal Server Error". Consequence: A Ceph-Dashboard user working with iSCSI will receive a poorly informative, and even misleading, message: an expected behaviour ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). Workaround (if any): The actual error message can be checked in Ceph Dashboard Logs. Result: | .The Dashboard does not provide correct Ceph iSCSI error messages If the Ceph iSCSI returns an error, for example the "400 HTTP" code when trying to delete an iSCSI target while a user is logged in, the {product} Dashboard does not forward that error code and message to the Dashboard user using the pop-up notifications, but displays a generic "500 Internal Server Error". Consequently, the message that the Dashboard provides is not informative and even misleading; an expected behavior ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). To work around this issue, see the Dashboard logs. |
| Flags | needinfo?(epuertat) | |||
| Ernesto Puerta | 2020-01-27 09:25:46 UTC | Doc Text | .The Dashboard does not provide correct Ceph iSCSI error messages If the Ceph iSCSI returns an error, for example the "400 HTTP" code when trying to delete an iSCSI target while a user is logged in, the {product} Dashboard does not forward that error code and message to the Dashboard user using the pop-up notifications, but displays a generic "500 Internal Server Error". Consequently, the message that the Dashboard provides is not informative and even misleading; an expected behavior ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). To work around this issue, see the Dashboard logs. | .The Dashboard does not provide correct Ceph iSCSI error messages If the Ceph iSCSI returns an error, for example the HTTP "400" code when trying to delete an iSCSI target while a user is logged in, the {product} Dashboard does not forward that error code and message to the Dashboard user using the pop-up notifications, but displays a generic "500 Internal Server Error". Consequently, the message that the Dashboard provides is not informative and even misleading; an expected behavior ("users cannot delete a busy resource") is perceived as an operational failure ("internal server error"). To work around this issue, see the Dashboard logs. |
| Flags | needinfo?(epuertat) | |||
| Ernesto Puerta | 2020-02-18 17:32:52 UTC | Priority | unspecified | medium |
| Ernesto Puerta | 2020-02-25 12:13:30 UTC | Status | ASSIGNED | POST |
| Ernesto Puerta | 2020-02-25 12:15:45 UTC | Status | POST | MODIFIED |
| Ernesto Puerta | 2020-02-27 11:41:12 UTC | Status | MODIFIED | POST |
| Ernesto Puerta | 2020-02-27 11:52:56 UTC | CC | kdreyer | |
| Flags | needinfo?(kdreyer) | |||
| Sunil Angadi | 2020-03-05 06:03:31 UTC | CC | tserlin | |
| CC | sangadi | |||
| Sunil Angadi | 2020-03-12 13:44:41 UTC | QA Contact | mkasturi | sangadi |
| Hemanth Kumar | 2020-03-17 04:23:35 UTC | Status | POST | MODIFIED |
| Fixed In Version | ceph-14.2.8-3.el8, ceph-14.2.8-3.el7 | |||
| Flags | needinfo?(kdreyer) | |||
| CC | ceph-qe-bugs | |||
| Flags | needinfo?(ceph-qe-bugs) | |||
| CC | hyelloji | |||
| Flags | needinfo?(ceph-qe-bugs) | needinfo- | ||
| errata-xmlrpc | 2020-03-17 04:45:50 UTC | Status | MODIFIED | ON_QA |
| Karen Norteman | 2020-03-31 19:03:33 UTC | CC | knortema | |
| Blocks | 1816167 | |||
| Sunil Angadi | 2020-04-06 07:10:43 UTC | Status | ON_QA | ASSIGNED |
| Ernesto Puerta | 2020-04-14 11:00:48 UTC | Status | ASSIGNED | ON_QA |
| Sunil Angadi | 2020-04-15 06:54:52 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2020-05-19 15:12:15 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-05-19 17:31:40 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-05-19 17:31:40 UTC | |||
| errata-xmlrpc | 2020-05-19 17:32:13 UTC | Link ID | Red Hat Product Errata RHSA-2020:2231 |
Back to bug 1786457