curtin fails to find itself in subiquity snap, when running on serial-subiquity@.service
Bug #1820604 reported by
Dimitri John Ledkov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Invalid
|
Undecided
|
Unassigned | ||
subiquity |
Fix Released
|
Critical
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
serial-
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.
Fix that in both livecd-rootfs & subiquity.
https:/
https:/
Related branches
~xnox/curtin:snap-bin-curtin
- Ryan Harper (community): Needs Information
- Server Team CI bot: Needs Fixing (continuous-integration)
-
Diff: 22 lines (+4/-0)1 file modifiedcurtin/util.py (+4/-0)
Changed in curtin: | |
status: | Incomplete → Invalid |
description: | updated |
summary: |
- curtin fails to find itself in subiquity snap + curtin fails to find itself in subiquity snap, when running on serial- + subiquity@.service |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Confirmed |
tags: | added: id-5d1adb08f3b51440c727e268 |
To post a comment you must log in.
It's not clear to me why this is a bug; users shouldn't be driving the curtin in subiquity's snap themselves (right?), and the only evidence here is that that usecase breaks. Could you expand on what user-facing issue this is causing?
subiquity doesn't expose the curtin executable as an "app", so adding /snap/bin to PATH won't help. (Looking at the code, it will try using `which` before it tries constructing paths itself.)
The curtin binary being installed in /bin seems like a reasonable thing to support.