Description of problem: OSD crash in release_op_ctx_locks. Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Run workload against rgw 2. Take pool snapshots of all rgw pools 3. Actual results: OSD crashes Expected results: OSD does not crash Additional info: Use of pool snaps with radosgw is fairly rare.
Release flag is set for 1.3.1, but this should be documented in Release notes for 1.3.0 as Known issue so that customers dont try this config. Thanks Sam for bringing this up in iirc.
hammer sha1's: 4cdc5f7d6b3ec488c79c09cb44a43d4d9398b74c 1550a569dab120ce28396fe365565e8e4acd9801 c7b6a6370a69149ea94f9e35d536aa90f06e7659 bfb144268b803340efad29cd6c627b170ea32402
Ran some multipart uploads, bucket creation/deletion as rgw workload and created snaps of all rgw pools. Works fine. Didn't find any issues on OSDs. Verified.
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, 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-2015:2512
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, 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-2015:2066