16 KiB
Changelog
All notable changes to proxmox-manager / pman are documented in this file. Format follows Keep a Changelog. Versions follow Semantic Versioning.
Unreleased
Planned core version: 2.14.1 (prepared 2026-11-08; not published).
Fixed
- Configure SPICE through QXL only, preserve VGA properties and request authenticated connection files through the Proxmox proxy instead of inventing ports.
- Report failed VM/CT inventory queries with a nonzero exit status instead of returning an empty or partial successful listing.
- Discard stale worker input before displaying maintenance results, so fresh input after a cancelled diagnostic is retained.
- Isolate the Bash test viewer marker in its temporary test directory.
- Gate releases on Bash/Python tests, tag/core-version agreement and asset checksums.
Maintenance module 1.0.5
- Add a display language choice: German (default) or English. The installer asks
Language / Sprache [de/en]in a terminal or takes--lang de|en, stores it in/etc/pman/languageand keeps it on upgrades;PMAN_LANG=de|enoverrides it per run. All screens, messages, CLI help and diagnostic reports are translated; a completeness test fails when a text lacks an English entry.
Maintenance module 1.0.4
- Rework the Community Scripts menu: the source is named as Proxmox VE
Helper-Scripts (Community) with licence (MIT), website
https://community-scripts.organd repository URL; tools are grouped by intent and every entry carries a text hazard level ([LESEN],[ÄNDERT],[LÖSCHT]), not only a colour. - New confirmation screen: exact source URL, command, "runs as root on this
host", pinned revision and checksum.
vshows the verified script before it is started; exactly those bytes are then executed. - The maintenance menu marks changing actions (
[ÄNDERT]) and the Helper-Scripts entry ([FREMD], blue badge) the same way; the Helper-Scripts overview no longer repeats name and URL and lists the groups. - A blocked start now names the changed file and the reviewed/current revision instead of a generic message; the menu shows the last stored source check.
- Re-pin the reviewed Community Scripts revision (2026-11-04). Upstream had
changed
core.funcand four tools, which blocked every launcher. - Accessibility: no theme-dependent foreground colours any more (badges use fixed
256-colour pairs with a contrast of at least 4.5:1);
NO_COLOR,PMAN_ASCII=1(ASCII glyphs) andPMAN_HYPERLINKS=0|1(OSC 8 links, plain URL is always shown) are supported. Golden snapshot tests cover 80x24, 120x40 andNO_COLOR.
2.14.0 - 2026-10-28
Maintenance module 1.0.3
-
Refine the optional maintenance TUI with responsive action/detail views, clearer status and contextual keys, safe confirmation paging, and terminal restoration coverage.
-
Check community source metadata before confirmation; pinned hashes and a second live check remain required immediately before launch.
-
Fix community back-entry details and discard keys queued while a worker runs.
-
Add an optional Python/curses storage and maintenance module with a small Bash dispatcher (
--maintenance, main-menum, and guest-menum). -
Add host storage/SMART diagnostics, scoped CT/VM adapters, confirmed TRIM and Debian/Ubuntu CT package-cache cleanup. No automatic guest starts or broad cleanup.
-
Install the module independently with versioned atomic deployment and rollback; base installation no longer installs unrelated optional packages automatically.
-
Track declared Community Scripts reference revisions with a daily metadata-only checker. Native adapters run locally; selected community tools download and execute pinned upstream scripts after source and hash verification.
-
Add independent module bundles/checksums and Python/installer regression tests.
2.13.2 - 2026-10-21
Fixed
- Stop action (menu key 2) now runs
qm shutdown/pct shutdownwith--timeout STOP_TIMEOUT --forceStop 1: the guest is shut down cleanly and only hard-stopped by Proxmox once the timeout expires. Previously it calledqm stop/pct stop, which kills the guest immediately (like pulling the power plug); the--overrule-shutdown 1retry did not force anything either, it only aborts running shutdown tasks. - Tests:
qm/pctmocks log their calls (PMAN_MOCK_GUEST_LOG) and can fail on demand (PMAN_MOCK_GUEST_FAIL); new tests cover stop, its failure path, a declined confirmation and restart for VM and CT.
Changed
- CI:
actions/upload-artifact7.0.1 → 7.0.2.
2.13.1 - 2026-09-26
Changed
- README: health monitoring and alerts documented with screenshots; SMTP relay setup for e-mail alerts.
- CI: GitHub Actions dependency group bumped. No change to
proxmox-manager.sh.
2.13.0 - 2026-09-19
Added
--health(boxed),--health --listand--health --json: CPU, memory and disk usage, uptime and a health level per local VM/CT, read frompvesh get /cluster/resources; templates and guests on other cluster nodes are skipped.--filterand--nameapply.- Main menu key
hopens the health overview; the status action prints an extraHealth:line. --checkfor cron: alerts only on changes (new, escalated, improved, resolved) for resource thresholds (CPU afterHEALTH_CPU_RUNSconsecutive runs; resolved when the guest stops), guests stopped withonboot=1, guests whose latest lifecycle task does not explain a stop (stop, shutdown, suspend, migrate, destroy, backup), and failed node tasks (read with--source all). Nagios-style summary and exit codes 0 OK, 1 WARN, 2 CRIT, 3 UNKNOWN (also for usage errors).--dry-run(with--check) prints the result and the composed message without sending or writing state;--test-notifysends a test message.- Notifications via ntfy (
NTFY_URL, optionalNTFY_TOKEN_FILE) and e-mail through the localsendmail(HEALTH_MAIL_TO,HEALTH_MAIL_FROM); one combined message per run. - New config keys
HEALTH_{CPU,MEM,DISK}_{WARN,CRIT}(0disables a level),HEALTH_CPU_RUNS,HEALTH_IGNORE_IDS,HEALTH_STATE_DIR(default/var/lib/pman) and the notification keys above. - CI runs the test suite (
tests/run.sh); shell completions gained--name,--health,--check,--dry-runand--test-notify.
Changed
STOP_TIMEOUTandPROXMOX_MANAGER_SPICE_ADDRare validated after the command line is parsed.- With
--jsonthe--forcewarning goes to stderr, so the JSON output stays valid. - Outbound traffic is now possible, but only when notifications are configured (opt-in).
Security
- The ntfy access token is read from a
0600file owned by the caller in a directory nobody else can write; the open descriptor is verified before reading (no swap between check and use). An inlineNTFY_TOKENin a config file and a token with anhttp://URL are configuration errors. - The token, URL and headers reach
curlonly via its stdin config, never argv;curl -qignores~/.curlrc, redirects are not followed, a token forceshttpsonly, and requests are not retried. - Logs name only the ntfy host, never the topic path or the token.
- Mail headers are built from validated single-line values (no header injection).
- JSON output escapes all control characters;
_truncatenever cuts inside a UTF-8 character. qm/pctconfig fallbacks run with a timeout; the--checklock descriptor is not inherited by child processes and the lock file is never truncated; the state directory's parent must not be group/world-writable.- The
--checkstate lives in a0700directory, is written atomically with mode0600, is parsed as validated data (never sourced), and parallel runs are prevented withflock.
2.12.1 - 2026-09-19
Fixed
- Action and snapshot menus now draw a closed frame: every row is padded to the box width and gets a right border; long guest names in the menu titles are truncated instead of overflowing.
Changed
- README screenshots regenerated from v2.12.1 on a real PVE 9.2 host; the
obsolete, unreferenced
docs/screenshots/Screenshot.png(pre-2.8 UI) was removed.
2.12.0 - 2026-09-19
Security
- Configuration files are now parsed as allowlisted data instead of being
executed with
source. - Log files must be private, owner-controlled regular files; unsafe paths and symlinks are rejected.
- The system-wide
pmancommand is installed as an atomic root-owned copy instead of a symlink to a potentially user-writable checkout. - GitHub Actions are commit-SHA pinned, remote tool downloads are checksum-verified, workflow permissions are minimized, and checkout credentials are not persisted.
- User-controlled status and message text is no longer interpreted as
printf %bescape sequences.
Fixed
- Broken TUI frames (#33): header and table rows are now padded by visible
width, so right borders line up; the table gained a closing border, the NAME
column grows with long guest names (capped at the terminal width, then
truncated), and header/data columns are aligned in
--listoutput too. - The header showed
PVE: (runninginstead of the version; it now parsespveversioncorrectly and shows a compact uptime (e.g.12d 1h 25m). - VM IP lookup now accepts the native QEMU Guest Agent list payload from
qm agent ... network-get-interfacesas well as the earlier wrapped shape, preventing parser errors on hosts that return a bare JSON array. - Snapshot name validation now matches Proxmox
pve-configidrules before callingpct/qm; numeric-only and single-letter names are rejected locally with a clearer message. - SPICE
.vvfiles now prefer the actual SPICE bind address/port from Proxmox instead of always using the host LAN IP, preventing mismatched connection targets on loopback-bound SPICE setups. spice_info()no longer claims success launchingvirt-viewerfrom a non-graphical shell; it falls back to the.vvfile with a clear desktop-session hint.- VM console guidance now tells the user to follow the escape hint printed by Proxmox instead of hardcoding a potentially wrong key sequence.
Added
- New IP info menu item: shows current IPv4 addresses for running VMs and
CTs. VMs use the QEMU Guest Agent, CTs use
pct exec ... ip -j addr show, with clear fallback messages when no address is available.
[2.9.0 – 2.11.1] - 2026-04-09 – 2026-05-04
Consolidated notes for the releases between 2.8.4 and 2.11.1 (tagged v2.9.0
and v2026.05.04).
Added
--filter STATUSflag: filter--list/--jsonoutput torunning,stopped, orpausedinstances; invalid values exit 1 with a clear error message.--timeout SECSflag: set a timeout (default 60 s) for stop operations; on exit code 124 (timeout fired) automatically retries with--overrule-shutdown 1as a force-stop fallback.--forceflag: skip allconfirm()prompts automatically; prints a warning at startup and logs each bypassed prompt in yellow so the action is always visible.filtered_instances()wrapper aroundcollect_instances(); used byprint_tableandprint_jsonso filter logic is in one place.- Bash completion script:
completions/pman.bash— tab-completes all flags; suggestsrunning|stopped|pausedafter--filterand common timeout values after--timeout. - Zsh completion script:
completions/pman.zsh—_arguments-based with value specs for--filterand--timeout. - GitHub issue templates (YAML form format):
bug_report.yml,feature_request.yml. - GitHub
ISSUE_TEMPLATE/config.yml: blank issues disabled, link to Discussions. - GitHub
PULL_REQUEST_TEMPLATE.mdwith ShellCheck / test / changelog checklist. - GitHub
workflows/release.yml: auto-creates a GitHub Release withproxmox-manager.shas an asset on everyv*tag push. - GitHub
FUNDING.yml: GitHub Sponsors link for TimInTech.
Fixed
do_action restart: replaced manualstop → sleep 1 → startsequence with nativepct reboot/qm reboot— atomic, no unnecessary 1-second delay, cleaner error output.
Changed
type_of_id()now checks a global_type_cacheassociative array before queryingpct list/qm list; cache is populated as a zero-cost side-effect of the existingmain_menuinstance loop (no extra Proxmox call required).collect_instances(): replaced threeawk '{print $N}' <<<subshells per VM/CT with a single parameter-expansion trim +IFS=' ' read -r— eliminates 6 subshells per iteration.print_table"no results" message is context-aware: when--filteris active it shows "No <status> VMs or containers found." rather than the generic root-hint message.
2.8.4 - 2026-03-06
Fixed
validate_snapshot_name()now applied to rollback and delete operations (previously only enforced on create).snapshots_menu: rollback and delete show Proxmox error details via_rb_out/_del_outvariables, consistent with create.open_console: guard added for VM terminal — checksqm statusbefore callingqm terminal; printsCtrl+]exit hint before entering._pve_outcorrectly declaredlocalin stop and restart branches ofdo_action(); fixes potential variable bleed between branches.
Added
- Keyboard legend in the main menu (
<VMID>,r,q).
2.8.3 - 2026-03-06
Added
pmanglobal command:install_dependencies.shnow installs a symlink at/usr/local/bin/pman; idempotent.
Fixed
_pve_outdeclaredlocalin all do_action() branches.- Rollback and delete snapshot errors now captured and displayed.
- VM console guard:
open_consolechecks VM running status beforeqm terminal.
2.8.2 - 2026-03-06
Fixed
- Proxmox error details surfaced on start / stop / restart failure via stderr capture.
- Snapshot name validated before any Proxmox call (create path).
- UX polish: VMID-not-found message hints to press
rto refresh; empty Enter in action menu treated as "Back".
2.8.1 - 2026-03-06
Fixed
open_console: CT status checked beforepct enter; clear error if not running.
Added
print_tableappends colour-coded count line:Count: N running M stopped.header()shows system uptime viauptime -p.
2.8.0 - 2026-03-06
Changed
- Full modular rewrite:
collect_instances,print_table,print_json,do_action,snapshots_menu,spice_info,spice_enableseparated into distinct functions. - Status symbols changed to ASCII:
[+]running,[-]stopped,[~]paused,[?]unknown. - Output normalised to English throughout.
set -Eeuo pipefail+IFS=$'\n\t'+LC_ALL=Chardened at the top.confirm()added before all destructive actions (stop, restart, rollback, delete).log()added for optional structured file logging via$LOG_FILE.validate_vmid()added — rejects non-numeric or out-of-range VMIDs.header()shows node hostname and PVE version when available.- SPICE bind address configurable via
PROXMOX_MANAGER_SPICE_ADDR. --versionflag added.PROXMOX_MANAGER_ALLOW_NONROOT=1env var for CI / test environments.
[1.5.0] - (pre-rewrite)
Early version with basic console and snapshot management. Replaced by the v2.8.0 rewrite.