DCO action / DCO (pull_request) Successful in 1m43sDetails
Vulncheck / Vulncheck (pull_request) Successful in 2m0sDetails
Tests and linters / Staticcheck (pull_request) Successful in 2m54sDetails
Build / Build Components (1.20) (pull_request) Successful in 2m49sDetails
Build / Build Components (1.21) (pull_request) Successful in 2m44sDetails
Tests and linters / Tests (1.21) (pull_request) Successful in 3m43sDetails
Tests and linters / Lint (pull_request) Successful in 3m58sDetails
Tests and linters / Tests (1.20) (pull_request) Successful in 23m28sDetails
Tests and linters / Tests with -race (pull_request) Successful in 29m0sDetails
It was introduced in 69e1e6ca to help node determine faulty shards.
However, the situation is possible in a real-life scenario:
1. Object O is evacuated from shard A to B.
2. Shard A is unmounted because of lower-level errors.
3. We now have object in meta on A and in blobstor on B. Technically we
have it in meta on shard B too, but we still got the error if B goes
to a degraded mode.
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>