Proxmox node package updates

NexoVirt can install Debian and Proxmox VE package updates on a node from the panel. The work is done by the NexoVirt agent on the node with apt-get. The node is never rebooted automatically.

Requirements

• An agent of version 0.23.0 or newer on the node.
• The agent must run on this node. In a cluster connection, the agent runs on the node you connected to; other members show a message that they need their own connection with an agent.

When a requirement is not met, the Updates card explains why and offers no update button.

Where to find it

• Hardware tab > Updates card: shows the number of available updates (from the last node facts scan) with Show packages, and an Install updates or Check for updates button.
• Overview tab > Health checks: the “update(s) available” check has an Install button.

Both open the System updates on <node> dialog.

Installing updates

1. Open the dialog. If an upgrade is already running on the node, the dialog shows its progress instead. Otherwise it runs apt-get update on the node (this can take a minute) and lists the upgradable packages with Package, Installed, New and Source. A badge warns when the updates include a kernel (a reboot is needed afterwards). Check for updates reloads the list at any time.
2. Choose what to install:
   • Install all updates runs a full apt-get dist-upgrade.
   • Or tick individual packages and click Install selected. Each change of the selection is simulated first: the dialog shows how many packages will be upgraded, which of them are required by your selection, and any new packages that will be installed. A selection that would remove packages, or cannot be installed on its own, is refused.
3. Confirm. Running guests keep running, but Proxmox services restart briefly. Turn on maintenance mode first if guests are critical.
4. The dialog shows the live apt output until the run finishes with Updates installed. or an error. The upgrade runs detached on the node, so you can close the dialog and reopen it later to follow it.

Reboot required

If a new kernel or core library was installed, the dialog shows Reboot required with a Reboot node button. Nothing is rebooted automatically; migrate or stop critical guests first.

After the run, the panel rescans the node facts so the update count and kernel on the node page are current.

Package source errors

If some package sources cannot be read, the dialog shows Some package sources could not be read with the raw apt error and a hint:

Problem	Hint
Enterprise repository returns 401	The Proxmox enterprise repository refused access (no subscription). Disable it or add the no-subscription repository on the node, then check again.
DNS failure	The node could not resolve the repository hosts. Check its DNS settings.
apt / dpkg locked	Another apt or dpkg process is running on the node. Try again when it has finished.
Interrupted install	Run dpkg --configure -a in the node console.
Timeout	The package repositories did not answer in time. Try again later.

An upgrade is refused while another one is running or while dpkg is locked.

Permissions and audit

Installing updates requires the node management permission. The start and the result of every run are recorded in the audit log (node.updates_start, node.updates_finish). On the node, the apt log is written to /var/log/nexovirt/apt-upgrade.log.