Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.7.5, 7.4.0
-
2
-
Severity 3 - Minor
-
1
-
Description
Issue Summary
During initial sync, farm vet tries to fix git content inconsistency even though repository is already in sync.
Steps to Reproduce
- Start Bitbucket primary and authorize a mirror (stand-alone or farm) to connect to it.
- Create a project and a repository inside it.
- Push some content to repository
- Add this project on mirror and wait for it to finish syncing.
- Shut down mirror
- Push another commit to the same repository
- Restart mirror with debug logging enabled.
- Wait for mirror to be in SYNCHRONIZED state.
- Search for logs containing "Detected content inconsistency in repository"
Expected Results
There should be no such logs as no new content has been pushed for that repository during mirror startup.
Actual Results
Following lines were noticed in logs which shows that even after initial sync was complete farm vet though content is inconsistent and ran snapshot sync.
2020-07-28 11:38:37,440 INFO [initial-sync-queue-poller:thread-1] c.a.b.i.m.m.f.s.InitialSyncHelper Initial Synchronization for [20] complete 2020-07-28 11:38:37,441 INFO [initial-sync-queue-poller:thread-1] c.a.b.i.m.m.f.s.InitialSyncHelper Repository synchronization complete. Running farm vet 2020-07-28 11:38:37,441 DEBUG [initial-sync-queue-poller:thread-1] c.a.b.i.m.mirror.vet.DefaultFarmVet Running farm vet 2020-07-28 11:38:37,566 DEBUG [initial-sync-queue-poller:thread-1] c.a.b.i.m.mirror.vet.VetContext Detected content inconsistency in repository: [20], repairing
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available.