…imary

This is a direct commit to nautilus branch to recreate the
behaviour we have post-nautilus, after refactoring made in
8a8947d, which seems to be
correct.

The in-flight backfill prevents updating of "backfill complete"
position, which remains on the object before the missing oid. So
when pg is re-peered it retries backfill from this position
instead of entering the clean state.

Fixes: https://tracker.ceph.com/issues/50747
Signed-off-by: Mykola Golub <mgolub@suse.com>

In PrimaryLogPG::on_failed_pull, we unconditionally remove soid
from recovering list, but remove it from backfills_in_flight only
when the backfill source is the primary osd.

Fixes: https://tracker.ceph.com/issues/50351
Signed-off-by: Mykola Golub <mgolub@suse.com>
(cherry picked from commit 9b78e00)

The osd may be 0.

Signed-off-by: Mykola Golub <mgolub@suse.com>
(cherry picked from commit 93139db)

Fixes: https://tracker.ceph.com/issues/50925
Signed-off-by: Mykola Golub <mgolub@suse.com>
(cherry picked from commit 0a9f7e1)

Conflicts:
    qa/suites/rados/singleton/all/ec-backfill-unfound.yaml:
        log-whitelist instead of log-ignorelist