Comment 1 for bug 1856063
Revision history for this message
| Maciej Borzecki (maciek-borzecki) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Looks like it's a specific scenario for the core devices. I believe this happens:
- system seeding completes
- there's no previous refresh, so it falls back to the mod time of either the core snap or the snapd executable
- ensure loop runs every 5 minutes, so if that happens first the system will auto refresh
- calling `snap set system refresh.hold=..` triggers EnsureBefore(0), so it actually speeds up the auto refresh
In comparison, in cloud images, snapd automatically sets up refresh.hold=now+2h after seeding completes. Perhaps it's something we should do for newly seeded core images too. Some input from Mvo or Samuele would be useful here.