snapd seeding allows gadget snap to configure arbitrary system config options

Bug #1906830 reported by jcat on 2020-12-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Low
Unassigned

Bug Description

When setting snap config defaults via a gadget snap, you can also set system config defaults.

e.g.

defaults:
  system:
    watchdog.runtime-timeout: 1m
    watchdog.shutdown-timeout: 1m
    foo.bar: wibble

Currently, you can configure any arbitrary value there for the core system, and snapd will configure them. As opposed to setting them manually, where snapd will return an error "unsupported system option" and not set them if they are not supported.

Seeding failure would probably be too much, but perhaps the seeding process should at least log a warning regarding invalid config option, and refuse to set unsupported options.
[ note: I haven't tested validation of values for supported options, but perhaps that should be checked too ]

I honestly don't know if this is desirable or not, but am raising this as a bug for visibility, and if there is no desire to change the behaviour that's fine :)

snapd: 2.48.1
Ubuntu Core: UC20

Cheers,
Just

jcat (jcat) wrote :
Changed in snapd:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers