gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-10 02:25:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add backup permissions fix for v4→v5 upgrades

Browse Source 
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
This commit is contained in:
rcourtman
2025-12-24 16:33:01 +00:00
parent a9078e96d1
commit 2c76cdaa43
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/UPGRADE_v5.md
+16
View File
@@ -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.