NAS-129206 / 26.04 / Remove syslog SNMP filter. (#17352)
The Debian version of the snmp daemon has been updated and patched to
fix the problem introduced with Linux 6.7
Confirmed via inspecting the Debian source for net-snmp and looking for
the characteristic syslog messages.
NAS-137956 / 26.04 / Add pyotp to test requirements.txt (#17351)
Halfmoon STIG CI tests are not running due to a missing requirement on
the test runner.
Adding `pyotp` to tests/requirements.txt restores STIG CI tests to
Goldeye level.
http://jenkins.eng.ixsystems.net:8080/job/tests/job/stig_tests/739/
Note: Does not fix tests, but recovers Goldeye functionality.
NAS-137540 / 25.10.0 / Secureboot attrs should only be validated at create time (by Qubad786) (#17347)
## Problem
* `enable_secure_boot` and `bootloader_ovmf` are **create-time
variables**, but their validation is currently part of the **common
validation logic**, which also runs during updates.
* As a result, VMs created **before this change** are incorrectly
validated during updates, leading to user-facing validation errors.
* Additionally, the transition to **Debian Trixie** has removed the
`OVMF_CODE.fd` file from the available choices. This causes problems
when users creates a VM without explicitly defining an OVMF value.
## Solution
* Move the validation for `enable_secure_boot` and `bootloader_ovmf` to
the **VM creation logic only**, preventing validation errors during
updates.
* Updated the right default value for bootloader_ovmf .
[3 lines not shown]
NAS-137540 / 26.04 / Secureboot attrs should only be validated at create time (#17340)
## Problem
* `enable_secure_boot` and `bootloader_ovmf` are **create-time
variables**, but their validation is currently part of the **common
validation logic**, which also runs during updates.
* As a result, VMs created **before this change** are incorrectly
validated during updates, leading to user-facing validation errors.
* Additionally, the transition to **Debian Trixie** has removed the
`OVMF_CODE.fd` file from the available choices. This causes problems
when users creates a VM without explicitly defining an OVMF value.
## Solution
* Move the validation for `enable_secure_boot` and `bootloader_ovmf` to
the **VM creation logic only**, preventing validation errors during
updates.
* Updated the right default value for bootloader_ovmf .
