Back to bug 1784895

Who When What Removed Added
Jason Dillaman 2019-12-18 15:43:40 UTC Status NEW ASSIGNED
Target Release 5.* 4.0
Blocks 1783415
Jason Dillaman 2019-12-18 15:45:00 UTC CC mkasturi
Flags needinfo?(mkasturi)
Jason Dillaman 2019-12-18 15:45:32 UTC Status ASSIGNED POST
Link ID Ceph Project Bug Tracker 41036
Hemant G 2020-01-02 09:56:55 UTC Keywords Regression
CC hgurav
Gopi 2020-01-02 10:00:16 UTC Keywords Regression
CC gpatta
QA Contact mkasturi gpatta
Jason Dillaman 2020-01-07 14:02:48 UTC Target Milestone rc z1
Tejas 2020-01-07 14:34:13 UTC CC tchandra
Flags needinfo?(mkasturi)
Jason Dillaman 2020-02-03 14:24:28 UTC Target Release 4.0 4.1
CC tserlin
Target Milestone z1 rc
Status POST MODIFIED
Jason Dillaman 2020-02-06 22:57:04 UTC Priority unspecified high
errata-xmlrpc 2020-03-13 20:14:41 UTC Fixed In Version ceph-14.2.8-3.el8, ceph-14.2.8-3.el7
Status MODIFIED ON_QA
Karen Norteman 2020-03-31 18:41:50 UTC CC knortema
Blocks 1816167
Karen Norteman 2020-04-14 14:39:33 UTC Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(jdillama)
Jason Dillaman 2020-04-14 18:04:05 UTC Doc Text Cause:
Concurrent unmapping of RBD block devices can result in udev event race conditions, leading to the "rbd unmap" CLI call failing.

Consequence:
One or more RBD block devices might remain mapped after the "unmap" call fails.

Fix:
The udev-related event race conditions have been fixed.

Result:
Concurrent "rbd unmap" calls should no longer sporadically fail, leaving RBD block devices mapped on a node.
Flags needinfo?(jdillama)
Harish Munjulur 2020-04-17 00:01:56 UTC CC hmunjulu
Hemanth Kumar 2020-04-17 04:38:50 UTC CC hyelloji
QA Contact gpatta hmunjulu
Harish Munjulur 2020-04-17 04:53:38 UTC Status ON_QA VERIFIED
Karen Norteman 2020-04-20 18:02:13 UTC Doc Text Cause:
Concurrent unmapping of RBD block devices can result in udev event race conditions, leading to the "rbd unmap" CLI call failing.

Consequence:
One or more RBD block devices might remain mapped after the "unmap" call fails.

Fix:
The udev-related event race conditions have been fixed.

Result:
Concurrent "rbd unmap" calls should no longer sporadically fail, leaving RBD block devices mapped on a node.
.If more than one `rbd unmap`command is issued concurrently, the commands might fail and the corresponding RBD block devices might remain mapped.

Previously, issuing concurrent `rbd unmap` commands could result in udev-related event race conditions. The commands would sporadically fail, and the corresponding RBD block devices might remain mapped to their node. With this update, the udev-related event race conditions have been fixed, and the commands no longer fail.
errata-xmlrpc 2020-05-19 15:12:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2020-05-19 17:31:24 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2020-05-19 17:31:24 UTC
errata-xmlrpc 2020-05-19 17:31:57 UTC Link ID Red Hat Product Errata RHSA-2020:2231
John Brier 2020-07-09 09:53:48 UTC CC jbrier
Doc Text .If more than one `rbd unmap`command is issued concurrently, the commands might fail and the corresponding RBD block devices might remain mapped.

Previously, issuing concurrent `rbd unmap` commands could result in udev-related event race conditions. The commands would sporadically fail, and the corresponding RBD block devices might remain mapped to their node. With this update, the udev-related event race conditions have been fixed, and the commands no longer fail.
.Multiple `rbd unmap` commands can be issued concurrently and the corresponding RBD block devices are unmapped successfully

Previously, issuing concurrent `rbd unmap` commands could result in udev-related event race conditions. The commands would sporadically fail, and the corresponding RBD block devices might remain mapped to their node. With this update, the udev-related event race conditions have been fixed, and the commands no longer fail.

Back to bug 1784895