vyos-1x.git/smoketest/scripts/cli/test_protocols_failover.py, branch rollingVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling2025-10-21T19:03:16+00:00smoketest: T7858: make failover route testcases failfast main argument dynamic2025-10-21T19:03:16+00:00Christian Breunigchristian@breunig.cc2025-10-20T16:58:23+00:00urn:sha1:156ff1849d58c900f05b5ae568a3776dee530632
This extends commit 2c521f135 ("smoketest: T7858: make failfast main argument
dynamic").
T7948: always call setUp() and tearDown() base class methods2025-10-21T19:03:16+00:00Christian Breunigchristian@breunig.cc2025-10-20T16:52:10+00:00urn:sha1:4995a58f998d3bdd055e49e919945bc0aa939be4
While working on task T7664 (FRR 10.4 upgrade), I identified the need for
additional validation and safeguards around the FRR management daemon. The
most appropriate place for this logic is in the setUp() and tearDown() methods
of the smoketest base class, VyOSUnitTestSHIM.
However, during implementation, it became apparent that test cases do not
consistently invoke the base class's setup and teardown methods. This
inconsistency complicates the process of capturing the FRR mgmtd PID at the
start of a test and verifying that it remains unchanged by the end - a key step
in detecting crashes or unexpected terminations (e.g., SIGSEGV) of the FRR
management daemon during tests.
T5942: Make failover support dhcp-interface2025-10-14T12:05:07+00:00Kyrylo Yatsenkohedrok@gmail.com2025-09-26T19:59:43+00:00urn:sha1:47d5f21b7770b0b8dcd29272e6c93bea9028adfe
* Refactor XML a little: move common dhcp-interface properties to
separate include file
* Add failover support for dhcp-interface
* Add test for DHCP in failover protocol
T7803: Make failover route vrf-aware2025-10-08T12:07:59+00:00Kyrylo Yatsenkohedrok@gmail.com2025-09-22T19:10:22+00:00urn:sha1:931e5b5712b4fa8b13027291eb21881c40b8a051
* Added 'protocol failover' to 'set vrf name':
set vrf name red protocols failover route 10.11.0.110/32 next-hop 10.0.0.2
* Added vrf and interface to target:
set ... next-hop 10.0.0.2 check target '10.120.0.21' vrf blue
set ... next-hop 10.0.0.2 check target '10.120.0.21' interface eth1
Last two are needed when check VRF is not same as route VRF.
In this case icmp can use any/both options, tcp requires `vrf` and
arp requires `interface`