Multipath VM raw images on LVM proxmox 8.3.3

[dhcolesj]

Not sure this is in the right place, but I have installed and setup ProxMox, and using 8.3, and Multpath with LVM for shared storaage.
I have created 2 templates and used the last to deploy a VM and when I run "pvs" from the console I see this:
# pvs
WARNING: Device mismatch detected for vmdatavg/vm-100-disk-0 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-100-disk-1 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-101-disk-0 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-101-disk-1 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-100-cloudinit which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-102-disk-0 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
WARNING: Device mismatch detected for vmdatavg/vm-102-disk-1 which is accessing /dev/sdad instead of /dev/mapper/mpatha.
PV VG Fmt Attr PSize PFree
/dev/mapper/mpatha vmdatavg lvm2 a-- <2.00t <1.65t
/dev/sdy3 pve lvm2 a-- <446.10g 16.00g

I'm not sure what I missed, but could someone direct me to what's up?

I've also noticed in the /etc/lvm/lvm.conf file there are now 2 "device { }" sections, the original, and one proxmox has added, so I'm wondering if my "filter = [ "a|/dev/mapper/|", "a|/dev/sdy.*|", "r|.*|" ]" line needs to be in the original, or in the one proxmox added with the "global_filter"

Other than that it's all pretty standard, I have the PURE udev rules (from PURE), and the services installed "multipath-tools" and "lsscsi", etc.

When the vm disks were created I selected the "VMData01" storage at the DataCenter level, etc. etc.

What's interesting is that vm-102 and vm-101 have cloudinit storage as well, but they're apparently using the mpatha.

 

[dhcolesj]

OK, well, right after posting this, I edited the definition of the VMs to remove disks on local-vm storage, and for odd reasons, the WARNING messages above are gone.
Very weird, and still has me puzzled.
NOTE: None of the vm disks shown above were on local storage. The cloudinit (which I thought was on VMdatavg, turned out not to be, so I moved it, and made sure the rest were the same.