What a node runs

Each node reports what it runs every two minutes. The release view puts that side by side and flags differences. It is also the starting point of every upgrade.

stratumctl admin upgrade status

NODE    OS                     ROLLBACK  CONTROL PLANE          HOST BINARIES  IMAGES      REPORTED
node-1  0.2.0 (dbcb96dfa0ab)   -         0.2.0 (schema 0302)    4298b2fe       18 current  21s ago

Release:     the same on all 1 node(s)

Column	Means
OS	The booted OS deployment: release and digest.
ROLLBACK	The previous OS deployment kept for a rollback.
CONTROL PLANE	The control plane’s build and the newest database migration it carries.
HOST BINARIES	The build of the host tools; stale when it is not the running release’s.
IMAGES	Each platform container against the image its release pins: current or differs.
REPORTED	Age of the node’s last report. Older than ten minutes counts as drift.

Below the table:

• Skew: values that differ between nodes (OS, kernel, control plane, schema, host binaries, package versions, images).
• Drift: a node not running its own release: an unpinned image, stale host binaries, a staged OS deployment waiting for a reboot, or a missing report.

-o json adds the host packages (Open vSwitch, OVN, libvirt, QEMU, podman, systemd), the system extensions, and the releases stored on the node with their sizes.

Console: Admin › Substrate › Upgrades, Nodes.

On the node itself

Without the API, the node’s own report:

sudo stratum-host-helper --release-report

It prints the report and changes nothing.