Snappy

move boot-ok to before sessions

Bug #1507607 reported by John Lenton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snappy
Fix Released
Undecided
Unassigned

Bug Description

Currently boot-ok is After=multi-user.target, which means it comes after systemd-user-sessions.service, so people can log in. This means there's a window for people to break things unintentionally, if they run snappy before boot-ok is done.

We can't just make boot-ok "Before=systemd-user-sessions.service", because then it'd run too early (as anything post-boot would satisfy its req's).

I suggest we run boot-ok earlier, using Before=systemd-user-session.service, but After=cloud-init.service.

Leo Arias (elopio)
Changed in snappy:
status: New → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

Its now running as part of the snapd daemon itself.

Changed in snappy:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.