Back to bug 2153673
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Vasishta | 2022-12-15 06:29:27 UTC | Severity | medium | urgent |
| Vasishta | 2022-12-15 06:35:24 UTC | Keywords | Regression | |
| Red Hat One Jira (issues.redhat.com) | 2022-12-15 06:50:20 UTC | Link ID | Red Hat Issue Tracker RHCEPH-5795 | |
| Vasishta | 2022-12-15 07:21:04 UTC | Target Release | 6.1 | 5.3 |
| Vasishta | 2022-12-15 08:51:52 UTC | Keywords | TestBlocker | |
| Ilya Dryomov | 2022-12-15 11:06:13 UTC | Keywords | Regression | |
| Ilya Dryomov | 2022-12-15 11:15:36 UTC | Target Release | 5.3 | 5.3z1 |
| Vasishta | 2022-12-15 14:22:14 UTC | Keywords | TestBlocker | |
| Christopher Hoffman | 2022-12-16 17:55:30 UTC | CC | choffman | |
| Vasishta | 2022-12-19 02:47:45 UTC | Flags | needinfo?(idryomov) needinfo?(choffman) | |
| CC | idryomov | |||
| Red Hat Bugzilla | 2022-12-31 23:39:47 UTC | Assignee | idryomov | nobody |
| CC | idryomov | |||
| Red Hat Bugzilla | 2023-01-01 06:29:14 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:45:27 UTC | QA Contact | vashastr | |
| Manohar Murthy | 2023-01-03 13:33:40 UTC | QA Contact | vashastr | |
| CC | mmurthy | |||
| Alasdair Kergon | 2023-01-04 04:41:16 UTC | Assignee | nobody | idryomov |
| Alasdair Kergon | 2023-01-04 06:13:47 UTC | CC | choffman | |
| Alasdair Kergon | 2023-01-04 06:46:24 UTC | CC | idryomov | |
| Red Hat Bugzilla | 2023-01-09 08:30:37 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Ilya Dryomov | 2023-01-11 14:25:17 UTC | Assignee | idryomov | choffman |
| Status | NEW | ASSIGNED | ||
| Ilya Dryomov | 2023-01-11 14:30:20 UTC | Flags | needinfo?(idryomov) | |
| Christopher Hoffman | 2023-01-12 21:55:30 UTC | Flags | needinfo?(choffman) | |
| Scott Ostapovicz | 2023-02-06 16:56:14 UTC | CC | sostapov | |
| Target Release | 5.3z1 | 6.1 | ||
| Ilya Dryomov | 2023-03-21 16:52:40 UTC | Link ID | Ceph Project Bug Tracker 59115 | |
| Ilya Dryomov | 2023-04-11 12:13:10 UTC | Status | ASSIGNED | POST |
| errata-xmlrpc | 2023-04-13 05:53:24 UTC | Fixed In Version | ceph-17.2.6-11.el9cp | |
| CC | tserlin | |||
| Status | POST | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| Akash Raj | 2023-05-03 06:42:45 UTC | CC | akraj | |
| Flags | needinfo?(choffman) | |||
| Docs Contact | akraj | |||
| Vasishta | 2023-05-08 17:37:26 UTC | Status | ON_QA | VERIFIED |
| Christopher Hoffman | 2023-05-24 14:58:54 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Flags | needinfo?(choffman) | needinfo+ | ||
| Doc Text | Cause: If the client is blocklisted and also requested an exclusive lock, there's a case where the lock request is delayed. Consequence: If the client is blocklisted, the delayed request will not continue and the call that requested lock will never complete. Fix: The fix now detects if the client is blocklisted. Result: The stuck condition now completes with appropriate error code. |
|||
| Ranjini M N | 2023-06-13 10:49:07 UTC | Doc Text | Cause: If the client is blocklisted and also requested an exclusive lock, there's a case where the lock request is delayed. Consequence: If the client is blocklisted, the delayed request will not continue and the call that requested lock will never complete. Fix: The fix now detects if the client is blocklisted. Result: The stuck condition now completes with appropriate error code. | .Detect the blocklisted client Previously, if the client was blocklisted and requested an exclusive lock, the delayed request would not continue and the call that requested the lock would never complete. With this fix, the blocklisted client is detected and the stuck condition completes with an appropriate error code. |
| Blocks | 2192813 | |||
| CC | rmandyam | |||
| errata-xmlrpc | 2023-06-15 09:08:17 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:16:27 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-06-15 09:16:27 UTC | |||
| errata-xmlrpc | 2023-06-15 09:17:40 UTC | Link ID | Red Hat Product Errata RHSA-2023:3623 | |
| Akash Raj | 2023-06-21 09:32:47 UTC | Doc Text | .Detect the blocklisted client Previously, if the client was blocklisted and requested an exclusive lock, the delayed request would not continue and the call that requested the lock would never complete. With this fix, the blocklisted client is detected and the stuck condition completes with an appropriate error code. | .Detect the blocklisted client Previously, if the client requested an exclusive lock while blocklisted, the delayed request would not continue and the call that requested the lock would never complete. With this fix, the blocklisted client is detected and the stuck condition completes with an appropriate error code. |
Back to bug 2153673