mirror of
https://github.com/community-scripts/ProxmoxVE.git
synced 2026-11-03 20:14:31 +01:00
d77c65093b
vzdump and pct restore ran with their output thrown away, so a failed backup only said "Backup failed for container N" (exit 235). That is the second most common update-apps failure and none of them can be told apart. Keep the output in the run log and put its error line in the message, e.g. "CT is locked (backup)". var_backup_storage was matched with grep -w, so "truenas" passed when only "truenas-backup" exists and vzdump then failed on a storage that does not exist. Match the whole name, and list the valid ones in the error instead of a spinner line after it. Name the app in "Update failed for container N", so a failed update says which app's update failed. Declining the start dialog now exits 0 like the other tools instead of failing with whiptail's 1.