get_time_sync = None and configure_time_sync = None, next to the other things QTS switches off. See NetOrk/netork#2370 (part of NetOrk/netork#2360).
napalm-linux now brings napalm-device-types' PosixTimeSyncMixin (4.35.0, NAPALM/napalm-linux#74) to every LinuxDriver. QTS has no systemd and no timedatectl, and its NTP client and zone are QTS settings. The inherited reading finds no client (daemon None, ntp_servers []), and every write fails its step. That would be a permanent difference netOrk reports but cannot fix. With these lines, a capability check (callable(getattr(driver, "get_time_sync", None))) answers no.
A read-only QTS variant was considered and left out. The zone is readable (getcfg System 'Time Zone', as scheduled jobs do), but the NTP keys in uLinux.conf have not been harvested from a box. A reading that reports the zone but no servers would show the same false difference. Follow-up: #21.
The floor rises to napalm-device-types>=4.35.0. napalm-linux stays at >=0.17.0: #74 is unreleased, its main still says 0.17.0, and CI installs it from git main. With napalm-linux 0.17.0 from PyPI the two lines do nothing.
Tests
test_time_sync_is_not_read_or_set_here failed first against napalm-linux main (both methods were callable on QnapQtsDriver). 117 tests pass (1 xfailed), and ruff, mypy, napalm-standard check and ratchet are clean.
## What
`get_time_sync = None` and `configure_time_sync = None`, next to the other things QTS switches off. See NetOrk/netork#2370 (part of NetOrk/netork#2360).
napalm-linux now brings napalm-device-types' `PosixTimeSyncMixin` (4.35.0, NAPALM/napalm-linux#74) to every `LinuxDriver`. QTS has no systemd and no `timedatectl`, and its NTP client and zone are QTS settings. The inherited reading finds no client (`daemon` None, `ntp_servers` []), and every write fails its step. That would be a permanent difference netOrk reports but cannot fix. With these lines, a capability check (`callable(getattr(driver, "get_time_sync", None))`) answers no.
A read-only QTS variant was considered and left out. The zone is readable (`getcfg System 'Time Zone'`, as scheduled jobs do), but the NTP keys in `uLinux.conf` have not been harvested from a box. A reading that reports the zone but no servers would show the same false difference. Follow-up: #21.
The floor rises to `napalm-device-types>=4.35.0`. `napalm-linux` stays at `>=0.17.0`: #74 is unreleased, its `main` still says 0.17.0, and CI installs it from git `main`. With napalm-linux 0.17.0 from PyPI the two lines do nothing.
## Tests
`test_time_sync_is_not_read_or_set_here` failed first against napalm-linux `main` (both methods were callable on `QnapQtsDriver`). 117 tests pass (1 xfailed), and ruff, mypy, `napalm-standard check` and `ratchet` are clean.
napalm-linux now brings napalm-device-types' PosixTimeSyncMixin (4.35.0). QTS has no systemd and no timedatectl, and its NTP client and time zone are QTS settings: the inherited reading finds no client there and every write fails its step, a difference netOrk could report on every poll but never fix (NetOrk/netork#2370). get_time_sync and configure_time_sync are None, so a capability check answers no, until a QTS variant is built against a real box. The floor rises to napalm-device-types 4.35.0.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
get_time_sync = Noneandconfigure_time_sync = None, next to the other things QTS switches off. See NetOrk/netork#2370 (part of NetOrk/netork#2360).napalm-linux now brings napalm-device-types'
PosixTimeSyncMixin(4.35.0, NAPALM/napalm-linux#74) to everyLinuxDriver. QTS has no systemd and notimedatectl, and its NTP client and zone are QTS settings. The inherited reading finds no client (daemonNone,ntp_servers[]), and every write fails its step. That would be a permanent difference netOrk reports but cannot fix. With these lines, a capability check (callable(getattr(driver, "get_time_sync", None))) answers no.A read-only QTS variant was considered and left out. The zone is readable (
getcfg System 'Time Zone', as scheduled jobs do), but the NTP keys inuLinux.confhave not been harvested from a box. A reading that reports the zone but no servers would show the same false difference. Follow-up: #21.The floor rises to
napalm-device-types>=4.35.0.napalm-linuxstays at>=0.17.0: #74 is unreleased, itsmainstill says 0.17.0, and CI installs it from gitmain. With napalm-linux 0.17.0 from PyPI the two lines do nothing.Tests
test_time_sync_is_not_read_or_set_herefailed first against napalm-linuxmain(both methods were callable onQnapQtsDriver). 117 tests pass (1 xfailed), and ruff, mypy,napalm-standard checkandratchetare clean.