Feature #10976

Updated by Samuel Just over 5 years ago

A common mistake upon osd loss is to remove the osd from the crush map before marking the osd lost. This tends to make it so that the user can no longer mark the osd lost to satisfy all_unfound_are_queried_or_lost. The simple solution is probably for all_unfound_are_queried_or_lost to ignore the osd if it does not exist. As a side note, the get_info usage there isn't quite valid since the osd might not still exist -- it needs to be guarded by an exists() check anyway.

This ticket includes extending the mark_lost_unfound_lost test to include this case.