mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-02 13:53:01 +02:00
Richard Alpe
d333c66f9c
Verify that the device's factory-default configuration boots cleanly and that the device remains usable afterwards -- i.e. it does not fall back to the fail-secure failure-config. The test exercises the device's own first-boot bootstrap path: it clears the startup-config and reboots with the test-mode startup override set, so confd initialises running from the factory-config (its first-boot path). That mirrors a factory-fresh / factory-reset device and avoids applying a full config swap over the live management session -- confd cannot replace the whole running datastore from within an RPC without timing out, and a factory config may reconfigure the very transport we are connected over. The test is image-generic, using whatever factory-config the running image was built with, so it covers both the stock Infix factory config and any spin factory config. A single-node (1x1) topology is used on purpose: a factory config is not written with a lab full of peers in mind, so booting it across a multi-node topology could trigger broadcast storms or similar. NETCONF only, as it is the one management transport present in every factory config. Signed-off-by: Richard Alpe <richard@bit42.se>
:testgroup: == System Tests verifying system configuration and management: - System hostname configuration and persistence - User account creation, modification, and deletion - Administrative user privilege management - System timezone configuration and handling - UTC offset timezone configuration - System upgrade and firmware management - NTP client configuration and time synchronization include::hostname/Readme.adoc[] <<< include::add_delete_user/Readme.adoc[] <<< include::user_admin/Readme.adoc[] <<< include::nacm-basic/Readme.adoc[] <<< include::timezone/Readme.adoc[] <<< include::timezone_utc_offset/Readme.adoc[] <<< include::upgrade/Readme.adoc[] <<< include::ntp_client/Readme.adoc[]