mirror of
https://github.com/Joulenap/joulenap.git
synced 2026-08-11 13:21:43 +02:00
Catubba
74e8af2380
Which PVE storage points at which backup server is discovered, never typed — and until now it was only ever discovered while the Add-PVE wizard was open. Register a backup server afterwards, which is the entire point of the Add-PBS flow, and there was no way to complete the map from the interface: the wizard only ever creates so it refuses a host it already knows, the device editor renders storages read-only, and the connection test reads guests rather than storages. Backup routes onto that server stayed impossible, and the only way through was hand-editing YAML. Worse, the advice the product gave was actively harmful. Both the Add-PBS wizard's closing warning and the device editor's hint said to re-run "+ Add -> Proxmox VE" — which provisions a token *before* it fails on the duplicate id, so following it rotated the working host's token and then errored out, taking every backup route with it. Settings -> Devices -> edit the PVE -> Re-read from Proxmox now rebuilds the map with the credentials the device already has, matching each storage to a registered server by host and datastore. The map is replaced rather than merged, so a storage removed on the Proxmox side goes away here too; the ordinary save-time cross-reference check refuses a result that would leave an existing route without a mapping. Both strings now point at it.