osd-scrub-repair.sh fails due to num_objects wrong
A status check for "1/1 objects unfound" is coming back as "1/2 objects unfound"
Can be reproduced easily with:
./qa/run-standalone.sh "osd-scrub-repair.sh TEST_unfound_erasure_coded_appends"
#2 Updated by David Zafman 12 months ago
- Subject changed from osd-scrub-repair.sh fails due to num_objects wrong to The mon num_objects is off
- Status changed from Resolved to 12
Reopening to use for root cause fix. This tracker should also revert 10b9626ea7b.
The commit comment is wrong, because we are using a different EC Pool not the rbd pool. "..presumably due to the rbd pool init creating the rbd_directory."