feat: say whether a host is still in its first boot
CI / test (3.10) (push) Successful in 29s
CI / test (3.11) (push) Successful in 30s
CI / test (3.12) (push) Successful in 29s
CI / test (3.10) (pull_request) Successful in 29s
CI / test (3.11) (pull_request) Successful in 46s
CI / test (3.12) (pull_request) Successful in 42s
CI / test (3.10) (push) Successful in 29s
CI / test (3.11) (push) Successful in 30s
CI / test (3.12) (push) Successful in 29s
CI / test (3.10) (pull_request) Successful in 29s
CI / test (3.11) (pull_request) Successful in 46s
CI / test (3.12) (pull_request) Successful in 42s
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.
This commit is contained in:
@@ -32,5 +32,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
sysDescr; `get_snmp_config` reports a running agent's community and port.
|
||||
- `get_host_status` (napalm-device-types' `HostStatusMixin`): on FreeBSD,
|
||||
"reboot required" when the installed kernel differs from the running one.
|
||||
- `first_boot_pending()`: whether a FreeBSD host is still in its first boot
|
||||
(`/firstboot`), so netOrk can wait before setting up a new VM
|
||||
(NetOrk/netork#795).
|
||||
- Parsers tested on output recorded from FreeBSD 15.1 (hand-installed and
|
||||
cloud image) and OpenBSD 7.9 (NetOrk/netork#793).
|
||||
|
||||
Reference in New Issue
Block a user