Bug 2102227 - [rbd-mirror] crash on assert in ImageWatcher::schedule_request_lock()
Summary: [rbd-mirror] crash on assert in ImageWatcher::schedule_request_lock()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RBD-Mirror
Version: 5.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 5.2
Assignee: Christopher Hoffman
QA Contact: Vasishta
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks: 2058223 2102272
TreeView+ depends on / blocked
 
Reported: 2022-06-29 13:47 UTC by Ilya Dryomov
Modified: 2022-08-09 17:39 UTC (History)
21 users (show)

Fixed In Version: ceph-16.2.8-77.el8cp
Doc Type: Bug Fix
Doc Text:
.Logic no longer causes RBD mirror to crash if owner is locked during `schedule_request_lock()` Previously, during `schedule_request_lock()`, for an already locked owner, the block device mirror would crash and image syncing would stop. With this fix, if the owner is already locked, `schedule_request_lock()` is gracefully aborted and the block device mirroring does not crash.
Clone Of: 2058223
Environment:
Last Closed: 2022-08-09 17:39:10 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 56549 0 None None None 2022-07-15 13:45:44 UTC
Red Hat Issue Tracker RHCEPH-4637 0 None None None 2022-06-29 14:03:28 UTC
Red Hat Product Errata RHSA-2022:5997 0 None None None 2022-08-09 17:39:56 UTC

Comment 17 Veera Raghava Reddy 2022-07-27 14:37:56 UTC
Thank you  Thomas.

Comment 22 errata-xmlrpc 2022-08-09 17:39:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5997


Note You need to log in before you can comment on or make changes to this bug.