snapd_refresh being set to max may prevent required snap upgrades
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Etcd Charm |
New
|
Undecided
|
Unassigned | ||
| Kubernetes Control Plane Charm |
New
|
Undecided
|
Unassigned | ||
| Kubernetes Worker Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
With the snapd_refresh set to the default of max my environment was set to update snaps 1 time per month. Unfortunately, right after the last update timeframe there was an update to canonical-livepatch which included a new certificate that was required for the livepatch service to continue working. With this default set, it would have been 3+ weeks before the canonical-livepatch snap was updated. Instead we decided to manually upgrade the canonical-livepatch snap in order to not wait.
It could easily be argued that a snap should be released with enough time for most scenarios to automatically update to the newest version before a breaking change, but this isn't something that can be always guaranteed. I also realize that the snapd_refresh config option is being deprecated in favor of the snap-store-proxy.
The request for this bug is either:
- remove the deprecated snapd_refresh option which has been deprecated since 1.19
- change the default to something more reasonable or set it to empty by default
- If the first two options aren't possible, then better document the potential fallout from this being set to max by default.
