driver / lint (pull_request) Successful in 13s
driver / standard (pull_request) Successful in 14s
driver / types (pull_request) Successful in 54s
driver / test (3.13) (pull_request) Successful in 1m2s
driver / test (3.12) (pull_request) Successful in 1m5s
driver / lowest (pull_request) Successful in 31s
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 54s
CI / driver (pull_request) Successful in 2m10s
driver / publish (pull_request) Skipped
netOrk holds a host's restart after patching while a backup runs on it, and a guest's restart while its hypervisor is backing it up (NetOrk/netork#2318). It asks right before the restart, so both drivers answer get_running_backups() from napalm-device-types 4.34.0: - PVE: the node's active vzdump tasks, each with the guests it is taking now (its own guest, or for a job the guests locked for their backup), and a guest locked without a task on its own, since the task list can lag and a lock can outlive its task. - PBS: the running backup, sync, verify, gc, prune and tape tasks; a restore or housekeeping is no backup. A failed read raises, so netOrk reads it as "not checked", never as "none".