Skip to content

net, tests, udn: Add VM-to-pod connectivity test - #5940

Open
Anatw wants to merge 1 commit into
RedHatQE:mainfrom
Anatw:udn-11432-vm-pod-connectivity
Open

net, tests, udn: Add VM-to-pod connectivity test#5940
Anatw wants to merge 1 commit into
RedHatQE:mainfrom
Anatw:udn-11432-vm-pod-connectivity

Conversation

@Anatw

@Anatw Anatw commented Aug 6, 2026

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

Verify that a VM and a pod, both connected to the same Primary User Defined Network, have connectivity over the UDN interfaces.

Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:

https://redhat.atlassian.net/browse/CNV-51404

Summary by CodeRabbit

  • New Features

    • Added support for identifying the IP address of pods connected to a user-defined network.
    • Improved visibility into connectivity between virtual machines and pods on user-defined networks.
  • Tests

    • Added validation that virtual machines can communicate with pods on user-defined networks.
    • Expanded network connectivity coverage for user-defined network scenarios, including pod readiness and default-network IP resolution.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fff10668-8087-4e9f-b11b-03a16cb8ba45

📥 Commits

Reviewing files that changed from the base of the PR and between 488ca3f and 24f51d3.

📒 Files selected for processing (3)
  • tests/network/user_defined_network/conftest.py
  • tests/network/user_defined_network/libudn.py
  • tests/network/user_defined_network/test_user_defined_network.py
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • RedHatQE/openshift-virtualization-tests-design-docs (manual)

📝 Walkthrough

Walkthrough

Changes

UDN tests now create a running pod in the UDN namespace. The suite resolves the pod’s default network IP and verifies VM-to-pod connectivity with three pings and a one-minute timeout.

UDN connectivity tests

Layer / File(s) Summary
UDN pod fixture
libs/net/udn.py, tests/network/user_defined_network/conftest.py
Enables postponed annotation evaluation and adds the class-scoped udn_pod fixture. The fixture creates udn-pod, waits for it to run, and yields it.
Pod IP resolution and connectivity test
tests/network/user_defined_network/libudn.py, tests/network/user_defined_network/test_user_defined_network.py
Adds lookup_default_pod_ip, which reads the network-status annotation and returns the default network IP. The test uses the IP to verify connectivity from vma_udn.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: ⚪ Minimal · up to 24f51

This PR adds localized VM-to-pod connectivity coverage for Primary User Defined Networks, with no actionable merge-blocking risk remaining beyond normal checks and review.

Possibly related PRs

Suggested labels: new-tests

Suggested reviewers: yossisegev, eddev, frenzyfriday

🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title is under 120 characters and clearly describes the added VM-to-pod connectivity test for UDN.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Pr Template Sections ✅ Passed The live PR body includes all four required headings, and the purpose section contains meaningful connectivity-test content.
Stp Link Required ✅ Passed The new test function has a docstring with a valid Jira URL and the required # marker.
Stp Scenario Coverage ✅ Passed The added test contains a valid Jira traceability link to CNV-51404; no STP link is present, so STP scenario comparison is not required.
✨ 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-6

Copy link
Copy Markdown

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 (PR author or approvers)
  • /hold cancel - Unblock PR merging (PR author or approvers)
  • /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
  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • Anatw
  • EdDev
  • RoniKishner
  • azhivovk
  • dshchedr
  • frenzyfriday
  • nirdothan
  • orelmisan
  • rnetser
  • servolkov
  • vsibirsk
  • 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

📌 Additional Information

Custom Commands:

  • /test-plan — Triggers CodeRabbit to analyze the PR's changed files and post a test execution plan
  • /rerun-smoke — Adds retest-smoke label on the PR to trigger smoke tests execution

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

@Anatw

Anatw commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai, please review this PR.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@Anatw: I will review pull request #5940. I will focus on the new VM-to-pod connectivity test. I will exclude the rearrangement commits noted in the PR description.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@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

🤖 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 `@libs/net/udn.py`:
- Around line 50-53: Update the helper containing the network-status parsing so
the value returned by json.loads is explicitly validated or narrowed to the
expected typed structure before accessing udn_entry["ips"][0]. Ensure the final
return is statically proven to be a str, satisfying strict mypy no-any-return
while preserving the existing network-status selection behavior.
🪄 Autofix

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 Plus

Run ID: 00347232-07f7-48fe-9d01-29c529c8e7ab

📥 Commits

Reviewing files that changed from the base of the PR and between 4fb9df2 and af2435f.

📒 Files selected for processing (3)
  • libs/net/udn.py
  • tests/network/user_defined_network/conftest.py
  • tests/network/user_defined_network/test_user_defined_network.py
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • RedHatQE/openshift-virtualization-tests-design-docs (manual)

Comment thread libs/net/udn.py Outdated
@Anatw

Anatw commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai - Please review this PR (we discussed your single comment. Do you lgtm?)

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-5940 published

Comment thread libs/net/udn.py Outdated
Comment thread tests/network/user_defined_network/test_user_defined_network.py
Comment thread tests/network/user_defined_network/conftest.py Outdated
Comment thread libs/net/udn.py Outdated
@Anatw

Anatw commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

Change: rename lookup_udn_pod_ip -> lookup_default_pod_ip to fit implementation and move i a local helper file.
Add missing TypeHinting.

@Anatw

Anatw commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

change: Added missing tests/network/user_defined_network/libudn.py

@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: 3

🤖 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/user_defined_network/conftest.py`:
- Line 22: Replace the incorrect multiprocessing.dummy Namespace import with
ocp_resources.namespace.Namespace in conftest.py, so the udn_namespace
annotation and its name attribute use the OpenShift resource type yielded by
create_ns.
- Line 5: Add postponed annotation evaluation at the top of the module, then
move the DynamicClient import into the existing TYPE_CHECKING block so it is
available for type checking without runtime import errors.

In `@tests/network/user_defined_network/test_user_defined_network.py`:
- Around line 84-87: Add the required Jira traceability docstring to
TestPrimaryUdn.test_vm_to_pod_connectivity_on_udn, using the CNV-51404 URL and
skip-jira-utils-check marker. Keep the existing test behavior unchanged.
🪄 Autofix

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 Plus

Run ID: 2c873e10-975d-44f1-91a7-c598267915ec

📥 Commits

Reviewing files that changed from the base of the PR and between fa43ae8 and 488ca3f.

📒 Files selected for processing (3)
  • libs/net/udn.py
  • tests/network/user_defined_network/conftest.py
  • tests/network/user_defined_network/test_user_defined_network.py
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • RedHatQE/openshift-virtualization-tests-design-docs (manual)

Comment thread tests/network/user_defined_network/conftest.py
Comment thread tests/network/user_defined_network/conftest.py Outdated
Comment thread tests/network/user_defined_network/test_user_defined_network.py
@Anatw

Anatw commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

Change: fix incorrect import.

@Anatw

Anatw commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

Change: add Jira link.

@servolkov servolkov 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.

LGTM in general, however I would add error handling here, not a must.

@Anatw

Anatw commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

/build-and-push-container

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-5940 published

@Anatw

Anatw commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

/verified

Tested on net-awax-5
Openshift version: 4.22.3
CNV version: 4.23.0
HCO image: brew.registry.redhat.io/rh-osbs/iib:1190218

cnv-tests-runner-containerized/6223
PYTEST_PARAMS: -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py
TEST: TestPrimaryUdn.test_vm_to_pod_connectivity_on_udn STATUS: PASSED
...
= 5 passed, 1 deselected, 1 xpassed, 6 warnings, 1 quarantined in 404.89s (0:06:44) =

@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 libs/net/udn.py
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5940"

echo '=== PR changed files and first patch lines ==='
gh pr diff "$pr" --repo "$repo" --name-only
gh pr diff "$pr" --repo "$repo" --patch | sed -n '1,360p'

echo '=== Changed source outlines ==='
for file in \
  libs/net/udn.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/libudn.py \
  tests/network/user_defined_network/test_user_defined_network.py
do
  if [ -f "$file" ]; then
    echo "--- $file ---"
    ast-grep outline "$file" --items all || true
  fi
done

echo '=== Modified Python definitions in PR diff ==='
gh pr diff "$pr" --repo "$repo" --unified=0 | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?def[[:space:]]' || true

echo '=== Helper definitions, imports, calls, fixtures, and tests ==='
rg -n -A28 -B8 \
  'def _lookup_default_pod_ip\b|def lookup_default_pod_ip\b|def _lookup_udn_pod_ip\b|def udn_pod\b|def test_vm_to_pod_connectivity_on_udn\b|lookup_default_pod_ip\s*\(|_lookup_default_pod_ip\s*\(|udn_pod\b' \
  libs tests/network/user_defined_network

echo '=== Direct caller search across tests and conftest ==='
rg -n -C3 \
  '\b(_lookup_default_pod_ip|lookup_default_pod_ip|_lookup_udn_pod_ip|lookup_udn_pod_ip)\s*\(' \
  tests || true

echo '=== Fixture cleanup and context-manager paths ==='
rg -n -C4 \
  'yield from|`@pytest`\.fixture|`@contextmanager`|lookup_default_pod_ip|_lookup_default_pod_ip' \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/libudn.py \
  tests/conftest.py 2>/dev/null || true

echo '=== Smoke marker files ==='
rg -l '`@pytest`\.mark\.smoke' tests/ || true
echo '=== Gating marker files ==='
rg -l '`@pytest`\.mark\.gating' tests/ || true

echo '=== Markers in the affected UDN test module ==='
rg -n -C3 '`@pytest`\.mark\.(smoke|gating)|test_vm_to_pod_connectivity_on_udn|class Test' \
  tests/network/user_defined_network/test_user_defined_network.py

echo '=== Conftest files in hierarchy ==='
for file in \
  conftest.py \
  tests/conftest.py \
  tests/network/conftest.py \
  tests/network/user_defined_network/conftest.py
do
  if [ -f "$file" ]; then
    echo "--- $file ---"
    rg -n -C3 'lookup_default_pod_ip|_lookup_default_pod_ip|udn_pod|autouse' "$file" || true
  fi
done

Length of output: 112555


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5940"
head_sha=$(gh pr view "$pr" --repo "$repo" --json headRefOid --jq '.headRefOid')

body=$(cat <<'EOF'
## Test Execution Plan

**Run smoke tests: False** — The smoke-marked test files do not import or reach `lookup_default_pod_ip` or the `udn_pod` fixture. The UDN `conftest.py` is not in a smoke test parent hierarchy.

**Run gating tests: False** — `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` is not gating-marked. The gating test in the same module uses only `server` and `client`; it does not use `udn_pod` or `lookup_default_pod_ip`.

**Affected tests to run**
- `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` (ipv4, single_nic)

**Real tests (cluster required)**

Error/fix path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn`

Expected: the class-scoped `udn_pod` fixture creates a pod in the Primary UDN namespace, `lookup_default_pod_ip` selects the `default` network-status entry, and `vma_udn` can ping that IP.

Happy path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_basic_connectivity_between_udn_vms`

Expected: existing VM-to-VM connectivity in the same Primary UDN namespace remains successful.
EOF
)

payload=$(jq -n \
  --arg commit_id "$head_sha" \
  --arg body "$body" \
  '{
    commit_id: $commit_id,
    event: "COMMENT",
    comments: [{
      path: "libs/net/udn.py",
      line: 1,
      side: "RIGHT",
      body: $body
    }]
  }')

gh api \
  --method POST \
  "repos/$repo/pulls/$pr/reviews" \
  --input - <<<"$payload" \
  --jq '{id, state, html_url, comments: [.comments[] | {path, line, side, body}]}'

Length of output: 2404


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5940"

existing_count=$(gh api --paginate \
  "repos/$repo/pulls/$pr/comments?per_page=100" \
  --jq '[.[] | select(.user.login == "coderabbitai[bot]" or .user.login == "coderabbitai") | select(.path == "libs/net/udn.py" and .line == 1 and (.body | contains("## Test Execution Plan"))] | length')

if [ "$existing_count" -eq 0 ]; then
  head_sha=$(gh pr view "$pr" --repo "$repo" --json headRefOid --jq '.headRefOid')
  body=$(cat <<'EOF'
## Test Execution Plan

**Run smoke tests: False** — The smoke-marked test files do not import or reach `lookup_default_pod_ip` or the `udn_pod` fixture. The UDN `conftest.py` is not in a smoke test parent hierarchy.

**Run gating tests: False** — `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` is not gating-marked. The gating test in the same module uses only `server` and `client`; it does not use `udn_pod` or `lookup_default_pod_ip`.

**Affected tests to run**
- `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` (ipv4, single_nic)

**Real tests (cluster required)**

Error/fix path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn`

Expected: the class-scoped `udn_pod` fixture creates a pod in the Primary UDN namespace, `lookup_default_pod_ip` selects the `default` network-status entry, and `vma_udn` can ping that IP.

Happy path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_basic_connectivity_between_udn_vms`

Expected: existing VM-to-VM connectivity in the same Primary UDN namespace remains successful.
EOF
)
  jq -n \
    --arg commit_id "$head_sha" \
    --arg body "$body" \
    '{commit_id: $commit_id, event: "COMMENT", comments: [{path: "libs/net/udn.py", line: 1, side: "RIGHT", body: $body}]}' \
  | gh api --method POST "repos/$repo/pulls/$pr/reviews" --input - --jq '{id, state, html_url}'
else
  gh api --paginate \
    "repos/$repo/pulls/$pr/comments?per_page=100" \
    --jq '.[] | select(.user.login == "coderabbitai[bot]" or .user.login == "coderabbitai") | select(.path == "libs/net/udn.py" and .line == 1 and (.body | contains("## Test Execution Plan"))) | {id, path, line, side}'
fi

Length of output: 3342


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5940"
comment_query='[.[] | select(.path == "libs/net/udn.py" and .line == 1 and (.body | contains("## Test Execution Plan")))]'

existing_count=$(gh api --paginate \
  "repos/$repo/pulls/$pr/comments?per_page=100" \
  --jq "$comment_query | length")

if [ "$existing_count" -gt 0 ]; then
  gh api --paginate \
    "repos/$repo/pulls/$pr/comments?per_page=100" \
    --jq "$comment_query | .[] | {id, path, line, side}"
  exit 0
fi

head_sha=$(gh pr view "$pr" --repo "$repo" --json headRefOid --jq '.headRefOid')
body=$(cat <<'EOF'
## Test Execution Plan

**Run smoke tests: False** — The smoke-marked test files do not import or reach `lookup_default_pod_ip` or the `udn_pod` fixture. The UDN `conftest.py` is not in a smoke test parent hierarchy.

**Run gating tests: False** — `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` is not gating-marked. The gating test in the same module uses only `server` and `client`; it does not use `udn_pod` or `lookup_default_pod_ip`.

**Affected tests to run**
- `tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn` (ipv4, single_nic)

**Real tests (cluster required)**

Error/fix path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_vm_to_pod_connectivity_on_udn`

Expected: the class-scoped `udn_pod` fixture creates a pod in the Primary UDN namespace, `lookup_default_pod_ip` selects the `default` network-status entry, and `vma_udn` can ping that IP.

Happy path:
`pytest -s -o log_cli=true -m tier2 --jira --skip-deprecated-api-test tests/network/user_defined_network/test_user_defined_network.py::TestPrimaryUdn::test_basic_connectivity_between_udn_vms`

Expected: existing VM-to-VM connectivity in the same Primary UDN namespace remains successful.
EOF
)

jq -n \
  --arg commit_id "$head_sha" \
  --arg body "$body" \
  '{commit_id: $commit_id, event: "COMMENT", comments: [{path: "libs/net/udn.py", line: 1, side: "RIGHT", body: $body}]}' \
| gh api --method POST "repos/$repo/pulls/$pr/reviews" --input - --jq '{id, state, html_url}'

Length of output: 2566


@openshift-virtualization-qe-bot-3: The inline test execution plan is posted on libs/net/udn.py, Line 1.

You are interacting with an AI system.

Test successful connectivity from a VM to a pod, both connected to the UDN.

Signed-off-by: Anat Wax <awax@redhat.com>
Assisted-by: Claude <noreply@anthropic.com>
@Anatw

Anatw commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

Change: raise IpNotFound if no ip were assigned to the pod.

@Anatw

Anatw commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/verified

net-awax-5 (locally)
Openshift version: 4.22.3
CNV version: 4.23.0
HCO image: brew.registry.redhat.io/rh-osbs/iib:1190218
uv run pytest -svv -o log_cli=true --pdbcls=IPython.terminal.debugger:TerminalPdb --skip-deprecated-api-test --tc-format=python tests/network/user_defined_network/test_user_defined_network.py -k test_vm_to_pod_connectivity_on_udn
TEST: TestPrimaryUdn.test_vm_to_pod_connectivity_on_udn STATUS: PASSED
____ 1 of 1 completed, 1 Pass, 0 Fail, 0 Skip, 0 XPass, 0 XFail, 0 Error, 0 ReRun _____

@maiqueb

maiqueb commented Aug 13, 2026

Copy link
Copy Markdown

/lgtm

@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"

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5940"

echo "=== Current PR metadata and changed files ==="
gh pr view "$pr" --repo "$repo" --json headRefOid,baseRefOid,files \
  --jq '{headRefOid, baseRefOid, files: [.files[] | {path, additions, deletions}]}'

echo "=== Current PR patch ==="
gh pr diff "$pr" --repo "$repo" --patch

echo "=== First changed lines on the PR branch ==="
git diff --unified=0 "$(git merge-base HEAD origin/main)" HEAD -- \
  | awk '
      /^\+\+\+ b\// { file=substr($0, 7) }
      /^@@/ {
        if (match($0, /\+[0-9]+/)) {
          hunk=substr($0, RSTART + 1, RLENGTH - 1)
          sub(/,.*/, "", hunk)
          print file ": right-side hunk starts at line " hunk
        }
      }'

echo "=== Outlines ==="
for f in \
  libs/net/udn.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/libudn.py \
  tests/network/user_defined_network/test_user_defined_network.py
do
  test -f "$f" && { echo "--- $f"; ast-grep outline "$f" --items all; }
done

echo "=== Modified definitions and helper call paths ==="
git diff --unified=0 "$(git merge-base HEAD origin/main)" HEAD -- \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?def[[:space:]]' || true
rg -n -C4 \
  '\b(lookup_default_pod_ip|_lookup_default_pod_ip|lookup_udn_pod_ip|_lookup_udn_pod_ip|udn_pod)\b' \
  libs tests || true

echo "=== Fixture cleanup and wrappers ==="
rg -n -C4 \
  'yield from|`@pytest`\.fixture|`@contextmanager`|lookup_default_pod_ip|_lookup_default_pod_ip|udn_pod' \
  tests/conftest.py tests/network/conftest.py tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/libudn.py 2>/dev/null || true

echo "=== Smoke and gating marker files ==="
rg -l '`@pytest`\.mark\.smoke' tests/ || true
rg -l '`@pytest`\.mark\.gating' tests/ || true

echo "=== Affected UDN module markers and tests ==="
rg -n -C3 \
  '`@pytest`\.mark\.(smoke|gating)|def test_|class Test' \
  tests/network/user_defined_network/test_user_defined_network.py

Length of output: 7999


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== Source outlines ==="
for f in \
  libs/net/udn.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/libudn.py \
  tests/network/user_defined_network/test_user_defined_network.py
do
  echo "--- $f"
  ast-grep outline "$f" --items all
done

echo "=== Helper calls, fixtures, tests, and same-file callers ==="
rg -n -C5 \
  '\b(lookup_default_pod_ip|udn_pod|vma_udn|server|client)\b|`@pytest`\.fixture|yield from|`@contextmanager`|def test_' \
  tests/network/user_defined_network libs/net/udn.py

echo "=== Direct imports and calls outside the changed UDN files ==="
rg -n -C3 \
  '(from\s+tests\.network\.user_defined_network\.libudn\s+import|lookup_default_pod_ip\s*\()' \
  tests libs || true

echo "=== Smoke marker files and their conftest ancestry ==="
smoke_files=$(rg -l '`@pytest`\.mark\.smoke' tests/ || true)
printf '%s\n' "$smoke_files"
while IFS= read -r f; do
  test -z "$f" && continue
  d=$(dirname "$f")
  while :; do
    candidate="$d/conftest.py"
    if test -f "$candidate"; then
      hits=$(rg -n 'lookup_default_pod_ip|udn_pod|tests\.network\.user_defined_network\.libudn' "$candidate" || true)
      test -n "$hits" && printf '%s\n%s\n' "--- $candidate" "$hits"
    fi
    test "$d" = "tests" && break
    d=$(dirname "$d")
  done
done <<< "$smoke_files"

echo "=== Gating marker files and UDN test marker scope ==="
rg -n -C3 '`@pytest`\.mark\.gating|def test_' tests/network/user_defined_network/test_user_defined_network.py
rg -l '`@pytest`\.mark\.gating' tests/ || true

echo "=== Existing CodeRabbit inline plan on the requested first line ==="
gh api --paginate \
  'repos/RedHatQE/openshift-virtualization-tests/pulls/5940/comments?per_page=100' \
  --jq '.[] | select((.user.login == "coderabbitai[bot]" or .user.login == "coderabbitai") and .path == "libs/net/udn.py" and .line == 1 and (.body | contains("## Test Execution Plan"))) | {id, commit_id, body}'

Length of output: 75581


@openshift-virtualization-qe-bot-3: The required inline test execution plan already exists on libs/net/udn.py, Line 1, for the current PR head. I did not post a duplicate comment.


🧠 Learnings used
Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T14:00:59.076Z
Learning: In the openshift-virtualization-tests repository, when responding to test execution plan requests from openshift-virtualization-qe-bot-3, CodeRabbit must post ONLY an inline review comment on the Files Changed tab and then stop immediately without generating any follow-up comments in the PR discussion thread. No acknowledgment messages, no confirmation of posting, no explanation - silence after posting the inline review equals success. Additional comments create empty/meaningless reviews that clutter the PR.

Learnt from: jpeimer
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-22T15:56:00.157Z
Learning: In the openshift-virtualization-tests repository, when responding to test execution plan requests from openshift-virtualization-qe-bot-3, do NOT use "REQUEST_CHANGES" review type if the PR author has already marked the PR as verified (e.g., with `/verified` command). Test execution plans are informational guides, not blocking requirements. Use COMMENT event for informational test plans, or only REQUEST_CHANGES if there are actual code issues that need to be addressed before merging.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T14:06:22.391Z
Learning: In the openshift-virtualization-tests repository, when posting test execution plan inline review comments using GitHub API, the full test execution plan content must go in the `comments[].body` field (which appears on Files Changed tab), NOT in the top-level `body` field (which appears in PR discussion thread). The top-level `body` field should be omitted or left empty to avoid posting redundant comments in the PR discussion thread.

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-16T10:28:54.212Z
Learning: In the openshift-virtualization-tests repository, when determining smoke test impact for test execution plans, only set "Run smoke tests: True" if there is a verified, traceable dependency path from smoke tests to the changed code. Session-scoped fixtures or infrastructure-sounding changes do NOT automatically imply smoke test impact - the dependency chain must be explicitly verified using shell scripts before recommending smoke test execution.

You are interacting with an AI system.

@Anatw

Anatw commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

/check-can-merge

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.