[Bug 1820604] Re: curtin fails to find itself in subiquity snap, when running on serial-subiquity at .service

[Michael Hudson-Doyle]

This is fixed now I think? I guess the livecd-rootfs change needs to go
back to bionic?

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: livecd-rootfs (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: subiquity
       Status: Confirmed => Fix Released

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1820604

Title:
  curtin fails to find itself in subiquity snap, when running on serial-
  subiquity at .service

Status in curtin:
  Invalid
Status in subiquity:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Triaged

Bug description:
  serial-subiquity at .service runs very differently to the tty1 subiquity.

  In seiral-subiquity@ case, it doesn't block starting on snapd as it
  doesn't use /usr/bin/snap run.

  Also, it doesn't execute subiquity.subiquity-service script, meaning
  that PATH setting there is not exported, causing troubles for curtin
  to reexec itself, or to find the right python in $PATH.

  
  Fix that in both livecd-rootfs & subiquity.

  https://github.com/CanonicalLtd/subiquity/pull/428
  https://code.launchpad.net/~xnox/livecd-rootfs/+git/livecd-rootfs/+merge/364888

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1820604/+subscriptions