Handle partial metadata sync scenario
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Repository Cache Charm |
Triaged
|
High
|
Haw Loeung |
Bug Description
Hi,
We have this scenario where the leader unit successfully synced and verified a snapshot of the archive metadata, it syncs to it's peers but is then interrupted. On next sync, we see this:
| 2023-06-15 00:10:34,973 - Syncing /srv/ubuntu-
| 2023-06-15 00:10:34,973 - timeout 3600 /usr/bin/rsync -r --quiet --recursive --links --perms --chmod=g+w --times --compress --delete --delete-before --timeout=300 -e sudo -u www-sync ssh -l www-sync --link-
From the above, `ubuntu_active` is still pointing at `ubuntu_
Full logs - https:/
We should handle this by making sure the synced destination matches the source (or timestamp/meta_ver `ubuntu_active` currently points to).
Changed in ubuntu-repository-cache: | |
assignee: | nobody → Haw Loeung (hloeung) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in ubuntu-repository-cache: | |
status: | In Progress → Triaged |