Geo: Reverify/resync loop when primary checksum is incorrect
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
When a repo checksum is incorrect on the primary, the secondaries will constantly reverify (and fail) and then resync (successfully) to no avail, since the primary checksum won't get regenerated until either the repo changes, or until the Re-verification interval days passes since it was generated.
Perhaps there should be some feedback to the primary to cause a Reverification sooner in this case?
Edited by 🤖 GitLab Bot 🤖