Skip to content

net, tests, hot-plug: W/A guest-agent deadlock on hot-plugged interfaces - #5584

Merged
rnetser merged 1 commit into
RedHatQE:mainfrom
yossisegev:hot_plug_bug_wa
Aug 9, 2026
Merged

net, tests, hot-plug: W/A guest-agent deadlock on hot-plugged interfaces#5584
rnetser merged 1 commit into
RedHatQE:mainfrom
yossisegev:hot_plug_bug_wa

Conversation

@yossisegev

@yossisegev yossisegev commented Jul 9, 2026

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

CNV-77961 causes guest-agent to stop reporting newly hot-plugged
interfaces, failing tests that depend on interface data from VMI status.
This changes works around the partial VMI status report by validating
the interface from the guest console, so tests continue to run until the
issue is fixed.
This flow is valid because it reflects user's behavior - users (and their
tools) don't necessarily inspect the openshift resources (VMI status) for
checking guest components, but rather might do that directly via the
guest.
As part of this change, functionality from another package
(user_defined_network/ip_specification) was re-used, therefore this
package is handled here as well, including a race fix by explicitly checking
the interfaces are available.

Originally composed by: Anat Wax awax@redhat.com
Assisted-by: Claude noreply@anthropic.com
Assisted-by: Yossi Segev ysegev@redhat.com

Which issue(s) this PR fixes:

CNV-77961

Special notes for reviewer:
jira-ticket:

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

Summary by CodeRabbit

  • Bug Fixes

    • Improved discovery of hot-plugged network interfaces when guest-agent information is unavailable.
    • Added console-based fallback for verifying secondary IPv4 addresses.
    • Added retries and clearer error handling when interfaces or addresses cannot be found.
    • Improved detection of malformed network information and mismatched IPv4 addresses.
  • Refactor

    • Consolidated guest IPv4 address detection into a shared networking utility.
    • Updated network validation tests to use the shared behavior.

@openshift-virtualization-qe-bot

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 (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

📌 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.

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@yossisegev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 02f9d4d8-1649-4c5e-8cb5-0d396e5000a5

📥 Commits

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

📒 Files selected for processing (4)
  • tests/network/l2_bridge/libl2bridge.py
  • tests/network/libs/guest.py
  • tests/network/user_defined_network/ip_specification/libipspec.py
  • tests/network/user_defined_network/ip_specification/test_ip_specification.py
📝 Walkthrough

Walkthrough

The change adds CNV-77961-gated console fallbacks for hot-plugged interface discovery and IPv4 verification. It moves guest IPv4 parsing into a shared guest helper and updates the IP specification test import.

Changes

Console fallback for hot-plugged interfaces

Layer / File(s) Summary
Shared guest IPv4 parsing
tests/network/libs/guest.py
Adds read_guest_interface_ipv4, which runs ip -j -4 addr show, parses console JSON, and raises IpNotFound for invalid or missing IPv4 data.
Hot-plug and static-IP fallback flow
tests/network/l2_bridge/libl2bridge.py
Uses console lookups when CNV-77961 is open. The lookup retries interface discovery, matches MAC addresses case-insensitively, and raises specific errors when interfaces are unavailable.
IPv4 helper migration
tests/network/user_defined_network/ip_specification/libipspec.py, tests/network/user_defined_network/ip_specification/test_ip_specification.py
Removes the local IPv4 helper and imports the shared implementation from tests.network.libs.guest.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Possibly related PRs

Suggested reviewers: anatw, vsibirsk, eddev, nirdothan


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (1 error)

Check name Status Explanation Resolution
Stp Scenario Coverage ❌ Error STP ip-request.md lists six scenarios; the existing file covers east-west, north-south, migration, and power-cycle, but misses upgrade (Tier 2/P1) and default DHCPv4 (Tier 2/P2). Add tests for upgrade and default DHCPv4, or document each intentional exclusion with a scenario-specific follow-up Jira link.
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title is 72 characters and clearly describes the guest-agent workaround for hot-plugged interface handling.
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 exact template headings, and the first section contains meaningful CNV-77961 rationale and implementation content.
Stp Link Required ✅ Passed The PR adds no test_.py file and no new def test_ function; test_ip_specification.py only changes imports.
✨ 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.

@yossisegev

Copy link
Copy Markdown
Contributor Author

/verified

Verified by executing the hot-plug tests on 2 iterations - one on a clean code, second with forcing the guest-agent (with #5467) to make sure this W/A works.
All tests passed on both iterations.

@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 Jul 9, 2026

Copy link
Copy Markdown
Contributor

Tip

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

#!/bin/bash
set -e
echo "=== First changed file diff context ==="
git log --oneline -5
echo "=== Find modified files list ==="
git diff --stat HEAD~2 HEAD -- tests/network/l2_bridge/ 2>/dev/null || git diff --stat origin/main HEAD -- tests/network/l2_bridge/

echo "=== libl2bridge.py content ==="
sed -n '1,60p' tests/network/l2_bridge/libl2bridge.py

echo "=== markers in test_bridge_nic_hot_plug.py ==="
rg -n '`@pytest.mark`' tests/network/l2_bridge/test_bridge_nic_hot_plug.py

echo "=== usages of hot_plug_interface, set_secondary_static_ip_address, hot_plug_interface_and_set_address ==="
rg -rn 'hot_plug_interface|set_secondary_static_ip_address|get_guest_vm_interface_name_by_vmi_interface_name' tests/ --type py -l

echo "=== conftest hierarchy for l2_bridge ==="
find tests/network -iname 'conftest.py'
</shell>

@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 `@tests/network/l2_bridge/libl2bridge.py`:
- Around line 230-235: The is_jira_open fallback currently accepts any interface
IPv4 address instead of verifying the requested one. In the branch around
read_guest_interface_ipv4, compare hot_plugged_interface_ip with
IPv4Address(address=ipv4_address), raise IpNotFound on mismatch, and emit the
LOGGER.warning “Verified” message only after the comparison succeeds.
🪄 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: 7e0cbb0e-6e53-45b6-9d9d-1e575c7f75be

📥 Commits

Reviewing files that changed from the base of the PR and between ce2f137 and 52b9425.

📒 Files selected for processing (4)
  • tests/network/l2_bridge/libl2bridge.py
  • tests/network/libs/guest.py
  • tests/network/user_defined_network/ip_specification/libipspec.py
  • tests/network/user_defined_network/ip_specification/test_ip_specification.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/l2_bridge/libl2bridge.py
@yossisegev

Copy link
Copy Markdown
Contributor Author

change: apply rabbit's validation comment

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

coderabbitai[bot]
coderabbitai Bot previously requested changes Aug 6, 2026

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

🤖 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/l2_bridge/libl2bridge.py`:
- Around line 307-310: Update the warning in hot_plug_interface to state that
console lookup by MAC is being used because Jira issue CNV-77961 is open, rather
than claiming the guest agent failed to report the interface. Preserve the
existing VM, interface, and MAC context.
- Around line 245-249: Update the IpNotFound error message in the static-IP
verification path to add the missing closing parenthesis after the actual
interface IP value, while preserving the existing message content.
🪄 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: 5c8ae502-10f2-4fc8-a41c-24f4b3421dc3

📥 Commits

Reviewing files that changed from the base of the PR and between ce2f137 and c9e3a62.

📒 Files selected for processing (4)
  • tests/network/l2_bridge/libl2bridge.py
  • tests/network/libs/guest.py
  • tests/network/user_defined_network/ip_specification/libipspec.py
  • tests/network/user_defined_network/ip_specification/test_ip_specification.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/l2_bridge/libl2bridge.py
Comment thread tests/network/l2_bridge/libl2bridge.py
@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

Clean rebase detected — no code changes compared to previous head (26a0f72).
The following labels were preserved: changes-requested-coderabbitai[bot].

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@yossisegev

Copy link
Copy Markdown
Contributor Author

/verified

Verified by running all the affected tests (see previous verification comments).

CNV-77961 causes guest-agent to stop reporting newly hot-plugged
interfaces, failing tests that depend on interface data from VMI status.
Work around the bug so tests continue to run until the fix is released.
As part of this change, functionality from another package
(user_defined_network/ip_specification) was re-used, therefore this
package is handled here as well.

Signed-off-by: Anat Wax <awax@redhat.com>
Assisted-by: Claude <noreply@anthropic.com>
Assisted-by: Yossi Segev <ysegev@redhat.com>
@yossisegev

Copy link
Copy Markdown
Contributor Author

/verified

Verified by running all the affected tests (see previous verification comments).

@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/l2_bridge/libl2bridge.py
@coderabbitai

coderabbitai Bot commented Aug 6, 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

base="$(git merge-base HEAD origin/main 2>/dev/null || git rev-parse HEAD~1)"

echo '=== PR head and changed files ==='
git rev-parse HEAD
git diff --name-status "$base"...HEAD

echo '=== changed declarations ==='
git diff --unified=0 "$base"...HEAD -- tests \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?def[[:space:]]+|^[+-][[:space:]]*class[[:space:]]+' \
  || true

echo '=== changed-file diff ==='
git diff --unified=4 "$base"...HEAD -- tests \
  | sed -n '1,1000p'

echo '=== outlines of changed source and affected test modules ==='
for file in \
  tests/network/l2_bridge/libl2bridge.py \
  tests/network/libs/guest.py \
  tests/network/user_defined_network/ip_specification/libipspec.py \
  tests/network/l2_bridge/test_bridge_nic_hot_plug.py \
  tests/network/user_defined_network/ip_specification/test_ip_specification.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    ast-grep outline "$file" --items all || true
  fi
done

echo '=== callers, fixtures, wrappers, and test definitions ==='
rg -n --type py -C 5 \
  '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address|_lookup_hotplugged_iface_via_console)\b|`@pytest`\.(fixture|mark\.(smoke|gating))|^(async )?def test_|^class Test|yield from|autouse\s*=' \
  tests || true

echo '=== smoke and gating test modules ==='
rg -l --type py '`@pytest`\.mark\.smoke\b' tests | sort || true
printf '%s\n' '--- gating ---'
rg -l --type py '`@pytest`\.mark\.gating\b' tests | sort || true

echo '=== ancestor conftest references ==='
for file in \
  tests/conftest.py \
  tests/network/conftest.py \
  tests/network/l2_bridge/conftest.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/ip_specification/conftest.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    rg -n --type py -C 3 \
      '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address)\b|yield from|autouse\s*=' \
      "$file" || true
  fi
done

Length of output: 2632


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5584"
workdir="$(mktemp -d)"
trap 'rm -rf "$workdir"' EXIT

pr_json="$(gh api "repos/$repo/pulls/$pr")"
sha="$(jq -r '.head.sha' <<<"$pr_json")"

echo '=== PR metadata ==='
jq '{head_sha: .head.sha, base_sha: .base.sha, changed_files: .changed_files}' <<<"$pr_json"

echo '=== changed files and changed declarations ==='
gh api --paginate "repos/$repo/pulls/$pr/files?per_page=100" >"$workdir/files.json"
jq -r '.[] | "\(.status)\t\(.filename)"' "$workdir/files.json"
jq -r '.[] | select(.patch != null) | .patch' "$workdir/files.json" \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?def[[:space:]]+|^[+-][[:space:]]*class[[:space:]]+' \
  || true

curl --fail --silent --show-error --location \
  "https://codeload.github.com/$repo/zip/$sha" \
  --output "$workdir/source.zip"
unzip -q "$workdir/source.zip" -d "$workdir"
root="$(find "$workdir" -mindepth 1 -maxdepth 1 -type d | head -n1)"
cd "$root"

echo '=== source outlines ==='
for file in \
  tests/network/l2_bridge/libl2bridge.py \
  tests/network/libs/guest.py \
  tests/network/user_defined_network/ip_specification/libipspec.py \
  tests/network/l2_bridge/test_bridge_nic_hot_plug.py \
  tests/network/user_defined_network/ip_specification/test_ip_specification.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    ast-grep outline "$file" --items all || true
  fi
done

echo '=== changed-helper callers, fixtures, wrappers, and tests ==='
rg -n --type py -C 5 \
  '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address|_lookup_hotplugged_iface_via_console)\b|`@pytest`\.(fixture|mark\.(smoke|gating))|^(async )?def test_|^class Test|yield from|autouse\s*=' \
  tests || true

echo '=== smoke and gating test modules ==='
rg -l --type py '`@pytest`\.mark\.smoke\b' tests | sort || true
printf '%s\n' '--- gating ---'
rg -l --type py '`@pytest`\.mark\.gating\b' tests | sort || true

echo '=== ancestor conftest references ==='
for file in \
  tests/conftest.py \
  tests/network/conftest.py \
  tests/network/l2_bridge/conftest.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/ip_specification/conftest.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    rg -n --type py -C 3 \
      '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address)\b|yield from|autouse\s*=' \
      "$file" || true
  fi
done

Length of output: 203066


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5584"
workdir="$(mktemp -d)"
trap 'rm -rf "$workdir"' EXIT

pr_json="$(gh api "repos/$repo/pulls/$pr")"
sha="$(jq -r '.head.sha' <<<"$pr_json")"
gh api --paginate "repos/$repo/pulls/$pr/files?per_page=100" >"$workdir/files.json"

path="$(jq -r '.[0].filename' "$workdir/files.json")"
patch="$(jq -r '.[0].patch // empty' "$workdir/files.json")"
if [[ -z "$patch" ]]; then
  echo "The first changed file has no patch." >&2
  exit 1
fi

line="$(
  awk '
    /^@@/ {
      h = $0
      sub(/^@@ -[0-9]+(,[0-9]+)? \+/, "", h)
      sub(/ .*/, "", h)
      current = h + 0
      next
    }
    /^\+/ && !/^\+\+\+/ { print current; exit }
    /^ / || /^-/ { current++ }
  ' <<<"$patch"
)"
if [[ -z "$line" ]]; then
  echo "The first changed file has no added line." >&2
  exit 1
fi

cat >"$workdir/comment.md" <<'EOF'
## Test Execution Plan

**Run smoke tests: False** — the smoke-marker search returned concrete paths. Neither direct-caller module is smoke-marked. The ancestor `conftest.py` files do not import or call `hot_plug_interface()`, `set_secondary_static_ip_address()`, `hot_plug_interface_and_set_address()`, or `read_guest_interface_ipv4()`.

**Run gating tests: False** — the gating-marker search returned concrete paths. Neither direct-caller module is gating-marked.

**Affected tests to run**
- `tests/network/l2_bridge/test_bridge_nic_hot_plug.py` — its fixtures directly call `hot_plug_interface()`, `set_secondary_static_ip_address()`, and `hot_plug_interface_and_set_address()`. This covers the normal guest-agent status path and the CNV-77961 console MAC/IP fallback.
- `tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_vm_is_started_with_successful_connectivity` — directly calls `read_guest_interface_ipv4()`.
- `tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_ip_address_is_preserved_over_power_cycle` — directly calls `read_guest_interface_ipv4()` after restart.

**Real tests (cluster required)**

Error path — force the guest-agent failure condition from `#5467`:
```bash
uv run pytest --verbose --jira -rs -s -o log_cli=true \
  --junitxml=xunit_results.xml --pytest-log-file=pytest-tests.log \
  --leftovers-collector --data-collector --tb=native \
  --skip-deprecated-api-test --cluster-sanity-skip-storage-check \
  -m 'not sriov' tests/network/l2_bridge/test_bridge_nic_hot_plug.py

Expected: hot-plug discovery and static-IP validation use console MAC/IP lookup when VMI interface status is absent.

Happy path — use normal guest-agent reporting:

uv run pytest --verbose --jira -rs -s -o log_cli=true \
  --junitxml=xunit_results.xml --pytest-log-file=pytest-tests.log \
  --leftovers-collector --data-collector --tb=native \
  --skip-deprecated-api-test --cluster-sanity-skip-storage-check \
  -m 'not sriov' \
  tests/network/l2_bridge/test_bridge_nic_hot_plug.py \
  tests/network/user_defined_network/ip_specification/test_ip_specification.py

Expected: VMI status verification remains active, and the hot-plug and explicit-IP workflows pass.
EOF

payload="$(
jq -n
--rawfile body "$workdir/comment.md"
--arg commit_id "$sha"
--arg path "$path"
--argjson line "$line"
'{body: $body, commit_id: $commit_id, path: $path, line: $line, side: "RIGHT"}'
)"

for attempt in 1 2; do
if printf '%s' "$payload" |
gh api --method POST "repos/$repo/pulls/$pr/comments" --input - --jq '.id' >/dev/null; then
exit 0
fi
if [[ "$attempt" -eq 1 ]]; then
sleep 2
fi
done

exit 1


Length of output: 3833

---

</details>

`@openshift-virtualization-qe-bot-3`

You are interacting with an AI system.

@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/l2_bridge/libl2bridge.py
@coderabbitai

coderabbitai Bot commented Aug 6, 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

base="$(git merge-base HEAD origin/main 2>/dev/null || git rev-parse HEAD~1)"

echo '=== current head and changed files ==='
git rev-parse HEAD
git diff --name-status "$base"...HEAD

echo '=== changed declarations ==='
git diff --unified=0 "$base"...HEAD -- tests \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?(def|class)[[:space:]]+' || true

echo '=== changed helper references in tests and conftests ==='
rg -n --type py -C 4 \
  '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address|_lookup_hotplugged_iface_via_console)\b' \
  tests || true

echo '=== affected test fixtures, tests, and markers ==='
rg -n --type py -C 5 \
  '`@pytest`\.(fixture|mark\.(smoke|gating))|^(async )?def test_|^class Test|yield from|hot_plug_interface|set_secondary_static_ip_address|read_guest_interface_ipv4' \
  tests/network/l2_bridge/test_bridge_nic_hot_plug.py \
  tests/network/user_defined_network/ip_specification/test_ip_specification.py || true

echo '=== smoke and gating marked files ==='
rg -l --type py '`@pytest`\.mark\.smoke\b' tests | sort || true
printf '%s\n' '--- gating ---'
rg -l --type py '`@pytest`\.mark\.gating\b' tests | sort || true

echo '=== ancestor conftest references ==='
for file in \
  tests/conftest.py \
  tests/network/conftest.py \
  tests/network/l2_bridge/conftest.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/ip_specification/conftest.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    rg -n --type py -C 3 \
      '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address)\b|yield from|autouse\s*=' \
      "$file" || true
  fi
done

Length of output: 2321


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5584"
workdir="$(mktemp -d)"
trap 'rm -rf "$workdir"' EXIT

pr_json="$(gh api "repos/$repo/pulls/$pr")"
sha="$(jq -r '.head.sha' <<<"$pr_json")"

echo '=== PR metadata ==='
jq '{head_sha: .head.sha, base_sha: .base.sha, changed_files: .changed_files}' <<<"$pr_json"

echo '=== changed files and declarations ==='
gh api --paginate "repos/$repo/pulls/$pr/files?per_page=100" >"$workdir/files.json"
jq -r '.[] | "\(.status)\t\(.filename)"' "$workdir/files.json"
jq -r '.[] | select(.patch != null) | .patch' "$workdir/files.json" \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?(def|class)[[:space:]]+' || true

curl --fail --silent --show-error --location \
  "https://codeload.github.com/$repo/zip/$sha" \
  --output "$workdir/source.zip"
unzip -q "$workdir/source.zip" -d "$workdir"
root="$(find "$workdir" -mindepth 1 -maxdepth 1 -type d | head -n1)"
cd "$root"

echo '=== changed-helper callers, fixtures, test definitions, and markers ==='
rg -n --type py -C 5 \
  '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address|_lookup_hotplugged_iface_via_console)\b|`@pytest`\.(fixture|mark\.(smoke|gating))|^(async )?def test_|^class Test|yield from|autouse\s*=' \
  tests || true

echo '=== smoke and gating test files ==='
rg -l --type py '`@pytest`\.mark\.smoke\b' tests | sort || true
printf '%s\n' '--- gating ---'
rg -l --type py '`@pytest`\.mark\.gating\b' tests | sort || true

echo '=== ancestor conftest references ==='
for file in \
  tests/conftest.py \
  tests/network/conftest.py \
  tests/network/l2_bridge/conftest.py \
  tests/network/user_defined_network/conftest.py \
  tests/network/user_defined_network/ip_specification/conftest.py; do
  if [[ -f "$file" ]]; then
    echo "--- $file ---"
    rg -n --type py -C 3 \
      '\b(read_guest_interface_ipv4|hot_plug_interface|set_secondary_static_ip_address|hot_plug_interface_and_set_address)\b|yield from|autouse\s*=' \
      "$file" || true
  fi
done

Length of output: 202594


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5584"
workdir="$(mktemp -d)"
trap 'rm -rf "$workdir"' EXIT

pr_json="$(gh api "repos/$repo/pulls/$pr")"
sha="$(jq -r '.head.sha' <<<"$pr_json")"
gh api --paginate "repos/$repo/pulls/$pr/files?per_page=100" >"$workdir/files.json"

path="$(jq -r '.[0].filename' "$workdir/files.json")"
patch="$(jq -r '.[0].patch // empty' "$workdir/files.json")"
test -n "$patch"

line="$(
  awk '
    /^@@/ {
      header = $0
      sub(/^@@ -[0-9]+(,[0-9]+)? \+/, "", header)
      sub(/ .*/, "", header)
      current = header + 0
      next
    }
    /^\+/ && !/^\+\+\+/ { print current; exit }
    /^ / || /^-/ { current++ }
  ' <<<"$patch"
)"
test -n "$line"

cat >"$workdir/comment.md" <<'EOF'
## Test Execution Plan

**Run smoke tests: False** — the smoke-marker search returned concrete paths. Neither direct-caller module is smoke-marked. The ancestor `conftest.py` files do not import or call `hot_plug_interface()`, `set_secondary_static_ip_address()`, `hot_plug_interface_and_set_address()`, or `read_guest_interface_ipv4()`.

**Run gating tests: False** — the gating-marker search returned concrete paths. Neither direct-caller module is gating-marked.

**Affected tests to run**
- `tests/network/l2_bridge/test_bridge_nic_hot_plug.py` — its fixtures directly call `hot_plug_interface()`, `set_secondary_static_ip_address()`, and `hot_plug_interface_and_set_address()`. These calls cover the normal guest-agent status path and the CNV-77961 console MAC/IP fallback.
- `tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_vm_is_started_with_successful_connectivity` — directly calls `read_guest_interface_ipv4()`.
- `tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_ip_address_is_preserved_over_power_cycle` — directly calls `read_guest_interface_ipv4()` after VM restart.

**Real tests (cluster required)**

Error path — force the guest-agent failure condition from `#5467`:
```bash
uv run pytest --verbose --jira -rs -s -o log_cli=true \
  --junitxml=xunit_results.xml --pytest-log-file=pytest-tests.log \
  --leftovers-collector --data-collector --tb=native \
  --skip-deprecated-api-test --cluster-sanity-skip-storage-check \
  -m 'not sriov' tests/network/l2_bridge/test_bridge_nic_hot_plug.py

Expected: hot-plug discovery and static-IP validation use console MAC/IP lookup when VMI interface status is absent.

Happy path — use normal guest-agent reporting:

uv run pytest --verbose --jira -rs -s -o log_cli=true \
  --junitxml=xunit_results.xml --pytest-log-file=pytest-tests.log \
  --leftovers-collector --data-collector --tb=native \
  --skip-deprecated-api-test --cluster-sanity-skip-storage-check \
  -m 'not sriov' \
  tests/network/l2_bridge/test_bridge_nic_hot_plug.py \
  tests/network/user_defined_network/ip_specification/test_ip_specification.py

Expected: VMI-status verification remains active, and the hot-plug and explicit-IP workflows pass.
EOF

payload="$(
jq -n
--rawfile body "$workdir/comment.md"
--arg commit_id "$sha"
--arg path "$path"
--argjson line "$line"
'{body: $body, commit_id: $commit_id, path: $path, line: $line, side: "RIGHT"}'
)"

for attempt in 1 2; do
if printf '%s' "$payload" |
gh api --method POST "repos/$repo/pulls/$pr/comments" --input - --jq '.id' >/dev/null; then
exit 0
fi
if [[ "$attempt" -eq 1 ]]; then
sleep 2
fi
done

exit 1


Length of output: 3713

---

</details>

`@openshift-virtualization-qe-bot-3`

You are interacting with an AI system.

@azhivovk azhivovk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks

@rnetser

rnetser commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

/approve

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

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

@yossisegev

Copy link
Copy Markdown
Contributor Author

/cherry-pick cnv-4.22 cnv-4.21 cnv-4.20 cnv-4.19 cnv-4.18

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Manual cherry-pick is needed
Cherry pick failed for eccc967 to cnv-4.22:
To cherry-pick run:

git remote update
git checkout cnv-4.22
git pull origin cnv-4.22
git checkout -b hot_plug_bug_wa-cnv-4.22
git cherry-pick eccc96717052419e23adcb3cb5d65b429b6a25a1
# If the above fails with 'is a merge but no -m option', run:
# git cherry-pick -m 1 eccc96717052419e23adcb3cb5d65b429b6a25a1
git push origin hot_plug_bug_wa-cnv-4.22

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Manual cherry-pick is needed
Cherry pick failed for eccc967 to cnv-4.21:
To cherry-pick run:

git remote update
git checkout cnv-4.21
git pull origin cnv-4.21
git checkout -b hot_plug_bug_wa-cnv-4.21
git cherry-pick eccc96717052419e23adcb3cb5d65b429b6a25a1
# If the above fails with 'is a merge but no -m option', run:
# git cherry-pick -m 1 eccc96717052419e23adcb3cb5d65b429b6a25a1
git push origin hot_plug_bug_wa-cnv-4.21

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Cherry-pick conflicts were resolved by AI

Cherry-picked PR net, tests, hot-plug: W/A guest-agent deadlock on hot-plugged interfaces into cnv-4.18: #5965
Conflicts were automatically resolved by AI (claude/claude-opus-4-6-1m).

@yossisegev Manual verification is required — please review the changes and test before merging.

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Cherry-pick conflicts were resolved by AI

Cherry-picked PR net, tests, hot-plug: W/A guest-agent deadlock on hot-plugged interfaces into cnv-4.20: #5966
Conflicts were automatically resolved by AI (claude/claude-opus-4-6-1m).

@yossisegev Manual verification is required — please review the changes and test before merging.

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Cherry-pick conflicts were resolved by AI

Cherry-picked PR net, tests, hot-plug: W/A guest-agent deadlock on hot-plugged interfaces into cnv-4.19: #5967
Conflicts were automatically resolved by AI (claude/claude-opus-4-6-1m).

@yossisegev Manual verification is required — please review the changes and test before merging.

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.