inhibit snap refresh under certain conditions (drone flying)

Bug #1635582 reported by Selene ToyKeeper on 2016-10-21
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

Could we take steps to ensure a device booted for the first time will not attempt to update snap-core and reboot until console-conf completes? This would prevent issues like spontaneously rebooting in the middle of the first-boot wizard... or on devices with only wifi, rebooting as soon as the network comes up.

Update: It sounds like there are other use cases where this will be relevant, not just console-conf. For example, connected cars often have a requirement not to do any updates while moving, and can only do those updates during a short window after parking with the engine off. Flying drones also need the ability to delay updates while in the air.

QA will also need to disable updates while running tests, but that can be done by the test harness via explicit sudo systemctl commands, so the QA story is probably out of scope for this bug.

description: updated
description: updated

The idea as I recall was that snaps could have a hook which gets called
in the runup to a refresh, which can defer it by up to a certain amount
of time.


Michael Vogt (mvo) wrote :

Thanks for your bugreport.

The reboot bug during console-conf got fixed, however as you point out there are more cases that we need to support.

summary: - inhibit snap refresh while console-conf is running
+ inhibit snap refresh under certain conditions (drone flying)
Changed in snappy:
importance: Undecided → High
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers