-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-10.0
-
python-blivet-3.10.0-17.el10
-
No
-
Important
-
rhel-storage-management
-
ssg_filesystems_storage_and_HA
-
7
-
10
-
2
-
False
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
None
What were you trying to do that didn't work?
Installation of RHEL-10 using kickstart with thin LVM partitioning on a system already containing a thin LVM partitioning failed with an error:
The object with LVM ID 'data/thinp' doesn't exist
where data/thinp comes from the existing partitioning.
What is the impact of this issue to you?
It's not possible to install RHEL-10 with thin LVM partitioning if there already is an existing one.
Please provide the package NVR for which the bug is seen:
python3-blivet-3.10.0-9.el10 (anaconda-40.22.3.13-1.el10)
How reproducible is this bug?:
100%
Steps to reproduce
- Install a RHEL-10 system using kickstart that uses the following partitioning:
part /boot --fstype="xfs" --ondisk=vda --size=1024 part biosboot --size=1 --fstype=biosboot part pv.1 --fstype="lvmpv" --ondisk=vda --size=7000 volgroup rhel --pesize=4096 pv.1 logvol none --fstype="None" --size=1 --grow --thinpool --metadatasize=4 --chunksize=65536 --name=thinp --vgname=rhel part pv.2 --fstype="lvmpv" --ondisk=vda --size=2048 volgroup data --pesize=4096 pv.2 logvol none --fstype="None" --size=1 --grow --thinpool --metadatasize=4 --chunksize=65536 --name=thinp --vgname=data logvol / --fstype="xfs" --size=1 --grow --name=root --vgname=rhel --thin --poolname=thinp logvol swap --fstype="swap" --size=1024 --name=swap --vgname=rhel --thin --poolname=thinp
- Reinstall the system using kickstart (you can use the same one as for the first installation, but it looks like it's not necessary).
Expected results
Anaconda/blivet is able to remove the existing partitioning flawlessly and performs a new installation according to kickstart.
Actual results
Installation fails with an error in partitioning stage.
Additional notes
This bug was actually discovered during pre-verification of RHEL-45181.
Manual installation with automatic partitioning went through fine in the partitioning phase. Kickstart installations seem to fail no matter what the partitioning is (tried with plain LVM and autopart).
The obvious workaround is to remove the existing partitioning (e. g. by using wipefs tool) prior to the actual installation.
- duplicates
-
RHEL-95367 Cannot reinstall system with kickstart, getting "The object with LVM ID xxx doesn't exist"
-
- Closed
-
-
RHEL-82794 [RHEL10] blivet.errors.LVMError: The object with LVM ID 'vg00/lv_var' doesn't exist
-
- Closed
-
- is cloned by
-
RHEL-84662 [RHEL9] blivet.errors.LVMError: The object with LVM ID 'data/thinp' doesn't exist
-
- Release Pending
-
- links to
-
RHBA-2025:148038 python-blivet update