timer not respected on UC20

Bug #1944014 reported by Oliver Grawert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Medium
Unassigned

Bug Description

Even though i have set a timer to refresh only between 4-7am the system refreshed 5 snaps today (which resulted in 4 unwanted reboots) during operation, this is definitely unexpected

$ snap refresh --time
timer: mon-fri,4:00-7:00
last: today at 23:41 UTC
next: n/a

$ snap changes
ID Status Spawn Ready Summary
1049 Doing today at 23:41 UTC - Auto-refresh 5 snaps
...

the content of change 1049 in case this is relevant:

https://paste.ubuntu.com/p/mRkfWNY9Qr/

Oliver Grawert (ogra)
summary: - timer not respected onn UC20
+ timer not respected on UC20
Revision history for this message
Ian Johnson (anonymouse67) wrote :

What is `snap get -d system`?

Revision history for this message
Oliver Grawert (ogra) wrote :

the output of "snap get -d system":

https://paste.ubuntu.com/p/fHM2TGTdXr/

Revision history for this message
Ian Johnson (anonymouse67) wrote :

Well I can't see anything that would obviously cause this, your timezone setting and the refresh.timer seem to imply that snapd should not have started/attempted the refresh so something is clearly wrong. If you could share snapd logs and also possibly turn on SNAPD_DEBUG=1 so if it happens again we can get more verbose logs that would be great, but as-is I don't see any indication as to why this refresh was performing at that time.

Revision history for this message
Paweł Stołowski (stolowski) wrote :

I talked to the team and similar issues were already reported and we know auto-refresh has some confirmed problems in that it doesn't always respect refresh window. According to Samuele this isn't a simple fix though and needs more effort to address properly, so it's something likely to be considered for next development cycle. I'm marking this confirmed.

Changed in snapd:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.