New installation F40 with dual encrypted disk

Hi everyone,
due to a mishap, I lost /boot, home is intact so I thought “easy peasy” I just reinstall it so I take it as an occasion to do a fresh install (I do them anyway every 2/3 dnf upgrades).
The problem is that the disk partitioning tool doesn’t want to handle the encrypted device correctly. If I select custom, I try to unlock the encrypted partition (it’s a luks2 part and lvm within) it doesn’t seem to be doing nothing and I’m not shown the unencrypted LVs. If I switch to the console, I can see the luks2 partition is open and the lv devices available. If I do a refresh on the gui, I can then see them, but when I need to apply the changes, it returns an error saying that they need a password for the device (or something about not able to use a blank password). More or less the same happens with the blivet gui.
I can see in the logs that blivet complains about some unresponsive devices, but I’m not sure if it’s the cause of this behaviour.
BTW the same happens with the other encrypted disk.

Could I eventually try to use a newer disk installer (rawhide) to see if it works but then how do then install F40 and not Rawhide?

PS: the encrypted partitions are fine, I can open them manually via console and mount the fs.
These are LUKS2 devices in case it matters.

UPDATE: I had to disconnect the two data HDDs with RAID/LUKS/LVM on them so Anaconda wouldn’t barf. Then Anaconda could successfully decrypt and reuse the existing LUKS/BTRFS volume on the OS SSD and add a new subvolume for F41.

The same thing happens for me with a new F41 install onto an existing luks encrypted btrfs volume. After selecting custom partitioning, select the encrypted partition, and entering the luks passphrase, it momentarily unlocks the partition (I can see it in /dev/mapper/luks-*), then the luks mapping disappears from /dev/mapper and anaconda cannot find the btrfs volume inside. I’m stuck and cannot install a new Fedora onto this disk now, and I can’t boot the old F39 unless I can get grub reinstalled since a Windows 11 update erased the grub bootloader.

I opened this bz some time ago. Unfortunately I couldn’t reproduce it so far. Maybe I’ll give it another go.