Why does Proxmox not want to work with storage on storage?

Question

linux

There is a storage system (Dell MD3600f). Two Proxmox servers are connected to it via FC (multipath), storing virtual disks in LVM volumes. I connect a third server, configure iscsi, multipath - multipath detects paired devices and mounts them, as expected, in / dev / mapper. But when it comes to pvdisplay, I see the following:

File descriptor 7 (pipe:[57622]) leaked on pvdisplay invocation. Parent PID 6642: bash
connect() failed on local socket: No such file or directory
Internal cluster locking initialization failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
--- Physical volume ---
PV Name /dev/mapper/36c81f660e53d7e00220309ee04769705-part3
VG Name pve
PV Size 536.00 GiB / not usable 1.98 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 137215
Free PE 4043
Allocated PE 133172
PV UUID vLDITo-c7Ez-jK2W-WxNV-X71r-28cJ-3Q8c0b
Skipping clustered volume group mail
Skipping clustered volume group shared_vm2
Skipping clustered volume group vg-voip2
Skipping clustered volume group vg-voip1
--- Physical volume ---
PV Name / dev / mapper / 3690b11c0005284f7000002f453761f41
VG Note VG00
PV Size 100.00 Gib / Not USABLE 4.00
MIB Allocatable Yes
PE Size 4.00 MIB
Total PE 25599
Free PE 12799
Allocated PE 12800
PV UUID KZFedo-BTU6-JZ6R-KQEF-E485-GFAL-SPOXTB
Skipping clustered volume group vg-video
Skipping clustered volume group vg-voip3
Skipping clustered volume group vg-vm
Skipping clustered volume group vg_shared_main
Skipping clustered volume group vg_shared_db

Accordingly, all storages located in the storage system are in the "Skipping clustered volume group" state. How to win?

Answer 1

And the third server is included in the same cluster as the first two hosts?