Fix #4635
closedmon: many ops expose uncommitted state
0%
Description
The prepare_update() methods are tricky because they need to make changes relative to uncommitted (pending) state. If they are a noop based on that state, they need to still wait for a commit, even though they aren't making an additional change. This isn't handled correctly in many of the OSDMonitor CLI commands... osd rm, osd crush rm to name just two.
A simple pattern that might make it easy to catch this is for a r=0 value at the end of the function to wait for a commit.
Updated by Sage Weil almost 11 years ago
- Translation missing: en.field_story_points set to 8.00
Updated by Sage Weil over 10 years ago
- Status changed from New to 12
- Source changed from Development to Q/A
teuthology-2013-08-02_01:00:11-rados-next-testing-basic-plana/93344 for a recent occurance
Updated by Joao Eduardo Luis over 10 years ago
- Assignee set to Joao Eduardo Luis
Updated by Joao Eduardo Luis over 10 years ago
We've fixed a couple of cases on the OSDMonitor and merged them into master. I'll keep this open for a while longer while I check for other potential cases and will close it if I find none.
Updated by Sage Weil over 10 years ago
- Target version changed from v0.68 to v0.68 - continued
Updated by Sage Weil over 10 years ago
- Status changed from In Progress to Resolved