tmpfs storage config definitions fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
In Progress
|
Medium
|
David Negreira |
Bug Description
Running an install (Jammy) with an install definition that includes
```
autoinstall:
...
storage:
config:
...
- id: tmpfs
type: mount
spec: "none"
path: "/tmp"
fstype: "tmpfs"
options: "mode=1777,
```
Leads to the following error
```
File "/snap/
raise ValueError(
```
I traced this back to the curtin invocation in /var/log/
```
- path: /tmp
options: mode=1777,
spec: none
id: tmpfs
type: mount
```
Critically, the fstype entry has been removed, leading me to believe that the error is in the subiquity code.
This previously worked with earlier Jammy images.
Currently running subiquity 24.02.1 via the image at https:/
A potentially related bug report from 2023-10-28 https:/
I believe this was broken by this commit https:/
The commit removed the fstype parameter, the new code assumes a device, which does not work in the case of tmpfs when the device is None.
Changed in subiquity: | |
status: | New → Triaged |
importance: | Undecided → Medium |
no longer affects: | subiquity (Ubuntu) |
Changed in subiquity: | |
assignee: | nobody → Heather Lemon (hypothetical-lemon) |
I was able to verify and reverting the commit did indeed fix the issue.
I have submitted a PR [1] to revert the change, pending review/feedback from the team.
[1] https:/ /github. com/canonical/ subiquity/ pull/2049