Break out metadata sync so it doesn't rely on health of juju
Bug #1799850 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Repository Cache Charm |
Triaged
|
High
|
Unassigned | ||
Bug Description
Hi,
Had a whole bunch of environments reporting metadata out of date. Turns out it was to do with the JAAS controller used.
I think we should break out the sync process so it's not heavily tied into the health of Juju. Maybe just have juju leader-elections write out and update the leader on all u-r-c units but the cron job and sync process run from cron outside of 'juju-run' which is what it's currently configured to d.
Related branches
lp:~hloeung/ubuntu-repository-cache/allow-specifying-leader
- James Simpson: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 169 lines (+61/-29)4 files modifiedconfig.yaml (+5/-0)
lib/ubuntu_repository_cache/mirror.py (+43/-24)
lib/ubuntu_repository_cache/service.py (+9/-4)
lib/ubuntu_repository_cache/util.py (+4/-1)
Revision history for this message
| Haw Loeung (hloeung) wrote | #1 |
| Changed in ubuntu-repository-cache: | |
| status: | New → Triaged |
| importance: | Undecided → High |
To post a comment you must log in.
https:/
There's more work to be done, in particular removing the reliance on juju-run for triggering and pushing the latest metadata snapshot to peers.