vyos-1x.git/smoketest/scripts/cli/test_interfaces_ethernet.py, branch rolling

smoketest: T8147: disable adaptive_rx|tx for virtio drivers

2026-05-02T18:39:32+00:00

Kernel 6.18 exposes support for adaptive_rx interrupt coalescing - but if set via ethtool, it still is in disabled state. $ sudo ethtool -C eth2 adaptive-rx on $ sudo ethtool -c eth2 Coalesce parameters for eth2: Adaptive RX: off TX: n/a Disable testcase for virtio modules.

vyos.ifconfig: T8358: clear qdiscs when deleting mirror CLI node

2026-03-10T04:15:32+00:00

When removing the mirror CLI node to stop mirroring or redirecting traffic to another interface, the egress configuration was not cleared. This caused traffic to continue being sent out the SPAN port even after the node was removed. Fix by properly clearing all tc(8) qdiscs. Update smoketests to verify nothing remains after mirror deletion.

ethtool: T7730: Add configuration coalesce for interface

2026-01-22T07:52:44+00:00

This change introduces CLI support for configuring network interface interrupt coalescing parameters via `netlink`. Note: Not all NIC drivers support interrupt coalescing. On unsupported interfaces, `netlink` returns an error and the VyOS commit will fail.

ethernet: T8142: do not raise ValueError for non-existing interfaces

2026-01-04T07:19:00+00:00

Call verify_interface_exists() with state_required=True to ensure the interface exists physically and is recognized by the kernel, rather than relying on its presence in the CLI configuration. Unlike bridge or bond interfaces, Ethernet interfaces are not virtual and must be physically present. Ethtool() instance can only be created when the physical interface exists, otherwise a ValueError is raised.

smoketest: T7948: always verify FRRs mgmtd PID is unchanged

2025-10-21T19:03:16+00:00

Upgrades to FRR 10.4 have shown that there are cases where FRRs mgmtd will SIGSEGV - to cover for this case and fail the smoketests we will monitor the PID of the mgmtd process.

frr: T7664: drop BASH/SED implementation in smoketest getFRRconfig()

2025-10-16T14:33:44+00:00

Rathern then re-inventing the wheel by outself we import the frr-reload.py script and their read-in function of the current vtysh configuration.

smoketest: T7858: use pylint for our testcases

2025-09-30T15:25:25+00:00

smoketest: T7858: make failfast main argument dynamic

2025-09-30T15:19:06+00:00

When smoketest debugging is enabled (by creating the file /tmp/vyos.smoketest.debug), all available smoketests will fail fast instead of running to completion. This helps reduce test time when something is broken or undergoing refactoring, as it avoids waiting for the full test suite to finish.

T7591: remove copyright years from source files

2025-06-28T21:16:52+00:00

The legal team says years are not necessary so we can go ahead with it, since it will simplify backporting. Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \ 's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors /g' In addition we will error-out during "make" if someone re-adds a legacy copyright notice

frr: T6746: additional improvements after 10.2 upgrade (#4259)

2024-12-30T19:35:08+00:00

* smoketest: T6746: add substring search in getFRRconfig() Some daemons (e.g. bgpd) have several nested substrings/sections like router bgp 100 address-family ipv4 unicast .. exit-address-family exit We can now use getFRRconfig() with the substring option to extract only address-family ipv4 unicast .. exit-address-family Making config validation more granular * frrender: T6746: only re-render FRR config if config_dict did change * frrender: T6746: fix naming glitch isis/eigrp * frrender: T6746: add --stdout option when running with debug flags * smoketest: T6746: remove unneeded commit_guard time It was an invalid workarround as the underlaying issue seems to be a race condition in CStore. The commit process is not finished until all pending files from VYATTA_CHANGES_ONLY_DIR are copied to VYATTA_ACTIVE_CONFIGURATION_DIR. This is done inside libvyatta-cfg1 and the FUSE UnionFS part. On large non-interactive commits FUSE UnionFS might not replicate the real state in time, leading to errors when querying the working and effective configuration. TO BE DELETED AFTER SWITCH TO IN MEMORY CONFIG