Description of problem:
The installer fails to re-install a system with an existing LVM thin pool, which is corrupted.
Such a problem can be simulated by the following steps: (The created disk image is attached)

[root@localhost ~]# parted -s /dev/vdd mklabel msdos
[root@localhost ~]# parted -s /dev/vdd mkpart primary 0% 25%
[root@localhost ~]# pvcreate /dev/vdd1
[root@localhost ~]# vgcreate testvg /dev/vdd1
[root@localhost ~]# lvcreate -L 100M -T testvg/testpool
[root@localhost ~]# vgchange -an testvg
[root@localhost ~]# vgcfgbackup -f /root/backup testvg
[root@localhost ~]#

1. Now edit the backup file, change the transaction_id value for the testpool LV

[root@localhost ~]# vgcfgrestore -f /root/backup testvg --force
WARNING: Forced restore of Volume Group testvg with thin volumes.
Restored volume group testvg.
[root@localhost ~]#

Use the disk image and let anaconda reclaim disk space and create the partitions during the installation.
There is an error when anaconda starts preparing the partitions for the new installation:
"device path does not exist or is not writable"

Version-Release number of selected component (if applicable):
RHEL-8.6.0-20220128.0
anaconda-33.16.6.5-1.el8
python3-blivet-3.4.0-8.el8

How reproducible:
Always

Steps to Reproduce:
1. Use the attached disk image
2. Let anaconda delete the partitions and create new ones
3. Begin the installation

Actual results:
Error while activating the storage configuration:
"device path does not exist or is not writable"

Expected results:
The old partitioning is removed and new partitions are successfully created.

Additional info:
This bug could be related to bug 1856358.