driver / standard (pull_request) Failing after 14s
driver / lint (pull_request) Successful in 14s
driver / types (pull_request) Failing after 1m13s
driver / test (3.13) (pull_request) Failing after 1m6s
driver / test (3.12) (pull_request) Failing after 1m17s
driver / lowest (pull_request) Failing after 29s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Failing after 2m25s
driver / publish (pull_request) Skipped
napalm-linux adds and locks accounts with shadow-utils and keys in ~/.ssh. OMV's sshd lets in only root and _ssh, and OMV keeps a user's keys in its own database, deploying them to /var/lib/openmediavault/ssh/authorized_keys. So a new account is made by UserMgmt.setUser in _ssh, one made outside OMV joins _ssh when it is opened, and keys go through setUser. Each call applies the modules it made dirty (postfix, ssh) and leaves what was pending in the web UI pending. setUser takes a plain password, netOrk only the hash, so the hash is set with usermod -p. The lock stays napalm-linux's expiry. Checked on a fresh OMV 8 (Debian 13) with the real driver over SSH and sudo -S: a new account logs in with its key and uses sudo, is refused after locking with OMV's keys emptied, logs in again after reopening; an account made outside OMV is let in once it joined _ssh; a module left dirty before stays dirty.