main
290
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
e729b935a4 |
Merge pull request 'feat(apt): read the release each source names, move a file to the host's (NetOrk/netork#2614)' (#127) from feature/apt-source-release into main
driver / lint (push) Successful in 15s
driver / test (3.13) (push) Successful in 1m12s
driver / build (push) Successful in 28s
driver / security (push) Successful in 58s
driver / publish (push) Skipped
driver / types (push) Successful in 1m3s
driver / lowest (push) Successful in 37s
driver / standard (push) Successful in 18s
driver / test (3.12) (push) Successful in 1m21s
CI / driver (push) Successful in 2m28s
|
||
|
|
f654076560 |
feat(apt): read the release each source names, move a file to the host's (NetOrk/netork#2614)
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m6s
CI / driver (pull_request) Successful in 2m28s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 55s
driver / test (3.13) (pull_request) Successful in 1m7s
driver / test (3.12) (pull_request) Successful in 1m16s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 12s
A release upgrade leaves third-party apt sources on the old release, where they still answer and their packages stop getting updates once the vendor stops building for it: z2m-house, Ubuntu 24.04, kept Docker's source on focal and never saw a Docker newer than 28.1.1. AptReleaseMixin.get_apt_source_releases() reports the host's /etc/os-release and every enabled source apt reads, one-line and deb822, with its file, line, types, URI, suites and components. set_apt_source_release(path, release, codename) moves every suite of release in one of apt's source files to codename, once each new suite's InRelease or Release is fetched with apt-helper through apt's own proxy; where the vendor has none, nothing is written. AptProxyMixin brings it, so every apt driver has it. |
||
|
|
2dea517e89 |
Merge pull request 'feat(firmware): install the offered firmware through FirmwareUpgradeMixin (NetOrk/netork#2615)' (#126) from feature/openwrt-sysupgrade-2615 into main
driver / lint (push) Successful in 12s
driver / test (3.13) (push) Successful in 1m3s
driver / lowest (push) Successful in 39s
driver / build (push) Successful in 26s
driver / security (push) Successful in 54s
driver / publish (push) Successful in 28s
driver / types (push) Successful in 53s
driver / test (3.12) (push) Successful in 1m5s
driver / standard (push) Successful in 16s
CI / driver (push) Successful in 2m57s
|
||
|
|
1a7885d22e |
refactor(firmware): FirmwareOfferDict lives with its contract
driver / build (pull_request) Successful in 24s
driver / security (pull_request) Successful in 53s
CI / driver (pull_request) Successful in 2m9s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 50s
driver / test (3.13) (pull_request) Successful in 59s
driver / test (3.12) (pull_request) Successful in 1m6s
driver / lowest (pull_request) Successful in 35s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
models.py is over the file limit and may not grow; the offer's two new fields moved it past its recorded length. It is still importable from napalm_device_types.models. |
||
|
|
71588613fb |
chore(release): 4.41.0
driver / build (pull_request) Successful in 25s
driver / security (pull_request) Successful in 52s
CI / driver (pull_request) Failing after 2m10s
driver / standard (pull_request) Failing after 15s
driver / types (pull_request) Successful in 53s
driver / test (3.13) (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
|
||
|
|
93ba335798 |
feat(firmware): install the offered firmware through FirmwareUpgradeMixin (NetOrk/netork#2615)
start_firmware_upgrade(version) starts an upgrade the device runs by itself and restarts at the end of; get_update_progress follows it. The offer says whether the driver can install it now (installable) and names a later release line it never crosses to (latest_major_version). |
||
|
|
eb1964c4b3 |
Merge pull request 'chore(release): 4.40.0' (#125) from chore/release-4.40.0 into main
driver / lint (push) Successful in 12s
driver / test (3.13) (push) Successful in 1m1s
driver / build (push) Successful in 33s
driver / security (push) Successful in 57s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 57s
driver / lowest (push) Successful in 36s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m14s
CI / driver (push) Successful in 3m10s
|
||
|
|
3622d0f825 |
chore(release): 4.40.0
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 57s
CI / driver (pull_request) Successful in 2m42s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 58s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / lowest (pull_request) Successful in 39s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
|
||
|
|
caf7ef4cc8 |
Merge pull request 'feat(fixes): ZabbixAgentMixin, a native Zabbix agent for a host without a container engine (NetOrk/netork#2571)' (#124) from feat/zabbix-agent-native into main
driver / lint (push) Successful in 14s
driver / lowest (push) Successful in 38s
driver / test (3.13) (push) Successful in 1m9s
driver / build (push) Successful in 29s
driver / security (push) Successful in 1m2s
driver / publish (push) Skipped
driver / types (push) Successful in 55s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m14s
CI / driver (push) Successful in 2m43s
|
||
|
|
3422b7d030 |
Merge remote-tracking branch 'origin/main' into feat/zabbix-agent-native
driver / build (pull_request) Successful in 33s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Successful in 2m38s
driver / standard (pull_request) Successful in 14s
driver / types (pull_request) Successful in 55s
driver / test (3.12) (pull_request) Successful in 1m10s
driver / test (3.13) (pull_request) Successful in 59s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 12s
# Conflicts: # CHANGELOG.md |
||
|
|
f1940aa918 |
Merge pull request 'feat(container-engine): reach rootful Podman like Docker (NetOrk/netork#818)' (#123) from feature/podman-engine-netork-818 into main
driver / lint (push) Successful in 12s
driver / test (3.13) (push) Successful in 58s
driver / build (push) Successful in 27s
driver / security (push) Successful in 55s
driver / publish (push) Skipped
driver / types (push) Successful in 49s
driver / lowest (push) Successful in 35s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m8s
CI / driver (push) Successful in 2m18s
|
||
|
|
5217c6e333 |
feat(fixes): ZabbixAgentMixin, a native Zabbix agent for a host without a container engine (NetOrk/netork#2571)
driver / build (pull_request) Successful in 24s
driver / security (pull_request) Successful in 55s
CI / driver (pull_request) Successful in 2m20s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 49s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / lowest (pull_request) Successful in 34s
driver / test (3.12) (pull_request) Successful in 1m11s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
configure_zabbix_agent(settings) loads the package index where the driver can, installs ZABBIX_AGENT_PACKAGE from the host's own packages and, where those have none and settings["release"] names the server's release line, from Zabbix's repository (the driver's _add_zabbix_repository); then the driver writes the configuration and opens the firewall, and the service is enabled and restarted. Settings that do not hold raise ValueError before anything changes. zabbix_agent.py holds what is the same on every host, without I/O: the settings check, the agent's configuration with Server, ServerActive, ListenPort and Hostname set and the rest kept, and the root command that adds Zabbix's repository for Debian, Ubuntu, Raspberry Pi OS and the RHEL family, in the layout before and since 7.2. LldpAgentMixin and ZabbixAgentMixin share the start step (enable_and_restart). |
||
|
|
7051199589 |
feat(container-engine): reach rootful Podman like Docker (NetOrk/netork#818)
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Successful in 2m27s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 55s
driver / test (3.13) (pull_request) Successful in 1m5s
driver / test (3.12) (pull_request) Successful in 1m13s
driver / lowest (pull_request) Successful in 37s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
container_engines() lists Podman with the API podman-libpod, and
open_container_engine("podman") reaches it with podman system dial-stdio
(Podman 4.0 and later). It is the host's rootful Podman: the engine of the
system's containers and of Quadlet's units, whose socket is root's. So the
connection runs every call as root (ContainerEngineConnection.privileged).
An engine is listed only when its CLI names itself on --version:
podman-docker's docker is podman, and listing it as Docker would read the
login user's rootless Podman a second time.
|
||
|
|
7c0e4fffc5 |
Merge pull request 'feat(apt): send https sources through the cache in the form it stores (netork#2555)' (#122) from fix/apt-https-cache into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m14s
driver / lowest (push) Successful in 37s
driver / build (push) Successful in 29s
driver / security (push) Successful in 1m3s
driver / publish (push) Skipped
driver / types (push) Successful in 58s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m21s
CI / driver (push) Successful in 2m33s
|
||
|
|
cb0f1cc05c |
feat(apt): send https sources through the cache in the form it stores (NetOrk/netork#2555)
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m9s
CI / driver (pull_request) Successful in 2m29s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 58s
driver / test (3.13) (pull_request) Successful in 1m1s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 35s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
apt-cacher-ng tunnels a source fetched over https and stores nothing of it. It fetches http://HTTPS///<host>/<path> over https itself, with the certificate verified, and stores it, where port 443 is allowed (AllowUserPorts=80 443). - apt_sources: cacheable_https_hosts(report), and the root commands that rewrite the https sources of .list and deb822 .sources files to that form and back. A host apt has credentials for in auth.conf stays on https; the rewrite names it in the proxy file as Package-Proxy::Not-Cached, which the report reads. - configure_package_proxy(url): a step "cache" before "https". It rewrites the sources, fetches one of them through url, and turns them all back to https where url cannot. The "fetch" step proves the proxy with a plain http source. - configure_package_proxy(""): the sources go back to https before the proxy file goes; without the cache apt would look for a host called HTTPS. |
||
|
|
b4929990f1 |
Merge pull request 'chore(release): 4.39.0' (#121) from chore/release-4.39.0 into main
driver / lint (push) Successful in 13s
driver / lowest (push) Successful in 36s
driver / test (3.13) (push) Successful in 1m2s
driver / build (push) Successful in 26s
driver / security (push) Successful in 1m20s
driver / publish (push) Successful in 29s
driver / types (push) Successful in 54s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 3m32s
|
||
|
|
3db6c6385c |
Merge pull request 'feat(updates): PackageIndexMissing, for a host without a package index' (#120) from feat/package-index-missing into main
driver / lint (push) Successful in 12s
driver / test (3.13) (push) Successful in 1m1s
driver / lowest (push) Successful in 34s
driver / build (push) Successful in 28s
driver / security (push) Successful in 1m0s
driver / publish (push) Skipped
driver / types (push) Successful in 53s
driver / test (3.12) (push) Successful in 1m7s
driver / standard (push) Successful in 14s
CI / driver (push) Successful in 2m15s
|
||
|
|
c5154d954b |
chore(release): 4.39.0
driver / build (pull_request) Successful in 24s
driver / security (pull_request) Successful in 50s
CI / driver (pull_request) Successful in 2m19s
driver / standard (pull_request) Successful in 14s
driver / types (pull_request) Successful in 49s
driver / test (3.12) (pull_request) Successful in 1m3s
driver / lowest (pull_request) Successful in 33s
driver / test (3.13) (pull_request) Successful in 59s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 12s
|
||
|
|
211d0c02eb |
feat(updates): PackageIndexMissing, for a host without a package index
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 52s
CI / driver (pull_request) Successful in 2m12s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 58s
driver / test (3.13) (pull_request) Successful in 1m2s
driver / test (3.12) (pull_request) Successful in 1m10s
driver / lowest (pull_request) Successful in 36s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
OpenWrt keeps its package index in RAM and loses it on every reboot. get_available_updates() raises then, rightly, but only as a bare RuntimeError, so a caller cannot tell it from a read that failed and reports a communication error for a state a refresh cures. PackageIndexMissing (a RuntimeError, so existing callers still catch it) names that case; refresh_available_updates() is the way out. Refs NetOrk/netork#2527 |
||
|
|
74d2f42b0e |
Merge pull request 'feat(system-identity): read the system firmware with the identity' (#119) from feat/system-firmware into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m10s
driver / lowest (push) Successful in 43s
driver / build (push) Successful in 31s
driver / security (push) Successful in 1m6s
driver / publish (push) Skipped
driver / types (push) Successful in 56s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m13s
CI / driver (push) Successful in 2m52s
|
||
|
|
c25f39768f |
refactor(system-identity): keep SystemIdentityDict with its mixin
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m4s
CI / driver (pull_request) Successful in 2m51s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 57s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
models.py is over its line limit and may not grow; the dict has no other user than system_identity.py, as clusters.py and apt_proxy.py keep theirs. NetOrk/netork#2518 |
||
|
|
9ecc6823c8 |
feat(system-identity): read the system firmware with the identity
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 58s
CI / driver (pull_request) Failing after 2m17s
driver / standard (pull_request) Failing after 15s
driver / types (pull_request) Successful in 52s
driver / test (3.13) (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m11s
driver / lowest (pull_request) Successful in 39s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
get_system_identity() also reads bios_vendor, bios_version and bios_date from /sys/class/dmi/id, in the same round trip as the SMBIOS identity. The date is given as ISO 8601; anything that is no MM/DD/YYYY reads as empty. Only the vendors' text defaults are placeholders for the firmware: a version of "1" is a version, unlike a serial of one repeated character. Output of the three identity fields alone still parses, with the firmware empty. NetOrk/netork#2518 |
||
|
|
2080ccbfd7 |
Merge pull request 'chore(release): 4.38.0' (#118) from chore/release-4.38.0 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m1s
driver / lowest (push) Successful in 37s
driver / build (push) Successful in 28s
driver / security (push) Successful in 53s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 56s
driver / test (3.12) (push) Successful in 1m10s
driver / standard (push) Successful in 16s
CI / driver (push) Successful in 3m1s
|
||
|
|
ce1fe18405 |
chore(release): 4.38.0
driver / build (pull_request) Successful in 31s
driver / security (pull_request) Successful in 1m11s
CI / driver (pull_request) Successful in 2m59s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m2s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / test (3.13) (pull_request) Successful in 1m9s
driver / lowest (pull_request) Successful in 46s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
|
||
|
|
e43926f1d5 |
Merge pull request 'feat(config-revisions): declare a device's own configuration history' (#117) from feat/config-revisions into main
driver / lint (push) Successful in 15s
driver / test (3.13) (push) Successful in 1m6s
driver / build (push) Successful in 29s
driver / security (push) Successful in 1m5s
driver / publish (push) Skipped
driver / types (push) Successful in 1m11s
driver / lowest (push) Successful in 37s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m27s
CI / driver (push) Successful in 2m58s
|
||
|
|
43e0210ff6 |
feat(config-revisions): declare a device's own configuration history
driver / build (pull_request) Successful in 34s
driver / security (pull_request) Successful in 3m34s
CI / driver (pull_request) Successful in 5m2s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m3s
driver / test (3.13) (pull_request) Successful in 1m12s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / lowest (pull_request) Successful in 47s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
Some devices keep a copy of their configuration for every save and can go back to one. An application restores a configuration there by reverting to the revision that holds it; on OPNsense that is the only way, since its API takes no uploaded config.xml (NetOrk/netork#2511). ConfigRevisionsMixin declares get_config_revisions() (newest first, as ConfigRevisionDict) and get_config_revision(revision_id). revert_config_revision(revision_id) is a template over the driver's _revert_to_config_revision step: it refuses an id that is not in the history (UnknownConfigRevision), reads the revision before the revert can rotate it out, and afterwards checks that the newest revision holds its configuration (ConfigRevertFailed otherwise), since a device may report a revert it did not make. config_revision_content(text) is the hook where a driver leaves out what its device stamps into every save, so revisions with the same configuration compare equal. Refs NetOrk/netork#2511 |
||
|
|
241acef6c1 |
Merge pull request 'feat(accounts): add_service_account takes the keys the new one replaces' (#115) from fix/service-account-replaces into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 59s
driver / lowest (push) Successful in 35s
driver / build (push) Successful in 28s
driver / security (push) Successful in 57s
driver / publish (push) Skipped
driver / types (push) Successful in 55s
driver / test (3.12) (push) Successful in 1m10s
driver / standard (push) Successful in 16s
CI / driver (push) Successful in 2m35s
|
||
|
|
4c0ba5b2c0 |
refactor(accounts): the account step of add_service_account in a helper
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 54s
CI / driver (pull_request) Successful in 2m32s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 52s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 39s
driver / test (3.13) (pull_request) Successful in 1m7s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
replaces= made add_service_account 55 lines long, over the quality ratchet's 50. Its account step -- none to take when the driver logs in as the account already, else the create or reopen -- moves to _accounts_service_account_step. Behaviour is unchanged; the tests of add_service_account cover both branches. |
||
|
|
e9da399568 | Merge remote-tracking branch 'origin/main' into fix/service-account-replaces | ||
|
|
8673d1eda1 |
Merge pull request 'feat(log-forwarding): each forwarding rule names its template' (#116) from feat/forward-rule-template into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m13s
driver / lowest (push) Successful in 43s
driver / build (push) Successful in 31s
driver / security (push) Successful in 1m3s
driver / publish (push) Skipped
driver / types (push) Successful in 1m8s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m22s
CI / driver (push) Successful in 2m33s
|
||
|
|
46d7125aa6 |
refactor(log-forwarding): a legacy rule's template is read on its own
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m4s
CI / driver (pull_request) Successful in 2m57s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 58s
driver / test (3.12) (pull_request) Successful in 1m21s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
The quality ratchet holds _Reader.legacy at complexity 10. |
||
|
|
8e43fe2ed9 |
feat(log-forwarding): each forwarding rule names its template
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Failing after 2m38s
driver / standard (pull_request) Failing after 17s
driver / types (pull_request) Successful in 1m9s
driver / test (3.13) (pull_request) Successful in 1m15s
driver / test (3.12) (pull_request) Successful in 1m30s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
A rule's template decides the timestamp it sends: rsyslog's default, RFC 3164, carries the host's local time without a zone, which a collector such as Graylog files shifted by the host's UTC offset (NetOrk/netork#493). The rule now says which template it uses: its own (`@host;Name`, `action(... template="...")`), else the default set before it (`$ActionForwardDefaultTemplate`, or `module(load="builtin:omfwd" template="...")` for omfwd actions), else None. |
||
|
|
679584766f |
feat(accounts): add_service_account takes the keys the new one replaces
driver / build (pull_request) Successful in 38s
driver / security (pull_request) Successful in 1m16s
CI / driver (pull_request) Failing after 2m45s
driver / standard (pull_request) Failing after 18s
driver / types (pull_request) Successful in 1m1s
driver / test (3.13) (pull_request) Successful in 1m11s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / lowest (pull_request) Successful in 46s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
netOrk moves a host from its installation-wide key to its site's (NetOrk/netork#2462): the old key has to go from its own account, which remove_local_account_keys refuses (the login's own account, a system account). With replaces, the old keys go once the new key is in -- never the new key itself, and not while it could not be added. |
||
|
|
1b04818982 |
Merge pull request 'fix(dhcp): a refused subnet no longer stops the rest of the set' (#114) from fix/dhcp-subnet-apply-tolerance into main
driver / lint (push) Successful in 13s
driver / lowest (push) Successful in 43s
driver / test (3.13) (push) Successful in 1m6s
driver / build (push) Successful in 29s
driver / security (push) Successful in 1m5s
driver / publish (push) Skipped
driver / types (push) Successful in 56s
driver / test (3.12) (push) Successful in 1m12s
driver / standard (push) Successful in 14s
CI / driver (push) Successful in 2m44s
|
||
|
|
65991d0930 |
fix(dhcp): a refused subnet no longer stops the rest of the set
driver / build (pull_request) Successful in 35s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Successful in 3m15s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m19s
driver / test (3.12) (pull_request) Successful in 1m32s
driver / test (3.13) (pull_request) Successful in 1m16s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
apply_dhcp_subnetset called apply_dhcp_subnet for each add and update
and committed only at the end, so one refused write raised before the
commit: the subnets written ahead of it stayed saved but inactive, and
as the device reports them as configured, no later diff committed them.
It now behaves like apply_dhcp_reservationset since 4.35.1: a refused
subnet gets a [failed] line, the others are written, any non-empty diff
is committed, then DhcpApplyError is raised. DhcpApplyError takes an
optional kind ("reservation" by default) for its message.
Closes #113
|
||
|
|
9dfb5596bc |
Merge pull request 'fix(dhcp): release an address before another reservation takes it' (#112) from fix/dhcp-reservation-apply-order into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m9s
driver / lowest (push) Successful in 40s
driver / build (push) Successful in 30s
driver / security (push) Successful in 1m9s
driver / publish (push) Skipped
driver / types (push) Successful in 1m1s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m17s
CI / driver (push) Successful in 2m59s
|
||
|
|
b4cdcfd347 |
fix(dhcp): release an address before another reservation takes it
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m10s
CI / driver (pull_request) Successful in 3m6s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m25s
driver / test (3.13) (pull_request) Successful in 1m13s
driver / lowest (pull_request) Successful in 45s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
apply_dhcp_reservationset wrote adds first, then updates in the order of the desired set. Kea keeps addresses unique at each write, so when an address moved from one reservation to another, the reservation taking it was refused as a duplicate whenever it came first. The changes are now ordered (_dhcp_order): an update that moves a reservation off its address goes before the change that takes that address, along a chain from its free end, and adds come after every update. A swap or rotation of addresses has no such order; its changes are still tried, so a server that checks only at the commit takes them, and a refused one's [failed] line says it was a swap and with which reservations. Nothing is moved to a temporary address: the contract knows no free one, and a failed second write would leave it there. The diff is computed against one read of the reservations, shared with diff_dhcp_reservations. Refused rows still do not stop the others, the rest is committed and DhcpApplyError follows, as since 4.35.1. Closes #106 |
||
|
|
5258a43dc9 |
Merge pull request 'feat(updates): the CVEs a host's installed advisories close (4.37.0)' (#111) from feature/installed-advisories into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m16s
driver / lowest (push) Successful in 39s
driver / build (push) Successful in 28s
driver / security (push) Successful in 1m6s
driver / publish (push) Successful in 28s
driver / types (push) Successful in 59s
driver / test (3.12) (push) Successful in 1m12s
driver / standard (push) Successful in 15s
CI / driver (push) Successful in 6m6s
|
||
|
|
f3cb3601a8 |
feat(updates): the CVEs a host's installed advisories close (4.37.0)
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m0s
CI / driver (pull_request) Successful in 2m29s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m2s
driver / test (3.13) (pull_request) Successful in 1m11s
driver / test (3.12) (pull_request) Successful in 1m24s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
UpdateMixin declares get_installed_advisory_cves(): per package, the CVEs the installed security advisories close -- the distribution's word that a backport is in although the upstream version did not move. The command (DNF_INSTALLED_CVES_COMMAND, dnf 4, from the cache) and its parser (parse_dnf_installed_cves) live here for every dnf driver, as the security read's do. netOrk reads it where its knowledge base holds no records of the host's release (NetOrk/netork#2394). |
||
|
|
a8fedf299a |
Merge pull request 'fix(host-status): kernel releases compare the way rpm does (4.36.2)' (#110) from fix/rpm-kernel-version-order into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m13s
driver / lowest (push) Successful in 46s
driver / build (push) Successful in 40s
driver / security (push) Successful in 1m16s
driver / publish (push) Successful in 30s
driver / types (push) Successful in 1m4s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m20s
CI / driver (push) Successful in 3m36s
|
||
|
|
c736fb30d0 |
refactor(host-status): compare one version segment in a helper of its own
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 57s
CI / driver (pull_request) Successful in 2m30s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 56s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
The quality ratchet refused _version_cmp at complexity 12. Comparing one segment moves to _segment_cmp, which also takes 01 and 1 as equal, as rpm does. |
||
|
|
cf555d006d |
fix(host-status): kernel releases compare the way rpm does (4.36.2)
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m3s
CI / driver (pull_request) Failing after 2m32s
driver / standard (pull_request) Failing after 15s
driver / types (pull_request) Successful in 1m5s
driver / test (3.13) (pull_request) Successful in 1m14s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / lowest (pull_request) Successful in 42s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
_version_key compared the text between numbers as plain strings, so '.el' outranked '.' and 6.12.0-208.112.5.el9uek counted as newer than the running 6.12.0-208.112.5.1.el9uek: an Oracle Linux host asked to reboot into an older kernel, and a reboot never cleared it. The releases now compare like rpmvercmp: separators only separate, a number is newer than letters in its place, and '~' comes before anything. Checked against rpm.labelCompare on Oracle Linux 9. Closes #109 |
||
|
|
4e79cd1fc8 |
Merge pull request 'fix(host-status): an Oracle Linux host's UEK kernels are not an interrupted dnf (4.36.1)' (#108) from fix/dnf-installonly-defaults into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m12s
driver / lowest (push) Successful in 41s
driver / build (push) Successful in 30s
driver / security (push) Successful in 1m3s
driver / publish (push) Successful in 30s
driver / types (push) Successful in 1m0s
driver / test (3.12) (push) Successful in 1m17s
driver / standard (push) Successful in 16s
CI / driver (push) Successful in 3m21s
|
||
|
|
304f404567 |
fix(host-status): an Oracle Linux host's UEK kernels are not an interrupted dnf (4.36.1)
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 56s
CI / driver (pull_request) Successful in 2m26s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 59s
driver / test (3.13) (pull_request) Successful in 1m12s
driver / test (3.12) (pull_request) Successful in 1m17s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
The installonly packages were dnf's upstream defaults plus dnf.conf's. Oracle builds kernel-uek and its parts into libdnf's defaults, and the UEK packages provide nothing of upstream's list, so every host with more than one UEK kernel was reported as left halfway. The defaults are now also asked of the host's libdnf through its Python binding; upstream's list stays the floor for dnf 5 and yum. Closes #107 |
||
|
|
aaa9f0504a |
Merge pull request 'feat(time-sync): DHCP-provided NTP servers count and are read apart (4.36.0)' (#105) from feat/time-sync-dhcp-ntp-2380 into main
driver / lint (push) Successful in 15s
driver / lowest (push) Successful in 42s
driver / test (3.13) (push) Successful in 1m11s
driver / build (push) Successful in 31s
driver / security (push) Successful in 1m2s
driver / publish (push) Successful in 31s
driver / types (push) Successful in 59s
driver / standard (push) Successful in 18s
driver / test (3.12) (push) Successful in 1m16s
CI / driver (push) Successful in 3m17s
|
||
|
|
bc47220318 |
Merge remote-tracking branch 'origin/main' into feat/time-sync-dhcp-ntp-2380
driver / build (pull_request) Successful in 48s
driver / security (pull_request) Successful in 1m26s
CI / driver (pull_request) Successful in 3m17s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m34s
driver / test (3.13) (pull_request) Successful in 1m32s
driver / test (3.12) (pull_request) Successful in 1m52s
driver / lowest (pull_request) Successful in 1m3s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
# Conflicts: # CHANGELOG.md # pyproject.toml |
||
|
|
08a62838f7 |
Merge pull request 'fix(dhcp): one refused reservation no longer stops the apply' (#104) from fix/dhcp-reservations-partial-apply into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m9s
driver / lowest (push) Successful in 41s
driver / build (push) Successful in 33s
driver / security (push) Successful in 1m7s
driver / publish (push) Successful in 32s
driver / types (push) Successful in 1m4s
driver / test (3.12) (push) Successful in 1m18s
driver / standard (push) Successful in 18s
CI / driver (push) Successful in 3m29s
|
||
|
|
ac38c68feb |
feat(time-sync): DHCP-provided NTP servers count and are read apart
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 3m22s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m16s
driver / test (3.13) (pull_request) Successful in 1m29s
driver / test (3.12) (pull_request) Successful in 1m33s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 31s
A device that gets the site's time giver through DHCP option 42 is aligned (NetOrk/netork#2380): most clients already learn it that way. 4.35.0 switched that off on every write -- chrony's DHCP sourcedir was commented out, and systemd-timesyncd's link servers failed the verify step -- and folded DHCP's servers into ntp_servers, so an application could not tell configured from DHCP-provided servers. TimeSyncDict gains dhcp_ntp_servers (not required): the servers the device got by DHCP and uses, in its order; [] for none, absent or None where the driver cannot tell. ntp_servers keeps only the configured ones. PosixTimeSyncMixin reads chrony's sources from the DHCP client's sourcedir (CHRONY_DHCP_DIRS, /run/chrony-dhcp by default) as chronyd reads them, and systemd-timesyncd's LinkNTPServers; ntpd and OpenNTPD keep DHCP's servers in a configuration of their own, so there it is unknown. A chrony write now comments out only server, pool and peer lines and leaves every sourcedir and the DHCP client's files alone. A DHCP sourcedir that 4.35.0 commented out behind the mark is given back on the next write, with a restart, so hosts it aligned hear DHCP again. Version 4.36.0. |
||
|
|
8516f2a1ee |
refactor(dhcp): one reservation's write in a helper of its own
driver / build (pull_request) Successful in 37s
driver / security (pull_request) Successful in 1m9s
CI / driver (pull_request) Successful in 3m0s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / test (3.13) (pull_request) Successful in 1m10s
driver / lowest (pull_request) Successful in 42s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
apply_dhcp_reservationset grew to 59 lines with the per-write handling; the quality ratchet allows no new function that long. Refs NetOrk/netork#2381 |
||
|
|
c74173523a |
fix(dhcp): one refused reservation no longer stops the apply
driver / build (pull_request) Successful in 38s
driver / security (pull_request) Successful in 1m11s
CI / driver (pull_request) Failing after 2m57s
driver / standard (pull_request) Failing after 22s
driver / types (pull_request) Successful in 1m22s
driver / test (3.12) (pull_request) Successful in 1m28s
driver / test (3.13) (pull_request) Successful in 1m26s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 18s
apply_dhcp_reservationset wrote the diff one reservation at a time and committed only after the last. A write the device refused -- on OPNsense, an address in a subnet Kea does not manage -- ended the run before the commit: every later reservation went unwritten, and the earlier ones stayed saved but inactive. The next diff read those back as configured, reported no changes and never committed them. A refused change now gets a "[failed] <mac> -> <ip>: <reason>" line and the others are still written. Any non-empty diff commits, also one whose every write was refused, so writes an interrupted earlier run saved take effect. DhcpApplyError (a RuntimeError, exported) is raised after the commit with how many of how many changes were refused. Refs NetOrk/netork#2381 |