From 2c76cdaa4397acb1e70a1c200f441e225db5ae34 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Wed, 24 Dec 2025 16:33:01 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20add=20backup=20permissions=20fix=20for?= =?UTF-8?q?=20v4=E2=86=92v5=20upgrades?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Users upgrading from v4 may have tokens that lack PVEDatastoreAdmin permission on /storage, causing backups to not appear. Added section to UPGRADE_v5.md with quick fix command and alternative approach (re-run agent setup). Related to #883 --- docs/UPGRADE_v5.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/UPGRADE_v5.md b/docs/UPGRADE_v5.md index 1622e63c8..dcb8c455a 100644 --- a/docs/UPGRADE_v5.md +++ b/docs/UPGRADE_v5.md @@ -64,3 +64,19 @@ Preferred option: Deprecated option (existing installs only): - `pulse-sensor-proxy` continues to work for now, but it is deprecated in v5 and not recommended for new installs. Plan to migrate to the unified agent. + +### Backups not showing after upgrade (v4 → v5) + +If your backups stop appearing after upgrading from v4, your existing API token may be missing the `PVEDatastoreAdmin` permission required for backup visibility. + +**Quick fix** (run on each Proxmox host): +```bash +pveum aclmod /storage -user pulse-monitor@pam -role PVEDatastoreAdmin +``` + +**Alternative** (re-run agent setup): +1. Delete the node from Pulse Settings +2. Re-run the agent setup command from Settings → Add Node +3. The new token will have correct permissions + +This happens because v5's agent setup grants broader permissions than the v4 manual setup scripts did.