napalm-bsd

2 Commits

Author	SHA1	Message	Date
Christian Manivong	32a63411d3	feat: say whether a host is still in its first boot CI / test (3.10) (push) Successful in 29s Details CI / test (3.11) (push) Successful in 30s Details CI / test (3.12) (push) Successful in 29s Details CI / test (3.10) (pull_request) Successful in 29s Details CI / test (3.11) (pull_request) Successful in 46s Details CI / test (3.12) (pull_request) Successful in 42s Details first_boot_pending() is true while /firstboot exists on FreeBSD. A FreeBSD cloud image upgrades its base system on its first boot, starts sshd only after that and restarts right away, and /etc/rc removes /firstboot just before that restart. netOrk waits for this before it sets up a new VM (NetOrk/netork#795). OpenBSD has no such marker to ask yet, so it returns False there.	2026-10-08 12:58:00 +02:00
Christian Manivong	25308bf747	fix: raise when an update reader cannot read, and report host status CI / test (3.10) (push) Successful in 26s Details CI / test (3.11) (push) Successful in 25s Details CI / test (3.12) (push) Successful in 26s Details CI / test (3.10) (pull_request) Successful in 25s Details CI / test (3.11) (pull_request) Successful in 24s Details CI / test (3.12) (pull_request) Successful in 26s Details netOrk reads an empty update list as "no updates" and closes every patch clock on the host. A refused sudo, a failing pkg, syspatch or freebsd-update, or a pkg database pkg cannot read used to come back as that empty list. Each of these now raises. Only pkg's "is not installed" still means no packages. BsdDriver takes on napalm-device-types' HostStatusMixin. On FreeBSD it reports a host whose installed kernel differs from the running one as needing a reboot (device-types 4.1). OpenBSD stays unknown. Closes #4	2026-10-08 12:08:44 +02:00