Comment # 44 on bug 1228863 from Marc Thomas

(In reply to Alberto Planas Dominguez from comment #42)
> (In reply to Marc Thomas from comment #41)
> > It seems after the rename of the file the enrollment no longer works.
> > 
> > localhost:~ # systemd-cryptenroll /dev/nvme0n1p2
> > 
> > No longer shows a TPM entry.
> 
> What file are you referring, initrd? No new initrd is generated?

Since I did the rename of initrd-a67e4f4c8aca4aa4f1b50919c64448ccb79b13b3 I had
issues enrolling the TPM again (see comment 39).
It did not ask for the recovery key but created a new initrd.
Also systemd-cryptenroll /dev/nvme0n1p2 did not show that the TPM was enrolled.

Somehow this is now working again and the TPM could be enrolled today.

Yes, secure boot is enabled:
localhost:~ # mokutil --sb-state
SecureBoot enabled

Did another unrenroll/enroll - nothing changed.
I have also attached the current pcrlock.

I would like to give a reinstall a try if you don't mind.
Nothing on the system is currently important - so it's quick and painless.
Could it also be that the fTPM is causing these issues?
Should I wipe that beforehand?