subiquity snap being updated kills subiquity

Bug #1724411 reported by Michael Hudson-Doyle
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
subiquity
Fix Released
Undecided
Unassigned
livecd-rootfs (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

By some sequence of events I don't understand, if a new version of subiquity is found and installed by snapd, the currently running one is killed and a shell session appears on tty1.

I think this is probably related to the snap.subiquity.started shenanigans we put it to try to fix the race condition.

Tags: iso-testing

Related branches

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I think this (and bug 1724410) could both be mitigated by disabling snapd.refresh.timer and given the timeframe maybe that's the best approach to take.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1724411

tags: added: iso-testing
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Taking snap.subiquity.started out of the After=/Requires= fixes this in my testing

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.478

---------------
livecd-rootfs (2.478) artful; urgency=medium

  [ Michael Hudson-Doyle ]
  * Two last minute server-live fixes:
    - Seed the subiquity snap to track the stable channel (LP: #1724410)
    - Remove snap.subiquity.started from subiquity's After=/Requires= as it
      does not fix the race condition they were intended to address and causes
      subiquity to be killed when snapd refreshes subiquity (LP: #1724411)

 -- Steve Langasek <email address hidden> Tue, 17 Oct 2017 22:08:38 -0700

Changed in livecd-rootfs (Ubuntu):
status: New → Fix Released
Changed in subiquity:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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