2.0.32 removed the 69-dm-lvm-metad.rules UDev rules file. The ".ID_FS_TYPE_NEW" UDev property is set in there. This property is used in lvmdbusd to detect LVM PV format remove with external tools like wipefs: https://sourceware.org/git/?p=lvm2.git;a=blob;f=daemons/lvmdbusd/udevwatch.py;h=b53b18003ee04619bf25be3231be949aac125a5e;hb=HEAD#l50
This is the part of the old udev rule. I don't have the best grasp of the logic here, but isn't .ID_FS_TYPE_NEW simply the same as ID_FS_TYPE? If so then the lvmdbus code could change to look at ID_FS_TYPE. # Detect removed PV label by comparing previous ID_FS_TYPE value with current one. ENV{.ID_FS_TYPE_NEW}="$env{ID_FS_TYPE}" IMPORT{db}="ID_FS_TYPE" ENV{ID_FS_TYPE}=="LVM2_member|LVM1_member", ENV{.ID_FS_TYPE_NEW}!="LVM2_member|LVM1_member", ENV{LVM_PV_GONE}="1" ENV{ID_FS_TYPE}="$env{.ID_FS_TYPE_NEW}" ENV{LVM_PV_GONE}=="1", GOTO="lvm_scan"
You are right, not sure why I missed this, ID_FS_TYPE and .ID_FS_TYPE_NEW are indeed the same. I tested it with ID_FS_TYPE and everything seems to be working fine.
Created attachment 1788723 [details] proposed fix
Thanks, pushed to dev-next branch. (https://sourceware.org/git/?p=lvm2.git;a=commit;h=2801b7a9b2faf08183685a79ec1dcee42d333541 will disappear when dev-next is rebased.)