diff --git a/test/case/system/factory_config/Readme.adoc b/test/case/system/factory_config/Readme.adoc deleted file mode 100644 index d6689e35f..000000000 --- a/test/case/system/factory_config/Readme.adoc +++ /dev/null @@ -1,34 +0,0 @@ -=== Boot From Factory Config - -ifdef::topdoc[:imagesdir: {topdoc}../../test/case/system/factory_config] - -==== Description - -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. - -This exercises the device's own first-boot bootstrap path: with no -startup-config present, confd initialises running from the factory-config. -That is exactly what a factory-fresh (or factory-reset) device does, and -it avoids applying a full config swap over the live management session. - -The test is image-generic: it uses 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 topology is used on purpose: a factory config is not written -with a lab full of peers in mind, so applying it across a multi-node -topology could trigger broadcast storms or similar. - -==== Topology - -image::topology.svg[Boot From Factory Config topology, align=center, scaledwidth=75%] - -==== Sequence - -. Set up topology and attach to target DUT -. Determine factory-config hostname -. Clear startup-config so the device boots from factory -. Reboot onto the factory config -. Verify device is usable and not in failure-config diff --git a/test/case/system/factory_config/Readme.adoc b/test/case/system/factory_config/Readme.adoc new file mode 120000 index 000000000..ae32c8412 --- /dev/null +++ b/test/case/system/factory_config/Readme.adoc @@ -0,0 +1 @@ +test.adoc \ No newline at end of file diff --git a/test/case/system/factory_config/test.adoc b/test/case/system/factory_config/test.adoc new file mode 100644 index 000000000..59b99a4b0 --- /dev/null +++ b/test/case/system/factory_config/test.adoc @@ -0,0 +1,24 @@ +=== Boot From Factory Config + +ifdef::topdoc[:imagesdir: {topdoc}../../test/case/system/factory_config] + +==== Description + +Verify that the device boots cleanly from its factory-config and stays +usable, i.e. it does not fall back to the fail-secure failure-config. +Clearing the startup-config makes confd bootstrap running from the +factory-config on the next boot, as on a factory-fresh device. + +==== Topology + +image::topology.svg[Boot From Factory Config topology, align=center, scaledwidth=75%] + +==== Sequence + +. Set up topology and attach to target DUT +. Determine factory-config hostname +. Clear startup-config so the device boots from factory +. Reboot onto the factory config +. Verify device is usable and not in failure-config + + diff --git a/test/case/system/factory_config/topology.svg b/test/case/system/factory_config/topology.svg index 1e10fc28e..6fc6f47a8 100644 --- a/test/case/system/factory_config/topology.svg +++ b/test/case/system/factory_config/topology.svg @@ -1,8 +1,7 @@ - +