Files
napalm-openmediavault/CHANGELOG.md
T
Christian Manivong e09af917c8
driver / standard (pull_request) Successful in 16s
driver / lint (pull_request) Successful in 13s
driver / types (pull_request) Successful in 1m2s
driver / test (3.12) (pull_request) Successful in 1m1s
driver / test (3.13) (pull_request) Successful in 58s
driver / lowest (pull_request) Successful in 28s
driver / build (pull_request) Successful in 27s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 2m35s
driver / publish (pull_request) Skipped
fix(disks): read a SAS disk's temperature
A SCSI/SAS disk prints its temperature as "Current Drive Temperature:
28 C", which matched none of the ATA and NVMe patterns, so every SAS
disk read -1. Found in the smartctl output recorded from a Proxmox host.
A QEMU disk without a sensor prints 0 C there and keeps reading -1.
2026-11-01 22:15:35 +01:00

3.6 KiB
Raw Blame History

Changelog

All notable changes to this driver. The format follows Keep a Changelog, versions follow Semantic Versioning.

[Unreleased]

Added

  • netOrk's own account with a fixed uid is not made on OMV yet (NetOrk/netork#1817): _account_create_with_uid raises NotImplementedError, as the keys go through UserMgmt, which knows only the users it made.
  • Personal accounts the way OMV's web UI makes them (NetOrk/netork#1793), on top of napalm-linux's get_local_accounts(), add_local_account() and lock_local_account(). 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/<user>. So a new account is made by UserMgmt.setUser in _ssh, an account made outside OMV joins _ssh when it is opened, and keys are added and removed through setUser. Each call applies the modules it made dirty (postfix, ssh) and nothing else: changes left pending in the web UI stay pending. setUser takes a plain password, which netOrk does not have, so the hash is set with usermod -p. Like the web UI, setUser gives the account OMV's primary group users. Checked on a fresh OMV 8 (Debian 13) with the real driver over SSH. Requires the napalm-device-types and napalm-linux releases with personal accounts.
  • set_hostname() the way OMV's web UI renames the NAS: Network.setGeneralSettings (an FQDN sets the domain too, a bare name keeps it), then Config.applyChanges for the modules the rename made dirty plus the hostname modules already dirty. Changes left pending in the web UI are not deployed with it. Replaces the inherited napalm-linux rename (NAPALM/napalm-linux#45), whose /etc/hostname and /etc/hosts OMV would regenerate on its next apply.

Changed

  • Python 3.12 is the floor (requires-python = ">=3.12"): netOrk runs every driver on 3.12, so 3.10 and 3.11 are no longer tested (NAPALM/driver-standard#6).

Fixed

  • get_disks() reports each disk's SMART verdict: healthy when smartctl's overall self-assessment passed (SCSI/SAS: health status OK), failed when it failed or a SCSI disk predicts a failure, unknown only when the disk gives none. The driver asked smartctl without -H, which never prints the verdict: a disk read unknown, and an ATA disk with an attribute table read failed from that table's WHEN_FAILED column, whatever its state.
  • get_disks() puts a disk in the md array only when the disk itself or one of its partitions is a member: sda no longer joins the array of sdaa1, nor nvme0n1 that of nvme0n11. /proc/mdstat is read once per call instead of once per disk.
  • get_disks() reports a SCSI/SAS disk's temperature (Current Drive Temperature); it read -1 for every SAS disk. A disk that prints 0 C there, as QEMU's virtual disks do, still reads -1.

[0.3.0] - 2026-10-23

The first release on PyPI.

Changed

  • The driver follows the NAPALM driver standard (https://git.netork.io/NAPALM/driver-standard): CI on Gitea runs ruff, mypy, the tests on Python 3.10–3.13 and at the lowest declared versions, bandit, pip-audit and a build check, and a release tag publishes to PyPI. The package now ships py.typed, a README and a LICENSE file. It needs napalm-device-types 4.22.0 and napalm-linux 0.15.0. Python 3.9 is no longer supported; napalm-device-types never ran on it.
  • Failures the driver deliberately ignores (the OpenMediaVault version, smartctl for one disk, /proc/mdstat, mdadm --detail, a shared folder lookup) are now logged at debug level.