Skip to content

Net multi arch regression#4810

Merged
rnetser merged 1 commit into
RedHatQE:mainfrom
yossisegev:net-multi-arch-regression
Jun 17, 2026
Merged

Net multi arch regression#4810
rnetser merged 1 commit into
RedHatQE:mainfrom
yossisegev:net-multi-arch-regression

Conversation

@yossisegev

@yossisegev yossisegev commented May 11, 2026

Copy link
Copy Markdown
Contributor
Short description:

Adjust network tests to be able to run on specific arch on multi-arch clusters, and also handle instabilities that was exposed while working on multi-architecture support.

More details:
  • Support the architecture label in VM's creation
    This change includes accessing constants.Images rather than importing
    Images at module level to ensure the updated Images on run-time is
    referenced.
  • Stability: Remove NetworkData (for setting IP) from VM configuration when OVN-K8s DHCP is used.
  • Stability: Retrieve interface name dynamically.
What this PR does / why we need it:

This is required for testing regression of network tests on multi-arch clusters.

jira-ticket:

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

@coderabbitai

coderabbitai Bot commented May 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Adds an optional architecture field to VMISpec, wires pytest config into the VM factory to default VMI architecture from py_config["cpu_arch"], and updates IP-spec tests to derive guest interface names from the VMI at runtime instead of a hardcoded constant.

Changes

Architecture-aware VM configuration and test refactoring

Layer / File(s) Summary
VM architecture field and config-driven factory wiring
libs/vm/spec.py, libs/vm/factory.py
VMISpec adds optional architecture: str | None. Factory imports pytest_testconfig.config as py_config and _fill_vm_spec_defaults() sets vmi_spec.architecture from py_config["cpu_arch"] when unset and cluster type is MULTIARCH.
IP specification test interface name refactoring
tests/network/user_defined_network/ip_specification/test_ip_specification.py
Remove hardcoded FIRST_GUEST_IFACE_NAME constant and typing.Final import; remove unused cloudinit import; remove in-test cloudinit.NetworkData construction and add_cloud_init calls; update guest IPv4 verification in both tests to call read_guest_interface_ipv4 with vm_under_test.vmi.interfaces[0].interfaceName and assert the returned value equals ip_to_request.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • EdDev
  • orelmisan
  • frenzyfriday
  • nirdothan
  • servolkov
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title 'Net multi arch regression' is vague and uses generic phrasing that doesn't clearly convey the main changes in the pull request. Consider a more specific title like 'Add architecture support to VM specs for multi-arch cluster testing' to better describe the primary change.
✅ Passed checks (3 passed)
Check name Status Explanation
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.
Description check ✅ Passed PR description covers key objectives, changes, and rationale, but uses informal section names that deviate from template structure.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ 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 and usage tips.

@yossisegev

Copy link
Copy Markdown
Contributor Author

/build-and-push-container

@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

Report bugs in Issues

Welcome! 🎉

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

🔄 Automatic Actions

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

📋 Available Commands

PR Status Management

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

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

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])

💡 Tips

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

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

@yossisegev

Copy link
Copy Markdown
Contributor Author

/build-and-push-container

@yossisegev

Copy link
Copy Markdown
Contributor Author

/retest build-container

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

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

1 similar comment
@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

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

Comment thread libs/vm/factory.py Outdated
Comment thread tests/network/conftest.py Outdated
@yossisegev

Copy link
Copy Markdown
Contributor Author

/wip

@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[bot]
coderabbitai Bot previously approved these changes Jun 15, 2026
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
echo "=== Modified symbols in libs/vm/factory.py ==="
git diff origin/main...HEAD --unified=0 -- libs/vm/factory.py | grep '^[+-]def '

echo ""
echo "=== Modified fields/lines in libs/vm/spec.py ==="
git diff origin/main...HEAD --unified=0 -- libs/vm/spec.py

echo ""
echo "=== Same-file callers of fedora_image in libs/vm/factory.py ==="
rg -n "fedora_image" libs/vm/factory.py

echo ""
echo "=== Direct callers of fedora_image in tests/ and libs/ ==="
rg -rn "fedora_image\b" tests/ libs/ --type py -l

echo ""
echo "=== Transitive: functions that call fedora_image (same file) ==="
rg -n "fedora_vm\|fedora_image" libs/vm/factory.py

echo ""
echo "=== Files calling fedora_vm in tests/ and conftest files ==="
rg -rn "fedora_vm\b" tests/ --type py -l

echo ""
echo "=== Smoke test files ==="
rg -rn "`@pytest.mark.smoke`" tests/ --type py -l

echo ""
echo "=== Gating test files ==="
rg -rn "`@pytest.mark.gating`" tests/ --type py -l

echo ""
echo "=== Do gating files import from libs.vm? ==="
GATING_FILES=$(rg -rn "`@pytest.mark.gating`" tests/ --type py -l)
for f in $GATING_FILES; do
  if rg -q "from libs\.vm|import libs\.vm" "$f" 2>/dev/null; then
    echo "GATING+LIBS.VM MATCH: $f"
    rg -n "from libs\.vm|import libs\.vm" "$f"
  fi
done
echo "Gating libs.vm check done"

echo ""
echo "=== Do smoke files import from libs.vm? ==="
SMOKE_FILES=$(rg -rn "`@pytest.mark.smoke`" tests/ --type py -l)
for f in $SMOKE_FILES; do
  if rg -q "from libs\.vm|import libs\.vm" "$f" 2>/dev/null; then
    echo "SMOKE+LIBS.VM MATCH: $f"
    rg -n "from libs\.vm|import libs\.vm" "$f"
  fi
done
echo "Smoke libs.vm check done"

echo ""
echo "=== Conftest files along fedora_vm caller paths - libs.vm imports ==="
FEDORA_VM_FILES=$(rg -rn "fedora_vm\b" tests/ --type py -l)
for f in $FEDORA_VM_FILES; do
  dir=$(dirname "$f")
  while [ "$dir" != "." ] && [ "$dir" != "/" ]; do
    conftest="$dir/conftest.py"
    if [ -f "$conftest" ]; then
      if rg -q "from libs\.vm|import libs\.vm" "$conftest" 2>/dev/null; then
        echo "CONFTEST WITH LIBS.VM: $conftest (from caller: $f)"
      fi
    fi
    dir=$(dirname "$dir")
  done
done
echo "Conftest check done"

echo ""
echo "=== Check multiarch_excluded in current diff ==="
git diff origin/main...HEAD | grep -i "multiarch_excluded" || echo "NOT FOUND in diff"

echo ""
echo "=== PR changed files ==="
git diff origin/main...HEAD --name-only

Length of output: 8371


🏁 Script executed:

#!/bin/bash
echo "=== tests/network/localnet/conftest.py - libs.vm imports and fedora_vm usage ==="
rg -n "from libs\.vm|import libs\.vm|fedora_vm" tests/network/localnet/conftest.py

echo ""
echo "=== tests/network/localnet/liblocalnet.py - libs.vm imports and fedora_vm usage ==="
rg -n "from libs\.vm|import libs\.vm|fedora_vm" tests/network/localnet/liblocalnet.py

echo ""
echo "=== tests/virt/node/owner_references/test_vm_owner_references.py - gating + fedora_vm check ==="
rg -n "fedora_vm\|from libs\.vm\|import libs\.vm" tests/virt/node/owner_references/test_vm_owner_references.py | head -10

echo ""
echo "=== tests/virt/cluster/vm_cloning/test_vm_cloning.py - gating + fedora_vm check ==="
rg -n "fedora_vm\|from libs\.vm\|import libs\.vm" tests/virt/cluster/vm_cloning/test_vm_cloning.py | head -10

echo ""
echo "=== Conftest files in the directory hierarchy of gating fedora_vm callers ==="
# Check if tests/virt/node/owner_references/ or its ancestors have a conftest importing libs.vm.factory
for dir in "tests/virt/node/owner_references" "tests/virt/node" "tests/virt" "tests"; do
  conftest="$dir/conftest.py"
  if [ -f "$conftest" ]; then
    if rg -q "from libs\.vm\.factory\|from libs\.vm import factory\|fedora_image\|_fill_vm_spec_defaults" "$conftest" 2>/dev/null; then
      echo "FACTORY MATCH in conftest: $conftest"
    fi
    if rg -q "from libs\.vm|import libs\.vm" "$conftest" 2>/dev/null; then
      echo "LIBS.VM import in: $conftest"
      rg -n "from libs\.vm|import libs\.vm" "$conftest"
    fi
  fi
done

echo ""
echo "=== Confirm: does libs/vm/factory.py fedora_image change affect VMISpec.architecture? ==="
grep -n "architecture\|_fill_vm_spec_defaults\|fedora_image\|vmi_spec" libs/vm/factory.py | head -20

Length of output: 3577



Test Execution Plan

⚠️ Fallback — posted as a regular comment (sandbox lacks GH_TOKEN for inline review).
Applies to: libs/vm/factory.py, Line 4 (first changed line).


Run smoke tests: False

Verified: none of the 6 smoke-marked files reside under any conftest directory that imports libs.vm.factory or libs.vm.spec. The smoke test hierarchy (tests/virt/, tests/storage/, tests/install_upgrade_operators/, tests/infrastructure/) has no conftest with libs.vm.factory imports confirmed by full hierarchy scan.

Run gating tests: False

Dependency trace confirmed:

  • tests/network/localnet/conftest.py (covers gating test_default_bridge.py) imports libs.vm.spec for Interface, Multus, Network and libs.vm.oper/libs.vm.vmNOT libs.vm.factory. The new VMISpec.architecture field is additive (default None) and doesn't affect these symbols.
  • tests/network/kubemacpool/test_kubemacpool.py (gating) is at root level — not under explicit_range/conftest.py which is the conftest that imports libs.vm.factory.
  • tests/virt/cluster/vm_cloning/ and tests/virt/node/owner_references/ conftest hierarchy: no libs.vm.factory imports found.

Affected tests to run:

Path Reason
tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_vm_is_started_with_successful_connectivity Guest interface name read dynamically from vmi.interfaces[0].interfaceName; cloud-init key "eth0""primary"; fedora_image() now arch-aware via ArchImages; VM gets architecture set from py_config["cpu_arch"]
tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_ip_address_is_preserved_over_power_cycle Same logic changes as above

Both tests verified by the author on arm64 multi-arch, amd64 multi-arch, and homogeneous clusters — all passed.

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

I think the description contains outdated info (like excluded tests). Pls. reflect accordingly what has been done in the PR.

Comment thread tests/network/user_defined_network/ip_specification/test_ip_specification.py Outdated
Comment thread libs/vm/factory.py Outdated
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 16, 2026
@yossisegev

Copy link
Copy Markdown
Contributor Author

/verified

Verified by running the tests on 3 different setups, making sure the tests are passing and that the VM spec is created with the expected .architecture field.

  1. On multi arch-cluster: --tc-file=tests/global_config_arm64.py --cpu-arch=arm64: VM created with architecture: arm64
  2. On multi arch-cluster: --tc-file=tests/global_config_amd64.py --cpu-arch=amd64: VM created with architecture: amd64
  3. On multi homogenous cluster: No arch argument sent -> VM spec created without .specarchitecture`

@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/vm/factory.py
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
echo "=== PR changed files ==="
git diff origin/main...HEAD --name-only

echo ""
echo "=== First changed line info for libs/vm/factory.py ==="
git diff origin/main...HEAD -- libs/vm/factory.py | head -30

echo ""
echo "=== Modified symbols in libs/vm/factory.py ==="
git diff origin/main...HEAD --unified=0 -- libs/vm/factory.py | grep '^[+-][^+-]' | head -20

echo ""
echo "=== Smoke test files ==="
rg -rn "`@pytest.mark.smoke`" tests/ --type py -l

echo ""
echo "=== Gating test files ==="
rg -rn "`@pytest.mark.gating`" tests/ --type py -l

echo ""
echo "=== Direct callers of fedora_image in tests/ ==="
rg -rn "fedora_image\b" tests/ --type py -l

echo ""
echo "=== Same-file callers of _fill_vm_spec_defaults ==="
rg -n "_fill_vm_spec_defaults\|fedora_image" libs/vm/factory.py

echo ""
echo "=== Do smoke files import libs.vm? ==="
SMOKE_FILES=$(rg -rn "`@pytest.mark.smoke`" tests/ --type py -l)
for f in $SMOKE_FILES; do
  if rg -q "from libs\.vm|import libs\.vm" "$f" 2>/dev/null; then
    echo "SMOKE+LIBS.VM: $f"
  fi
done
echo "Smoke check done"

echo ""
echo "=== Do gating files import libs.vm? ==="
GATING_FILES=$(rg -rn "`@pytest.mark.gating`" tests/ --type py -l)
for f in $GATING_FILES; do
  if rg -q "from libs\.vm|import libs\.vm" "$f" 2>/dev/null; then
    echo "GATING+LIBS.VM: $f"
  fi
done
echo "Gating check done"

echo ""
echo "=== Get commit SHA for PR HEAD to use for inline comment ==="
git rev-parse HEAD

echo ""
echo "=== Get the exact line numbers changed in libs/vm/factory.py ==="
git diff origin/main...HEAD --unified=0 -- libs/vm/factory.py | grep "^@@"

echo ""
echo "=== libs/vm/factory.py diff ==="
git diff origin/main...HEAD -- libs/vm/factory.py

Length of output: 8995


🏁 Script executed:

#!/bin/bash
# Post inline review comment on libs/vm/factory.py line 4 (first changed line)
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/4810/reviews \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  --field event="COMMENT" \
  --field commit_id="5494c258197a8eca64a77a744c9893305cf2e02d" \
  --field body="" \
  --field "comments[][path]=libs/vm/factory.py" \
  --field "comments[][line]=4" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=**Test Execution Plan**

**Run smoke tests: False**
Verified: none of the 6 smoke-marked files (`tests/virt/node/general/test_container_disk_vm.py`, `tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py`, `tests/storage/cdi_upload/test_upload_virtctl.py`, `tests/install_upgrade_operators/csv/test_csv.py`, `tests/infrastructure/instance_types/supported_os/test_rhel_os.py`, `tests/storage/cdi_clone/test_clone.py`) import from \`libs.vm\`. No conftest in their directory hierarchy imports \`libs.vm.factory\` or \`libs.vm.spec\`.

**Run gating tests: False**
Verified: all 46 gating-marked files checked — none import from \`libs.vm\`. The \`_fill_vm_spec_defaults\` and \`fedora_image\` symbols have no direct or transitive callers in gating tests.

**Affected tests to run:**

| Path | Reason |
|---|---|
| \`tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_vm_is_started_with_successful_connectivity\` | Guest interface name read dynamically from \`vmi.interfaces[0].interfaceName\`; cloud-init key \`\"eth0\"\`\`\"primary\"\`; \`_fill_vm_spec_defaults\` now sets \`vmi_spec.architecture\` from \`py_config[\"cpu_arch\"]\` on MULTIARCH clusters |
| \`tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_ip_address_is_preserved_over_power_cycle\` | Same logic changes as above |

Both tests verified by the author across arm64 multi-arch, amd64 multi-arch, and homogeneous clusters — all passed."
echo "Exit code: $?"

Length of output: 4408



coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 16, 2026
Comment thread libs/vm/factory.py Outdated
@yossisegev

yossisegev commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

/verified

Verified by running the tests on 3 different setups, making sure the tests are passing and that the VM spec is created with the expected .architecture field.

  1. On multi arch-cluster: --tc-file=tests/global_config_arm64.py --cpu-arch=arm64: VM created with architecture: arm64
  2. On multi arch-cluster: --tc-file=tests/global_config_amd64.py --cpu-arch=amd64: VM created with architecture: amd64
  3. On homogeneous cluster: No arch argument sent -> VM spec created without .specarchitecture`

Add arcitecture support to VM specs.
 This change includes accessing `constants.Images` rather than importing
 `Images` at module level to ensure the updated Images on run-time is
 referenced.
Retrieve guest interface name dynamically

Signed-off-by: Yossi Segev <ysegev@redhat.com>
Assisted-by: Claude Code <noreply@anthropic.com>
@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"

@yossisegev

Copy link
Copy Markdown
Contributor Author

/verified

Verified by running the tests on 3 different setups, making sure the tests are passing and that the VM spec is created with the expected .architecture field.

  1. On multi arch-cluster: --tc-file=tests/global_config_arm64.py --cpu-arch=arm64: VM created with architecture: arm64
  2. On multi arch-cluster: --tc-file=tests/global_config_amd64.py --cpu-arch=amd64: VM created with architecture: amd64
  3. On homogeneous cluster: No arch argument sent -> VM spec created without .specarchitecture`

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Clean rebase detected — no code changes compared to previous head (3e7cb40).

Comment thread libs/vm/factory.py
@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
echo "=== Current HEAD SHA ==="
git rev-parse HEAD

echo ""
echo "=== First changed line in libs/vm/factory.py ==="
git diff origin/main...HEAD --unified=0 -- libs/vm/factory.py | grep "^@@" | head -3

echo ""
echo "=== PR changed files ==="
git diff origin/main...HEAD --name-only

echo ""
echo "=== Post inline review comment ==="
HEAD_SHA=$(git rev-parse HEAD)
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/4810/reviews \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  --field event="COMMENT" \
  --field commit_id="$HEAD_SHA" \
  --field body="" \
  --field "comments[][path]=libs/vm/factory.py" \
  --field "comments[][line]=4" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=**Test Execution Plan**

**Run smoke tests: False**
Verified: none of the 6 smoke-marked files (`tests/virt/node/general/test_container_disk_vm.py`, `tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py`, `tests/storage/cdi_upload/test_upload_virtctl.py`, `tests/install_upgrade_operators/csv/test_csv.py`, `tests/infrastructure/instance_types/supported_os/test_rhel_os.py`, `tests/storage/cdi_clone/test_clone.py`) import from \`libs.vm\`. Full hierarchy scan of conftest files in their directory chains confirmed no import of \`libs.vm.factory\` or \`libs.vm.spec\`.

**Run gating tests: False**
Verified: all gating-marked files checked — none import from \`libs.vm\`. The modified symbols (\`_fill_vm_spec_defaults\` arch defaulting logic, \`VMISpec.architecture\` field) have no direct or transitive callers in any gating test.

**Affected tests to run:**

| Path | Reason |
|---|---|
| \`tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_vm_is_started_with_successful_connectivity\` | Guest interface name read dynamically from \`vmi.interfaces[0].interfaceName\`; cloud-init key \`\"eth0\"\`\`\"primary\"\`; \`_fill_vm_spec_defaults\` sets \`vmi_spec.architecture\` from \`py_config[\"cpu_arch\"]\` on MULTIARCH clusters |
| \`tests/network/user_defined_network/ip_specification/test_ip_specification.py::TestVMWithExplicitIPAddressSpecification::test_ip_address_is_preserved_over_power_cycle\` | Same logic changes as above |

Both tests verified by the PR author on arm64 multi-arch, amd64 multi-arch, and homogeneous clusters — all passed."
echo "Exit code: $?"

Length of output: 5230



@rnetser

rnetser commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@rnetser

rnetser commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

smoke tests are not needed; override

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

Successfully removed PR tag: quay.io/openshift-cnv/openshift-virtualization-tests:pr-4810.

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

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

@yossisegev

Copy link
Copy Markdown
Contributor Author

/cherry-pick cnv-4.22

@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

Cherry-picked PR Net multi arch regression into cnv-4.22: #5267

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.