infra-proxmoxlisted

# Proxmox VE Operations Reference (Release 9.1.2) Nodes, guests, and services can be down, unreachable, or vanish mid-operation. Never assume one is up: re-query real state, retry under a timeout, and degrade gracefully. For the self-healing patterns, see `bitranox:coding-resilience`. --- ## 1. Cluster Configuration (Auto-Detect) | Check | Command | |------------------|-------------------------------------------------------------------------------------------------| | **Environment** | `pveversion --verbose` (full component versions: kernel, pve-manager, corosync, qemu-server) | | **Nodes** | `pvecm nodes` (count, names, IDs) / `pvecm status` (IPs, quorum, transport, link states) | | **Quorum** | `pvecm status` -- check "Quorate" field. Threshold: `floor(total_nodes/2) + 1` | | **API Access** | `pvesh` (local CLI), `pveproxy` (HTTPS :8006), REST API. Use `--output-format json` for scripts | | **Storage** | `pvesm status` (active storages) / `cat /etc/pve/storage.cfg` (full config) | | **Network** | `pvesh get /nodes/{node}/network --output-format json` / `cat /etc/network/interfaces` | | **Subscription** | `pvesubscription get` (check status) / `pvesubscription set <key>` (apply key) | --- ## 2. Safety Protocols | Rule | Details