-
Bug
-
Resolution: Unresolved
-
Normal
-
None
What were you trying to do that didn't work?
I tried to select a pre-existing VDO LV in custom partitioning. This results in anaconda traceback:
anaconda 40.22.3.17 exception report
Traceback (most recent call first):
File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 710, in _setup_device_type_combo
self._typeStore.append([_(DEVICE_TEXT_MAP[dt]), dt])
File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 804, in _populate_right_side
self._setup_device_type_combo(self._request.device_type, device_types)
File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 1389, in on_selector_clicked
self._populate_right_side(self._accordion.current_selector)
File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 343, in process_event
cb(old_selector, selector)
KeyError: 6
What is the impact of this issue to you?
Aborted installation, unable to re-use an existing VDO LV.
Please provide the package NVR for which the bug is seen:
RHEL-10.0-20241202.0
anaconda-40.22.3.17
How reproducible is this bug?:
Always
Steps to reproduce
- Create a VDO LV before starting a new installation:
# pvcreate /dev/vdb1 # vgcreate vdovg /dev/vdb1 # lvcreate --type vdo --name test-vdo --size 5g --virtualsize 10g vdovg
- Start a new graphical installation
- Proceed to the custom partitioning spoke
- Select the VDO LV
Expected results
Be able to modify the LV.
Actual results
Anaconda traceback.
- blocks
-
-
- Planning
-