Skip to content

Geo: Fix "Project/wiki/design repo not able to resync after storage move"

What does this MR do?

When a project is moved to a different shard for rebalancing load, a Geo secondary does not replicate the move, rather it used to be the case that the project would be resynced after e.g. a push, or re-verification has failed. The old storage would unfortunately retain an orphaned repo, which is why #9803 was opened.

But now, it appears there is an interaction with Praefect which prevents even the resync from working. See #9803 (comment 422414267) for the investigation of this problem.

This MR fixes the urgent problem of resyncing not working.

#260337 (closed)

Does this MR meet the acceptance criteria?


Availability and Testing

Edited by Michael Kozono

Merge request reports