snapd_refresh defaults to "max", meaning only monthly snap updates
Bug #1833416 reported by
Tom Haddon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Control Plane Charm |
Fix Released
|
Low
|
Kevin W Monroe | ||
Bug Description
The default setting for snapd_refresh in the kubernetes-master charm is "max", which means only monthly snap updates. This means it could be up to a month after snap updates are released before people get an update.
This was noticed as part of looking at https:/
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #1 |
| Changed in charm-kubernetes-master: | |
| status: | New → Triaged |
Revision history for this message
| Tim Van Steenburgh (tvansteenburgh) wrote | #2 |
| Changed in charm-kubernetes-master: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Kevin W Monroe (kwmonroe) |
| milestone: | none → 1.16 |
| importance: | Undecided → Low |
| Changed in charm-kubernetes-master: | |
| status: | In Progress → Fix Committed |
| Changed in charm-kubernetes-master: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The 'max' value was intentionally set as the default refresh interval. While it's true that updates could be delayed for up to a month, it also offers some protection against clusters being auto-upgraded to a broken upstream release (which happened in the 1.10.x cycle).
I think we should resolve this bug with documentation about the existence of this setting, what it means, and how to change it if needed. First pass at a doc PR is here:
https:/