ubuntu-repository-cache_rsync cron job missing on leader
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Undecided
|
Unassigned | ||
Ubuntu Repository Cache Charm |
New
|
Undecided
|
Unassigned |
Bug Description
On two separate occasions I have seen the elected leader missing the ubuntu-
This appears to happen after "leadership failure: lease operation timed out" as per below.
It is possible to trigger re-rendering the cron job file by setting something like "juju config ubuntu-
2020-06-29 00:50:31 WARNING juju.worker.
2020-06-29 00:50:31 ERROR juju.worker.
2020-06-29 00:50:31 ERROR juju.worker.uniter agent.go:31 resolver loop error: could not acquire lock: cancelled acquiring mutex
2020-06-29 00:50:31 INFO juju.worker.uniter uniter.go:457 unit "ubuntu-
2020-06-29 00:50:34 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/
2020-06-29 00:50:34 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/
2020-06-29 00:50:36 INFO juju.worker.
2020-06-29 00:50:36 INFO juju.worker.
2020-06-29 00:51:24 ERROR juju.worker.
2020-06-29 00:51:24 INFO juju.worker.
2020-06-29 00:51:27 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/
2020-06-29 00:51:27 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/
2020-06-29 00:51:29 INFO juju.worker.
2020-06-29 00:51:30 INFO juju.worker.
2020-06-29 00:52:17 ERROR juju.worker.
2020-06-29 00:52:17 INFO juju.worker.
2020-06-29 00:52:22 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/
2020-06-29 00:52:22 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/
2020-06-29 00:52:24 INFO juju.worker.
2020-06-29 00:52:24 INFO juju.worker.
2020-06-29 00:53:12 ERROR juju.worker.
2020-06-29 00:53:12 INFO juju.worker.
2020-06-29 00:53:17 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/
2020-06-29 00:53:17 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/
2020-06-29 00:53:19 INFO juju.worker.
2020-06-29 00:53:19 INFO juju.worker.
2020-06-29 00:53:23 INFO juju.worker.
2020-06-29 00:53:24 INFO juju.worker.
2020-06-29 00:53:26 INFO juju.worker.
2020-06-29 00:53:27 INFO juju.worker.
2020-06-29 00:53:28 INFO juju.worker.
2020-06-29 00:53:29 INFO juju.worker.
2020-06-29 00:53:30 INFO juju.worker.
2020-06-29 00:53:31 INFO juju.worker.
2020-06-29 00:53:31 INFO juju.worker.
2020-06-29 00:53:32 INFO juju.worker.
2020-06-29 00:53:32 INFO juju.worker.
2020-06-29 00:53:33 INFO juju.worker.
2020-06-29 00:53:33 INFO juju.worker.
2020-06-29 00:53:35 INFO juju.worker.uniter uniter.go:246 unit "ubuntu-
2020-06-29 00:53:36 INFO juju.worker.uniter uniter.go:285 hooks are retried true
2020-06-29 00:53:43 INFO juju.worker.uniter resolver.go:130 found queued "leader-elected" hook
2020-06-29 00:53:45 INFO juju-log leader-elected fired. This unit is the new leader: ubuntu-
Changed in juju: | |
status: | New → Incomplete |
summary: |
- ubuntu-repository-cache_rsync missing on leader + ubuntu-repository-cache_rsync cron job missing on leader |
The charm relies on leadership election to ensure that only one unit has the cron job and that it is only running on one unit, the master. Adding the Juju project here. We've only started seeing these recently and likely to do with the upgrade to 2.7.6 across the board.