mon: snap delete on deleted pool returns 0 without proper payload
It can lead to an abort in the client application since an empty reply w/o an error code is constructed in the monitor and the decode of the reply isn't wrapped with a try/catch block.
2018-05-03 18:58:44.207 7f9a28b11700 10 mon.a@0(leader).osd e104 attempt to operate on non-existent pool id 2
#2 Updated by Greg Farnum over 1 year ago
- Subject changed from Potential race with creating self-managed snapshot and pool deletion to mon: snap delete on deleted pool returns 0 without proper payload
- Category set to Correctness/Safety
- Status changed from Need Review to Verified
- Component(RADOS) Monitor added
Jason put a client-side handler in, but we should change the monitor as well so that we don't break older clients (or tell lies!).