subiquity generated storage config fails validation when ventoy is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Undecided
|
Olivier Gayot | ||
subiquity |
Fix Released
|
Undecided
|
Olivier Gayot | ||
ubuntu-desktop-installer |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Based on recent reports, there seems to be an issue when loading the desktop installer from a ventoy image. The server installer seems to be unaffected. The storage configuration based on the probert output is invalid because we seem to lack support for /dev/mapper/ventoy partitions.
Workaround: flashing the installer directly onto a USB stick (or other media) would be enough to work-around the issue but this needs to be confirmed.
2023-03-24 06:05:17,814 ERROR block-discover:847 block probing failed restricted=False
Traceback (most recent call last):
File "/snap/
await asyncio.
File "/snap/
return fut.result()
File "/snap/
return await meth(self, **kw)
File "/snap/
self.
File "/snap/
self.reset()
File "/snap/
self.
File "/snap/
tree = get_config_
File "/snap/
for dep in find_item_
File "/snap/
_validate_
File "/snap/
raise ValueError(
ValueError: Invalid dep_id (format-disk-dm-0) not in storage config
Here's a redacted excerpt of the probe-data that involves ventoy and causes the failed installed.
},
]
}
Related branches
- Dan Bungert: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 1535 lines (+1492/-0)3 files modifiedcurtin/storage_config.py (+9/-0)
tests/data/probert_storage_ventoy.json (+1458/-0)
tests/unittests/test_storage_config.py (+25/-0)
description: | updated |
summary: |
- generated storage config fails validation when ventoy is used + subiquity generated storage config fails validation when ventoy is used |
description: | updated |
description: | updated |
Changed in curtin: | |
status: | New → In Progress |
assignee: | nobody → Olivier Gayot (ogayot) |
Changed in curtin: | |
status: | In Progress → Fix Committed |
Changed in subiquity: | |
status: | In Progress → Fix Committed |
My attempts to reproduce the issue have some far been unsuccessful. I generated a ventoy image using ventoy-1.0.89 from Linux and tried the two following:
* Ventoy2Disk.sh -i /dev/sda -g <--- (gpt partition table)
* Ventoy2Disk.sh -i /dev/sda <--- (dos partition table)
I suspect that building the ventoy image from Windows might have a different result.
I would appreciate if someone affected could send us or detailed test-case (or maybe a `dd` of the media?) to reproduce the issue.