I got hold of the lease snapshots from IS, they look like this:
Earlier snapshot (taken at 2020-01-08T21:59:54.560)
global-time: 0001-11-28T14:46:13.032021499Z entries: ... ? namespace: application-leadership model-uuid: e951cb4a-9abf-420a-8ee0-4dcc7716dbe9 lease: canonical-livepatch : holder: canonical-livepatch/1816 start: 0001-11-28T14:46:00.03012772Z duration: 1m0s
Later snapshot (taken at 2020-01-08T22:03:08.582)
global-time: 0001-11-28T14:49:14.156856294Z entries: ... ? namespace: application-leadership model-uuid: e951cb4a-9abf-420a-8ee0-4dcc7716dbe9 lease: canonical-livepatch : holder: canonical-livepatch/1816 start: 0001-11-28T14:48:47.148564464Z duration: 1m0s
That makes it looks like the canonical-livepatch/1816 agent was still running and renewing its lease - there's nothing else that would be updating the start time like that.
So it seems like the bug is more likely to be with unit teardown somehow?
I got hold of the lease snapshots from IS, they look like this:
Earlier snapshot (taken at 2020-01- 08T21:59: 54.560)
global-time: 0001-11- 28T14:46: 13.032021499Z leadership 9abf-420a- 8ee0-4dcc7716db e9 livepatch/ 1816 28T14:46: 00.03012772Z
entries:
...
? namespace: application-
model-uuid: e951cb4a-
lease: canonical-livepatch
: holder: canonical-
start: 0001-11-
duration: 1m0s
Later snapshot (taken at 2020-01- 08T22:03: 08.582)
global-time: 0001-11- 28T14:49: 14.156856294Z leadership 9abf-420a- 8ee0-4dcc7716db e9 livepatch/ 1816 28T14:48: 47.148564464Z
entries:
...
? namespace: application-
model-uuid: e951cb4a-
lease: canonical-livepatch
: holder: canonical-
start: 0001-11-
duration: 1m0s
That makes it looks like the canonical- livepatch/ 1816 agent was still running and renewing its lease - there's nothing else that would be updating the start time like that.
So it seems like the bug is more likely to be with unit teardown somehow?