fix: Use per-node shared flag for storage deduplication

The storage deduplication logic only checked cluster config's Shared
flag, but this required the cluster config API call to succeed. When
the per-node storage API already returns shared=1 (as the user
verified), we should use that directly.

Now we check three sources for shared storage detection:
1. Per-node API shared flag (storage.Shared)
2. Cluster config shared flag (if available)
3. Storage type heuristics (NFS, RBD, PBS, etc.)

Related to #1049
This commit is contained in:
rcourtman 2026-01-07 10:16:23 +00:00
parent dcdbee3c5c
commit 9cfcdbb247
18 changed files with 164 additions and 42 deletions

View file

@ -47,6 +47,8 @@ volumes:
pulse_data:
```
> **Note**: Plain text passwords set via `PULSE_AUTH_PASS` are auto-hashed on startup. For production, prefer Quick Security Setup or a pre-hashed bcrypt value.
---
## 🛠️ Installation Methods