Skip to content

tests, net, sanity: Add IPv6 family stack validation #2177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 15, 2025
Merged

tests, net, sanity: Add IPv6 family stack validation #2177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions tests/network/conftest.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,6 +224,7 @@ def network_sanity(
network_overhead,
Copy link

@coderabbitai coderabbitai bot Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test Execution Plan

Based on the changes to the network_sanity fixture that add IPv6 family stack validation:

Recommended approach:

  • -m ipv6 - Most efficient approach to verify all tests requiring IPv6 support

Alternative specific test paths:

  • tests/network/connectivity/test_ovs_linux_bridge.py::TestLinuxBridgeConnectivity::test_ipv6_linux_bridge
  • tests/network/connectivity/test_ovs_linux_bridge.py::TestOvsBridgeConnectivity::test_ipv6_ovs_bridge
  • tests/observability/metrics/test_general_metrics.py::TestVirtHCOSingleStackIpv6::test_metric_kubevirt_hco_single_stack_ipv6

Rationale:
The modified network_sanity fixture now validates IPv6 cluster support. All tests marked with ipv6 depend on this fixture and will be validated against IPv6 capabilities.

Copy link
Contributor Author

@EdDev EdDev Oct 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the verification described here are covering this change.

sriov_workers,
ipv4_supported_cluster,
ipv6_supported_cluster,
conformance_tests,
):
"""
Expand Down Expand Up @@ -310,13 +311,13 @@ def _verify_sriov():
f"has {len(sriov_workers)} SRIOV-capable worker nodes"
)

def _verify_ipv4():
if any(test.get_closest_marker("ipv4") for test in collected_tests):
LOGGER.info("Verifying if the cluster supports running IPV4 tests...")
if not ipv4_supported_cluster:
failure_msgs.append("IPv4 is not supported in this cluster")
def _verify_ip_family(family, is_supported_in_cluster):
if any(test.get_closest_marker(family) for test in collected_tests):
LOGGER.info(f"Verifying if the cluster supports running {family} tests...")
if not is_supported_in_cluster:
failure_msgs.append(f"{family} is not supported in this cluster")
else:
LOGGER.info("Validated network lane is running against an IPV4 supported cluster")
LOGGER.info(f"Validated network lane is running against an {family} supported cluster")

def _verify_bgp_env_vars():
"""Verify if the cluster supports running BGP tests.
Expand All @@ -343,7 +344,8 @@ def _verify_bgp_env_vars():
_verify_service_mesh()
_verify_jumbo_frame()
_verify_sriov()
_verify_ipv4()
_verify_ip_family(family="ipv4", is_supported_in_cluster=ipv4_supported_cluster)
_verify_ip_family(family="ipv6", is_supported_in_cluster=ipv6_supported_cluster)
_verify_bgp_env_vars()

if failure_msgs:
Expand Down