subiquity crashes upon reusing existing full-disk raid member
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Undecided
|
Unassigned | ||
subiquity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
subiquity crashes upon reusing existing disks
https:/
get_blockdev_
An error occured handling 'disk-vdb': ValueError - disk 'disk-vdb' does not have correct partition table or cannot be read, but preserve is set to true. cannot continue installation.
finish: cmd-install/
TIMED BLOCK_META: 1.592
finish: cmd-install/
Traceback (most recent call last):
File "/snap/
ret = args.func(args)
File "/snap/
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File "/snap/
return func(*args, **kwargs)
File "/snap/
return meta_custom(args)
File "/snap/
handler(
File "/snap/
"cannot continue installation." % info.get('id'))
ValueError: disk 'disk-vdb' does not have correct partition table or cannot be read, but preserve is set to true. cannot continue installation.
disk 'disk-vdb' does not have correct partition table or cannot be read, but preserve is set to true. cannot continue installation.
My layout is:
vda - grub partition, /boot partition, raid0 member
vdb - whole disk raid0 member
It is correct that vdb does not have a partition table. But equally we don't need to create or touch things on vdb either.
Related branches
- Ryan Harper (community): Approve
- Server Team CI bot: Approve (continuous-integration)
- Dan Watkins (community): Approve
-
Diff: 46 lines (+15/-3)2 files modifiedcurtin/storage_config.py (+2/-2)
tests/unittests/test_storage_config.py (+13/-1)
summary: |
- subiquity crashes upon reusing existing disks + subiquity crashes upon reusing existing full-disk raid member |
tags: | added: reuse |
Changed in curtin: | |
status: | Invalid → New |
Yes; we can relax that restriction I suppose.