Status update: This bz appears to exhibit symptoms of one or both of two behaviors--1) metadata not advancing on one or more shards, due to lack of an error-handling strategy; 2) incremental sync inconsistency, at least partly correlated with a watch-notify update which fails and retries--possibly triggering a reversion to a stale state. For case #1, Casey is designing and implementing an error handling path for metadata sync. Fix will be downstreamed when ready (likely not this week). For case #2, Adam Emerson is expecting to send a new build immanently (probably on 7/12, as Adam is out with illness today). (Delete via LC is likely not behaving differently than other delete scenarios.)
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 5.1 Security, Enhancement, and Bug Fix 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:1174