Skip to content

net, evpn: refactor helpers for independent endpoint deployment#5248

Open
servolkov wants to merge 1 commit into
RedHatQE:mainfrom
servolkov:net/evpn-helpers-refactor
Open

net, evpn: refactor helpers for independent endpoint deployment#5248
servolkov wants to merge 1 commit into
RedHatQE:mainfrom
servolkov:net/evpn-helpers-refactor

Conversation

@servolkov

@servolkov servolkov commented Jun 16, 2026

Copy link
Copy Markdown
Contributor
What this PR does / why we need it:

Separate shared EVPN infrastructure (bridge VLAN/VNI mappings, L3 VRF) from per-endpoint setup so multiple endpoints can coexist independently.

  • Move VLAN/VNI mappings into deploy_evpn_bridge (shared, created once)
  • Extract deploy_evpn_l3_vrf/teardown_evpn_l3_vrf from L3 endpoint
  • Use uuid-suffixed netns/veth names for endpoint isolation
  • Teardown functions take EvpnEndpoint instead of raw pod/vni args
  • Update test_source_provider_migration to use new signatures
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:

NONE

Summary by CodeRabbit

Release Notes

  • Tests
    • Refactored EVPN test infrastructure to separate L3 VRF provisioning from endpoint provisioning for improved test modularity.
    • Enhanced endpoint isolation using unique namespace naming for each endpoint in test scenarios.
    • Updated test fixture dependencies and simplified function signatures for cleaner test setup and teardown flows.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified
  • Labels: Enabled categories: branch, can-be-merged, cherry-pick, has-conflicts, hold, needs-rebase, size, verified, wip

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (approvers only)
  • /hold cancel - Unblock PR merging
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status
  • /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
  • /regenerate-welcome - Regenerate this welcome message
  • /security-override - Set security check runs to pass (maintainers only)
  • /security-override cancel - Re-run security checks

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest build-container - Rebuild and test container image
  • /retest verify-bugs-are-open - verify-bugs-are-open
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3
  • /cherry-pick-retry <branch> - Retry a failed cherry-pick (merged PRs only)

Branch Management

  • /rebase - Rebase this PR branch onto its base branch

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 2 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
  5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

  • EdDev
  • rnetser

Reviewers:

  • Anatw
  • EdDev
  • azhivovk
  • frenzyfriday
  • nirdothan
  • orelmisan
  • rnetser
  • servolkov
  • yossisegev
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
AI Features
  • Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6[1m])
Security Checks
  • Suspicious Path Detection: Monitors paths: .claude/, .vscode/, .cursor/, .devcontainer/, .pi/, .github/workflows/, .github/actions/
  • Committer Identity Check: Verifies last committer matches PR author
  • Mandatory: Security checks block merge (use /security-override to bypass — maintainers only)

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tests/network/bgp/evpn/test_evpn_connectivity.py (1)

215-231: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

HIGH: new_l2_endpoint is created but never torn down

After switching to endpoint-object teardown, this test removes the old endpoint but does not clean the newly deployed new_l2_endpoint. That leaves endpoint lifecycle asymmetric and risks stale netns/veth artifacts in the FRR pod.

Suggested fix
     new_l2_endpoint = deploy_evpn_l2_endpoint(
         pod=frr_external_pod.pod,
         endpoint_ips=[_L2_ENDPOINT_IPV4, _L2_ENDPOINT_IPV6],
     )
-
-    assert_evpn_workloads_connectivity(
-        target_vm=vm_evpn_target,
-        ref_vm=vm_source_provider,
-        l2_endpoint=new_l2_endpoint,
-        l3_endpoint=external_l3_endpoint,
-        subtests=subtests,
-    )
+    try:
+        assert_evpn_workloads_connectivity(
+            target_vm=vm_evpn_target,
+            ref_vm=vm_source_provider,
+            l2_endpoint=new_l2_endpoint,
+            l3_endpoint=external_l3_endpoint,
+            subtests=subtests,
+        )
+    finally:
+        teardown_evpn_l2_endpoint(endpoint=new_l2_endpoint)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/network/bgp/evpn/test_evpn_connectivity.py` around lines 215 - 231, The
test creates new_l2_endpoint by calling deploy_evpn_l2_endpoint() but never
cleans it up, leaving the endpoint lifecycle asymmetric and risking stale
artifacts in the FRR pod. After the assert_evpn_workloads_connectivity() call
completes, add a teardown_evpn_l2_endpoint(endpoint=new_l2_endpoint) call to
properly clean up the newly deployed endpoint and maintain symmetric resource
management consistent with how external_l2_endpoint is torn down at the
beginning.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/network/bgp/evpn/libevpn.py`:
- Around line 214-218: The UUID suffix generation using uuid.uuid4().hex[:3]
only provides 4096 unique combinations. To improve collision resistance for
potential higher parallelism or longer-lived namespaces in future test
scenarios, extend the hex suffix length from 3 characters to 4 or 5 characters
in the suffix assignment. This change requires modifying only the string slicing
operation where the suffix is generated (uuid.uuid4().hex[:3]) to use a longer
substring, which will then be propagated to all the dependent variables like
netns, veth_pod, and veth_ep that use this suffix.

---

Outside diff comments:
In `@tests/network/bgp/evpn/test_evpn_connectivity.py`:
- Around line 215-231: The test creates new_l2_endpoint by calling
deploy_evpn_l2_endpoint() but never cleans it up, leaving the endpoint lifecycle
asymmetric and risking stale artifacts in the FRR pod. After the
assert_evpn_workloads_connectivity() call completes, add a
teardown_evpn_l2_endpoint(endpoint=new_l2_endpoint) call to properly clean up
the newly deployed endpoint and maintain symmetric resource management
consistent with how external_l2_endpoint is torn down at the beginning.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 817e2f6a-73c7-454e-a8cc-4d135427ab67

📥 Commits

Reviewing files that changed from the base of the PR and between 6730968 and 7d5c838.

📒 Files selected for processing (3)
  • tests/network/bgp/evpn/conftest.py
  • tests/network/bgp/evpn/libevpn.py
  • tests/network/bgp/evpn/test_evpn_connectivity.py

Comment thread tests/network/bgp/evpn/libevpn.py
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 16, 2026
@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

/retest all

Auto-triggered: Files in this PR were modified by merged PR #4994.

Overlapping files

tests/network/bgp/evpn/test_evpn_connectivity.py

@servolkov

Copy link
Copy Markdown
Contributor Author

/verified

$ uv run pytest --cluster-sanity-skip-nodes-check --cluster-sanity-skip-storage-check --skip-deprecated-api-test --cluster-sanity-skip-check tests/network/bgp/evpn
...
collected 8 items / 1 deselected / 7 selected
...
7 of 7 completed, 7 Pass, 0 Fail, 0 Skip, 0 XPass, 0 XFail, 0 Error, 0 ReRun

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the full Test Execution Plan (smoke decision, gating decision, and specific affected tests).
Do NOT submit a blocking review event (REQUEST_CHANGES/APPROVE).
Post a single inline PR comment on Files Changed (non-blocking COMMENT flow).

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file

  2. Identify affected code paths, functions, and classes

  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes

  4. Trace test dependencies through imports, shared utilities, fixture inheritance, fixture teardown, and yield from cleanup in conftest

  5. Detect new tests introduced in the PR

  6. Utilities and libs impact (when utilities/ or libs/ changes):
    You MUST use shell scripts (rg, git diff) to trace the full impact.
    Follow these sub-steps in order:

    6a. Identify modified symbols: For each changed file under utilities/ or libs/,
    list every modified function or method.
    Example: git diff HEAD~1 --unified=0 -- utilities/hco.py | grep '^[+-]def '

    6b. Find direct callers: Search tests and conftest for each symbol from 6a.
    Example: rg -l 'get_hco_version' tests/

    6c. Trace fixture teardown and cleanup: Find fixtures that reach
    the modified symbol through yield from or context-manager wrappers.
    Example: rg -l 'yield from.*enable_common_boot|def.*enable_common_boot' tests/

    6d. Trace same-file callers: In each changed file, find other functions
    whose body calls a modified symbol (including code after yield
    in @contextmanager helpers).
    Example: rg 'get_hco_version|enable_common_boot' utilities/hco.py

    6e. Expand transitively: If function A calls modified B, then
    tests/fixtures that call A are affected — even when the test body
    never imports B directly.

    Do NOT limit impact to tests that import the modified symbol only.

  7. Smoke test impact: Intersect the affected set from step 6 with smoke-marked tests.
    Run: rg -l '@pytest.mark.smoke' tests/
    VERIFY the above command returned actual file paths before concluding False.
    Set True if either condition is met:

    • a smoke-marked file appears in the affected set from 6b-6e, OR
    • any conftest.py in the smoke test's parent-directory hierarchy (up to repo root)
      imports or calls a modified utilities/libs symbol — including autouse fixtures
      that depend on modified functions. ALL tests in that directory and below are affected.
      Example check: for each smoke_file, scan dirname(smoke_file)/conftest.py,
      dirname(dirname(smoke_file))/conftest.py, etc. for modified symbol imports
      and autouse fixtures that depend on modified symbols.
  8. Gating test impact: Intersect the affected set from step 6 with gating-marked tests.
    Run: rg -l '@pytest.mark.gating' tests/
    Set True if a gating-marked file also appears in the affected set from 6b-6e.
    Utilities/libs changes often affect gating tests without affecting smoke tests.
    Do NOT stop analysis after concluding Run smoke tests: False.

Output rules:
Do NOT include analysis step numbers (1-8) in your visible output.

Your deliverable:
Your inline informational comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False — If True, state the dependency path (test → fixture → changed symbol). True ONLY with a verified path.
  • Run gating tests: True / False — If True, state the dependency path. True if any gating-marked test is in the affected set.
  • Affected tests to run (required when utilities/, libs/, or shared conftest changes — list concrete paths even when smoke is False)

Use these formats:

  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When a marker covers multiple affected tests (e.g. -m gating only if ALL gating tests in scope need run)
  • Tag each listed test or group with its marker when not obvious, e.g. (gating) or (smoke)

Real test commands (MANDATORY when changes affect session/runtime code):

When the affected code runs at session/collection time (conftest fixtures, pytest plugins,
config hooks, session-scoped setup) or modifies runtime behavior that unit tests mock away,
you MUST include concrete pytest commands the PR author must run on a real cluster
to verify the change works end-to-end. Include:

  • A command for the error/fix path (the scenario the PR fixes)
  • A command for the happy path (regression: the normal case still works)
  • Use lightweight tests (e.g., --collect-only for startup failures,
    a single small test for runtime behavior)
    If the PR only changes test logic (not utilities/libs/conftest), the affected test
    paths themselves serve as the real test commands — no separate section needed.

Example output for a session-startup fix:

**Real tests (cluster required)**
Error path (the fix):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=nonexistent-sc --collect-only`
Expected: ValueError with clear message, not IndexError

Happy path (regression):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=<valid-sc> -k test_bar`
Expected: session starts normally

Guidelines:

  • Include tests affected directly OR via fixture setup/teardown, yield from cleanup, or transitive utility call chains (caller calls modified helper)
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name when only specific tests use an affected fixture or utility wrapper (preferred for partial file impact)
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal
  • Example: if leaf helper foo() changes, include tests whose fixture teardown calls wrapper bar() where bar() calls foo(), even when the test body only imports an unrelated symbol from the same utilities module

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post one non-blocking inline comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If inline comment API calls fail after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL — Verification rules for smoke and gating decisions:
- For each True decision, you must have traced a concrete path: test file → fixture → utility function → modified symbol.
- Do NOT assume impact based on scope, file proximity, or infrastructure-sounding names.
Only set True when you trace a concrete path through steps 6a-6e, then 7 or 8.
WRONG: "utilities/hco.py changed → run smoke" (no traced dependency path)
WRONG: "Run smoke tests: False" with no affected-test list when gating tests use the changed utility
RIGHT: "Run smoke tests: False, Run gating tests: True" plus tests/.../test_foo.py::TestBar::test_baz (gating)
RIGHT: "Smoke test X uses fixture Y → wrapper Z → changed function W in utilities/hco.py"

Comment thread tests/network/bgp/evpn/conftest.py
@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for smoke and gating markers in evpn tests
echo "=== Smoke markers in evpn ==="
rg -n '`@pytest.mark.smoke`' tests/network/bgp/evpn/

echo "=== Gating markers in evpn ==="
rg -n '`@pytest.mark.gating`' tests/network/bgp/evpn/

echo "=== All test functions in evpn ==="
rg -n '^def test_' tests/network/bgp/evpn/

echo "=== All smoke marker files ==="
rg -l '`@pytest.mark.smoke`' tests/network/bgp/

echo "=== All gating marker files ==="
rg -l '`@pytest.mark.gating`' tests/network/bgp/

echo "=== Fixtures used by test_source_provider_migration ==="
rg -n 'test_source_provider_migration' tests/network/bgp/evpn/

echo "=== All test functions in test_evpn_connectivity.py ==="
rg -n 'def test_' tests/network/bgp/evpn/test_evpn_connectivity.py

echo "=== libevpn imports in test files ==="
rg -rn 'from.*libevpn import\|import.*libevpn' tests/

echo "=== deploy_evpn_bridge callers ==="
rg -n 'deploy_evpn_bridge\|deploy_evpn_l2_endpoint\|deploy_evpn_l3_endpoint\|teardown_evpn_l2_endpoint\|teardown_evpn_l3_endpoint\|deploy_evpn_l3_vrf\|teardown_evpn_l3_vrf' tests/

Length of output: 3201


🏁 Script executed:

#!/bin/bash
echo "=== test_source_provider_migration signature ==="
rg -n -A 15 'def test_source_provider_migration' tests/network/bgp/evpn/test_evpn_connectivity.py

echo "=== external_l3_vrf fixture usage ==="
rg -n 'external_l3_vrf\|external_l3_endpoint\|external_l2_endpoint' tests/network/bgp/evpn/test_evpn_connectivity.py

echo "=== conftest fixtures defined ==="
rg -n 'def external_l' tests/network/bgp/evpn/conftest.py

Length of output: 1362


🏁 Script executed:

#!/bin/bash
# Get the PR diff to find first changed line in conftest.py
gh pr diff 5248 --repo RedHatQE/openshift-virtualization-tests -- tests/network/bgp/evpn/conftest.py | head -40

echo "=== PR number and files ==="
gh pr view 5248 --repo RedHatQE/openshift-virtualization-tests --json files --jq '.files[].path' | head -10

Length of output: 555


🏁 Script executed:

#!/bin/bash
# Get the PR diff via API to find file positions
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/files \
  --jq '.[] | select(.filename == "tests/network/bgp/evpn/conftest.py") | {filename, patch: .patch}' | head -60

echo "=== Get PR commit SHA ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248 \
  --jq '{head_sha: .head.sha, base_sha: .base.sha}'

Length of output: 2770


🏁 Script executed:

#!/bin/bash
# Post inline review comment on first changed line of conftest.py
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/reviews \
  --method POST \
  --field commit_id="7d5c838432948b48069b9595e09ad4c246a18e46" \
  --field body="" \
  --field event="COMMENT" \
  --field "comments[][path]=tests/network/bgp/evpn/conftest.py" \
  --field "comments[][line]=30" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=**Test Execution Plan**

**Run smoke tests: False** — No \`@pytest.mark.smoke\` markers found in \`tests/network/bgp/evpn/\` or any parent directory. Verified with \`rg -l '`@pytest.mark.smoke`' tests/network/bgp/\`.

**Run gating tests: False** — No \`@pytest.mark.gating\` markers found in \`tests/network/bgp/evpn/\` or any parent directory. Verified with \`rg -l '`@pytest.mark.gating`' tests/network/bgp/\`.

---

**Affected tests to run** — all changes are scoped to \`tests/network/bgp/evpn/\`:

- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_udn_vm_and_external_provider\` — uses \`external_l2_endpoint\` (teardown path changed: now passes \`EvpnEndpoint\` object)
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_is_preserved_over_live_migration\` — uses \`external_l2_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider\` — uses \`external_l3_endpoint\` (now depends on new \`external_l3_vrf\` fixture; VRF lifecycle separated)
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_is_preserved_over_live_migration\` — uses \`external_l3_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_source_provider_migration\` — directly modified; \`cudn_evpn_layer2\` param replaced with \`external_l2_endpoint\`

---

**Real tests (cluster required)**

Happy path (regression — verify all existing EVPN scenarios still pass):
\`\`\`
pytest tests/network/bgp/evpn/
\`\`\`
Expected: 7/7 pass.

Fix path (verify new \`external_l3_vrf\` shared-infra fixture and independent endpoint deployment):
\`\`\`
pytest tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider tests/network/bgp/evpn/test_evpn_connectivity.py::test_source_provider_migration -v
\`\`\`
Expected: L3 VRF deployed once via \`external_l3_vrf\`; \`external_l3_endpoint\` and \`external_l2_endpoint\` each get UUID-suffixed netns/veth without conflicts."

Length of output: 4306



Comment thread tests/network/bgp/evpn/conftest.py
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh pr view 5248 --json headRefOid,commits --jq '{head: .headRefOid}'
echo "=== files changed now ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/files --jq '.[].filename'
echo "=== diff for libevpn.py and conftest.py ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/files --jq '.[] | select(.filename=="tests/network/bgp/evpn/conftest.py") | .patch' | head -60
echo "=== check for smoke/gating markers ==="
rg -l '`@pytest.mark.smoke`' tests/network/bgp/ || true
rg -l '`@pytest.mark.gating`' tests/network/bgp/ || true

Length of output: 3067


🏁 Script executed:

#!/bin/bash
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/reviews \
  --method POST \
  --field commit_id="48f365337133047a3e74249cff687348dfa219af" \
  --field body="" \
  --field event="COMMENT" \
  --field "comments[][path]=tests/network/bgp/evpn/conftest.py" \
  --field "comments[][line]=30" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=**Test Execution Plan**

**Run smoke tests: False** — No \`@pytest.mark.smoke\` markers found under \`tests/network/bgp/\` (verified with \`rg -l '`@pytest.mark.smoke`' tests/network/bgp/\`, no matches).

**Run gating tests: False** — No \`@pytest.mark.gating\` markers found under \`tests/network/bgp/\` (verified with \`rg -l '`@pytest.mark.gating`' tests/network/bgp/\`, no matches).

---

**Affected tests to run** — all changes are scoped to \`tests/network/bgp/evpn/\`. Latest commit (48f3653) extracted \`deploy_evpn_l3_vrf\`/\`teardown_evpn_l3_vrf\` into a dedicated \`external_l3_vrf\` fixture, removing the redundant VRF cleanup previously inlined in \`external_l3_endpoint\`:

- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_udn_vm_and_external_provider\` — uses \`external_l2_endpoint\` (teardown now passes \`EvpnEndpoint\` object)
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_is_preserved_over_live_migration\` — uses \`external_l2_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider\` — uses \`external_l3_endpoint\`, which now depends on new module-scoped \`external_l3_vrf\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_is_preserved_over_live_migration\` — uses \`external_l3_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_source_provider_migration\` — directly modified; \`cudn_evpn_layer2\` param replaced with \`external_l2_endpoint\`

---

**Real tests (cluster required)**

Happy path (regression — full suite):
\`\`\`
pytest tests/network/bgp/evpn/
\`\`\`
Expected: 7/7 pass (author reported this locally per PR thread).

Fix path (verify VRF-only teardown ordering and shared-infra reuse across L3 endpoint + VRF fixtures):
\`\`\`
pytest tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_is_preserved_over_live_migration -v
\`\`\`
Expected: \`external_l3_vrf\` deploys/tears down VRF once (module scope); \`external_l3_endpoint\` teardown only removes its own netns/veth without double-tearing-down the VRF."

Length of output: 4608


Test execution plan posted as an inline review comment on tests/network/bgp/evpn/conftest.py.

Separate shared EVPN infrastructure (bridge VLAN/VNI mappings, L3 VRF)
from per-endpoint setup so multiple endpoints can coexist independently.

- Move VLAN/VNI mappings into deploy_evpn_bridge (shared, created once)
- Extract deploy_evpn_l3_vrf/teardown_evpn_l3_vrf from L3 endpoint
- Use uuid-suffixed netns/veth names for endpoint isolation
- Teardown functions take EvpnEndpoint instead of raw pod/vni args
- Simplify endpoint teardown to netns removal only (kernel auto-removes veth peer)
- Update test_source_provider_migration to use new signatures

Signed-off-by: Sergei Volkov <sevolkov@redhat.com>
Assisted-by: Claude Opus 4.6 <noreply@anthropic.com>
@servolkov

Copy link
Copy Markdown
Contributor Author

/verified

this

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the full Test Execution Plan (smoke decision, gating decision, and specific affected tests).
Do NOT submit a blocking review event (REQUEST_CHANGES/APPROVE).
Post a single inline PR comment on Files Changed (non-blocking COMMENT flow).

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file

  2. Identify affected code paths, functions, and classes

  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes

  4. Trace test dependencies through imports, shared utilities, fixture inheritance, fixture teardown, and yield from cleanup in conftest

  5. Detect new tests introduced in the PR

  6. Utilities and libs impact (when utilities/ or libs/ changes):
    You MUST use shell scripts (rg, git diff) to trace the full impact.
    Follow these sub-steps in order:

    6a. Identify modified symbols: For each changed file under utilities/ or libs/,
    list every modified function or method.
    Example: git diff HEAD~1 --unified=0 -- utilities/hco.py | grep '^[+-]def '

    6b. Find direct callers: Search tests and conftest for each symbol from 6a.
    Example: rg -l 'get_hco_version' tests/

    6c. Trace fixture teardown and cleanup: Find fixtures that reach
    the modified symbol through yield from or context-manager wrappers.
    Example: rg -l 'yield from.*enable_common_boot|def.*enable_common_boot' tests/

    6d. Trace same-file callers: In each changed file, find other functions
    whose body calls a modified symbol (including code after yield
    in @contextmanager helpers).
    Example: rg 'get_hco_version|enable_common_boot' utilities/hco.py

    6e. Expand transitively: If function A calls modified B, then
    tests/fixtures that call A are affected — even when the test body
    never imports B directly.

    Do NOT limit impact to tests that import the modified symbol only.

  7. Smoke test impact: Intersect the affected set from step 6 with smoke-marked tests.
    Run: rg -l '@pytest.mark.smoke' tests/
    VERIFY the above command returned actual file paths before concluding False.
    Set True if either condition is met:

    • a smoke-marked file appears in the affected set from 6b-6e, OR
    • any conftest.py in the smoke test's parent-directory hierarchy (up to repo root)
      imports or calls a modified utilities/libs symbol — including autouse fixtures
      that depend on modified functions. ALL tests in that directory and below are affected.
      Example check: for each smoke_file, scan dirname(smoke_file)/conftest.py,
      dirname(dirname(smoke_file))/conftest.py, etc. for modified symbol imports
      and autouse fixtures that depend on modified symbols.
  8. Gating test impact: Intersect the affected set from step 6 with gating-marked tests.
    Run: rg -l '@pytest.mark.gating' tests/
    Set True if a gating-marked file also appears in the affected set from 6b-6e.
    Utilities/libs changes often affect gating tests without affecting smoke tests.
    Do NOT stop analysis after concluding Run smoke tests: False.

Output rules:
Do NOT include analysis step numbers (1-8) in your visible output.

Your deliverable:
Your inline informational comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False — If True, state the dependency path (test → fixture → changed symbol). True ONLY with a verified path.
  • Run gating tests: True / False — If True, state the dependency path. True if any gating-marked test is in the affected set.
  • Affected tests to run (required when utilities/, libs/, or shared conftest changes — list concrete paths even when smoke is False)

Use these formats:

  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When a marker covers multiple affected tests (e.g. -m gating only if ALL gating tests in scope need run)
  • Tag each listed test or group with its marker when not obvious, e.g. (gating) or (smoke)

Real test commands (MANDATORY when changes affect session/runtime code):

When the affected code runs at session/collection time (conftest fixtures, pytest plugins,
config hooks, session-scoped setup) or modifies runtime behavior that unit tests mock away,
you MUST include concrete pytest commands the PR author must run on a real cluster
to verify the change works end-to-end. Include:

  • A command for the error/fix path (the scenario the PR fixes)
  • A command for the happy path (regression: the normal case still works)
  • Use lightweight tests (e.g., --collect-only for startup failures,
    a single small test for runtime behavior)
    If the PR only changes test logic (not utilities/libs/conftest), the affected test
    paths themselves serve as the real test commands — no separate section needed.

Example output for a session-startup fix:

**Real tests (cluster required)**
Error path (the fix):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=nonexistent-sc --collect-only`
Expected: ValueError with clear message, not IndexError

Happy path (regression):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=<valid-sc> -k test_bar`
Expected: session starts normally

Guidelines:

  • Include tests affected directly OR via fixture setup/teardown, yield from cleanup, or transitive utility call chains (caller calls modified helper)
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name when only specific tests use an affected fixture or utility wrapper (preferred for partial file impact)
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal
  • Example: if leaf helper foo() changes, include tests whose fixture teardown calls wrapper bar() where bar() calls foo(), even when the test body only imports an unrelated symbol from the same utilities module

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post one non-blocking inline comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If inline comment API calls fail after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL — Verification rules for smoke and gating decisions:
- For each True decision, you must have traced a concrete path: test file → fixture → utility function → modified symbol.
- Do NOT assume impact based on scope, file proximity, or infrastructure-sounding names.
Only set True when you trace a concrete path through steps 6a-6e, then 7 or 8.
WRONG: "utilities/hco.py changed → run smoke" (no traced dependency path)
WRONG: "Run smoke tests: False" with no affected-test list when gating tests use the changed utility
RIGHT: "Run smoke tests: False, Run gating tests: True" plus tests/.../test_foo.py::TestBar::test_baz (gating)
RIGHT: "Smoke test X uses fixture Y → wrapper Z → changed function W in utilities/hco.py"

Comment thread tests/network/bgp/evpn/conftest.py
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248 --jq '{head_sha: .head.sha, base_sha: .base.sha}'
echo "=== files changed ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/files --jq '.[].filename'
echo "=== diff for conftest.py first hunk ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/files --jq '.[] | select(.filename=="tests/network/bgp/evpn/conftest.py") | .patch' | head -30

Length of output: 1942


🏁 Script executed:

#!/bin/bash
echo "=== smoke markers ==="
rg -l '`@pytest`\.mark\.smoke' tests/network/bgp/ || echo "none"
echo "=== gating markers ==="
rg -l '`@pytest`\.mark\.gating' tests/network/bgp/ || echo "none"
echo "=== check git log for latest commits ==="
git log --oneline -5

Length of output: 625


🏁 Script executed:

#!/bin/bash
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5248/reviews \
  --method POST \
  --field commit_id="2488600e13f5d00d0989ecca20a50e033370ca42" \
  --field body="" \
  --field event="COMMENT" \
  --field "comments[][path]=tests/network/bgp/evpn/conftest.py" \
  --field "comments[][line]=30" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=**Test Execution Plan**

**Run smoke tests: False** — No \`@pytest.mark.smoke\` markers found under \`tests/network/bgp/\` (verified with \`rg -l '`@pytest.mark.smoke`' tests/network/bgp/\`, no matches).

**Run gating tests: False** — No \`@pytest.mark.gating\` markers found under \`tests/network/bgp/\` (verified with \`rg -l '`@pytest.mark.gating`' tests/network/bgp/\`, no matches).

---

**Affected tests to run** — all changes are scoped to \`tests/network/bgp/evpn/\`:

- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_udn_vm_and_external_provider\` — uses \`external_l2_endpoint\` (teardown now passes \`EvpnEndpoint\` object)
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_stretched_l2_connectivity_is_preserved_over_live_migration\` — uses \`external_l2_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider\` — uses \`external_l3_endpoint\`, which now depends on module-scoped \`external_l3_vrf\` fixture (shared VRF setup/teardown)
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_is_preserved_over_live_migration\` — uses \`external_l3_endpoint\` fixture
- \`tests/network/bgp/evpn/test_evpn_connectivity.py::test_source_provider_migration\` — directly modified; \`cudn_evpn_layer2\` param replaced with \`external_l2_endpoint\`

---

**Real tests (cluster required)**

Happy path (regression — full suite):
\`\`\`
pytest tests/network/bgp/evpn/
\`\`\`
Expected: 7/7 pass (author verified locally per PR thread comments).

Fix path (verify shared \`external_l3_vrf\` lifecycle and UUID-suffixed netns/veth isolation across endpoints):
\`\`\`
pytest tests/network/bgp/evpn/test_evpn_connectivity.py::test_routed_l3_connectivity_udn_vm_and_external_provider tests/network/bgp/evpn/test_evpn_connectivity.py::test_source_provider_migration -v
\`\`\`
Expected: \`external_l3_vrf\` deploys/tears down VRF once (module scope); \`external_l3_endpoint\`/\`external_l2_endpoint\` each get unique netns/veth without conflicts and teardown removes only their own namespace."

Length of output: 4443


Test execution plan posted as an inline review comment on tests/network/bgp/evpn/conftest.py.

@azhivovk azhivovk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks

@yossisegev yossisegev left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you Sergei

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants