tests, net, udn: Introduce IP specification STD

[EdDev]

What this PR does / why we need it:

IP addresses specification on a VM

Tests are aimed to cover the ability to define at VM definition its primary UDN IP address.

STP Reference:
https://github.com/RedHatQE/openshift-virtualization-tests-design-docs/blob/main/stps/sig-network/ip-request.md

Which issue(s) this PR fixes:

Special notes for reviewer:

This STD has been written based on guidelines and examples introduced in #2881

jira-ticket:

Summary by CodeRabbit

• Tests
  • Added tests validating explicit VM IP assignment on user-defined networks: startup connectivity, external reachability, IP preservation across live migration, and retention through power cycles.
  • Added upgrade-suite test stubs (disabled) to verify IP persistence across cluster upgrades.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new test module with four explicit-IP UDN VM tests and extends the upgrade test suite with two disabled VM state-preservation tests for pre- and post-upgrade scenarios. All new tests are scaffolding with docstrings and Polarion markers; some are marked to not collect/run.

Changes

Cohort / File(s)	Summary
New explicit-IP UDN tests tests/network/user_defined_network/ip_specification/test_ip_specification.py	New test module adding TestVMWithExplicitIPAddressSpecification with four test methods: test_vm_is_started_with_successful_connectivity, test_successful_external_connectivity, test_seamless_in_cluster_connectivity_is_preserved_over_live_migration, test_ip_address_is_preserved_over_power_lifecycle. Tests include docstrings and Polarion IDs; module sets __test__ = False to avoid collection in some contexts.
Upgrade-suite VM state tests (disabled) tests/network/upgrade/test_upgrade_network.py	Added two test stubs test_udn_vm_state_before_upgrade and test_udn_vm_state_after_upgrade in TestUpgradeNetwork. Both verify IP preservation for a VM with a primary UDN network across upgrade phases but are marked disabled (__test__ = False) and act as documented scaffolding.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dshchedr
• vsibirsk
• rlobillo
• RoniKishner
• hmeir
• azhivovk
• rnetser
• servolkov
• yossisegev

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description covers the key sections (what it does, STP reference, special notes) but lacks required fields like short description, more details, issue fixes, and jira-ticket details.	Complete the missing template sections: add a short description, expand 'more details', specify which issues are fixed, and provide the Jira ticket URL or explicitly state 'NONE'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: introducing a new IP specification STD (Standard Test Design) for UDN networking.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-virtualization-qe-bot-5]

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 (optional)
• /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, conflict labels
5. Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

• EdDev

Reviewers:

• Anatw
• EdDev
• azhivovk
• servolkov
• yossisegev

Available Labels

• hold
• verified
• wip
• lgtm
• approve

💡 Tips

• WIP Status: Use /wip when your PR is not ready for review
• Verification: The verified label is automatically removed on each new commit
• 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.

[openshift-virtualization-qe-bot]

D/S test tox -e verify-tc-requirement-polarion failed: cnv-tests-tox-executor/24439

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In
`@tests/network/user_defined_network/ip_specification/test_ip_specification.py`:
- Around line 31-118: The module is disabled with __test__ = False and the test
functions (e.g., test_vm_is_started_with_successful_connectivity,
test_successful_external_connectivity,
test_seamless_in_cluster_connectivity_is_preserved_over_live_migration,
test_ip_address_is_preserved_over_power_lifecycle,
test_ip_address_is_preserved_over_upgrade) contain only docstrings so enabling
the module will produce failing/empty tests; either implement each test body
according to its docstring (set IP via annotation/cloud-init,
start/restart/migrate as needed, assert VMI.status IP equals the configured IP
and guest OS sees the same IP, and verify TCP/ping connectivity from the
reference VM) or, if not ready, replace each empty body with pytest.skip("TODO:
implement explicit IP verification and connectivity checks") and only remove
__test__ = False after full implementations are added.
- Line 10: Remove the collection-blocking line "__test__ = False" from the
module so pytest can discover the tests; for each of the five test functions in
tests/network/user_defined_network/ip_specification/test_ip_specification.py,
replace the docstring-only bodies with real assertions that implement the
described checks (translate the steps in each docstring into assert statements
and any necessary setup/teardown); add the appropriate pytest markers as
decorators (e.g., `@pytest.mark.ipv4`, `@pytest.mark.single_nic`,
`@pytest.mark.incremental`) above each test function to match the markers listed
in the docstrings and pytest.ini so tests are selectable and run.
- Around line 15-23: Remove or set the module-level __test__ = False to allow
pytest to collect tests (either delete the line or change it to __test__ =
True), and add pytest markers to the test class or its test methods by
decorating TestVMWithExplicitIPAddressSpecification with `@pytest.mark.ipv4`,
`@pytest.mark.single_nic`, and `@pytest.mark.incremental` so the tests can be
selected by the repository's marker-based test runs; ensure the pytest import is
present if not already.

[openshift-virtualization-qe-bot]

D/S test tox -e verify-tc-requirement-polarion failed: cnv-tests-tox-executor/24560

[yossisegev]

/retest tox

[yossisegev]

/retest all

[EdDev]

Verification:

uv run pytest --collect-only --skip-deprecated-api-test --cluster-sanity-skip-storage-check ./tests/network/user_defined_network/ip_specification/

Result: collected 1 item / 1 deselected / 0 selected

/verified

[openshift-virtualization-qe-bot-3]

@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 Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

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, and fixture inheritance
5. Detect new tests introduced in the PR
6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
   • Changes to files/functions used by tests marked with @pytest.mark.smoke
   • Changes to fixtures or utilities imported by smoke tests
   • Changes to conftest.py files that may affect smoke test execution
   • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

• Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
• 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 specific marker(s) can be used to cover multiple cases.

Guidelines:

• Include only tests directly affected by the changes
• Use a full file path only if ALL tests in that file require verification
• Use file path + test name if only specific tests are needed
• If a test marker can cover multiple files/tests, provide the marker
• Balance coverage vs over-testing - Keep descriptions minimal

CRITICAL WORKFLOW COMPLETION RULES:

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

1. YOUR ONLY DELIVERABLE: Post an inline review 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 submitting the review fails 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: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

[coderabbitai]

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# Find all files changed in this PR to determine order
echo "=== Files changed in PR ==="
git diff --name-only origin/main...HEAD | sort

echo -e "\n=== Check if any smoke tests exist in network directories ==="
rg "pytest\.mark\.smoke" tests/network/ -n --type=py -C2 || echo "No smoke tests found in network/"

echo -e "\n=== Verify the new test file has __test__ = False ==="
if [ -f "tests/network/user_defined_network/ip_specification/test_ip_specification.py" ]; then
    grep "__test__" tests/network/user_defined_network/ip_specification/test_ip_specification.py
else
    echo "File not found"
fi

echo -e "\n=== Check upgrade test file changes ==="
if [ -f "tests/network/upgrade/test_upgrade_network.py" ]; then
    grep "__test__" tests/network/upgrade/test_upgrade_network.py | head -5
else
    echo "File not found"
fi

echo -e "\n=== Verify no imports from these files in smoke tests ==="
rg "from.*ip_specification" tests/ --type=py || echo "No imports of ip_specification found"
rg "from.*test_upgrade_network" tests/ --type=py -C1 | grep -i smoke || echo "No smoke test imports of test_upgrade_network found"

Length of output: 678

---

🏁 Script executed:

#!/bin/bash

# Get the PR number and repo details
PR_NUMBER=3612
REPO="RedHatQE/openshift-virtualization-tests"

# Get the commit SHA for the latest commit in this PR
COMMIT_SHA=$(git rev-parse HEAD)

# Find the first changed line in the first file (tests/network/upgrade/test_upgrade_network.py)
FIRST_FILE="tests/network/upgrade/test_upgrade_network.py"

# Get the diff to find the first added line
git diff origin/main...HEAD -- "$FIRST_FILE" | head -30

echo -e "\n=== Preparing inline review comment ==="

# Create the test execution plan comment
COMMENT_BODY="**Test Execution Plan**

- **Run smoke tests: False**

**Rationale:**
- This PR introduces STD (Standard Test Definition) for IP specification on VMs with \`__test__ = False\` markers
- No functional code changes - only test structure definitions
- No smoke tests in network directories depend on these changes
- Per STD workflow (learning e27e059d), collection verification is sufficient until implementation PR
- PR author already verified collection: \`collected 1 item / 1 deselected / 0 selected\`

**Verification:**
\`\`\`bash
pytest --collect-only tests/network/user_defined_network/ip_specification/
pytest --collect-only tests/network/upgrade/test_upgrade_network.py
\`\`\`

Expected: Tests marked with \`__test__ = False\` are deselected until implementation phase."

# Find the first added line number (position in the new file)
# The first additions are test_udn_vm_state_before_upgrade
FIRST_LINE_IN_NEW_FILE=$(git diff origin/main...HEAD -- "$FIRST_FILE" | grep "^@@" | head -1 | sed 's/.*+\([0-9]*\).*/\1/')

echo "First line in new file: $FIRST_LINE_IN_NEW_FILE"
echo "Commit SHA: $COMMIT_SHA"
echo "File: $FIRST_FILE"

# Post the inline review comment using GitHub API
gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  "/repos/$REPO/pulls/$PR_NUMBER/reviews" \
  -f body="" \
  -f event="COMMENT" \
  -f commit_id="$COMMIT_SHA" \
  -f comments[][path]="$FIRST_FILE" \
  -f comments[][position]=1 \
  -f comments[][body]="$COMMENT_BODY"

Length of output: 1654

---

🏁 Script executed:

#!/bin/bash

PR_NUMBER=3612
REPO="RedHatQE/openshift-virtualization-tests"
COMMIT_SHA=$(git rev-parse HEAD)
FIRST_FILE="tests/network/upgrade/test_upgrade_network.py"

COMMENT_BODY="**Test Execution Plan**

- **Run smoke tests: False**

**Rationale:**
- This PR introduces STD (Standard Test Definition) for IP specification on VMs with \`__test__ = False\` markers
- No functional code changes - only test structure definitions
- No smoke tests in network directories depend on these changes
- Per STD workflow, collection verification is sufficient until implementation PR
- PR author already verified collection: \`collected 1 item / 1 deselected / 0 selected\`

**Verification:**
\`\`\`bash
pytest --collect-only tests/network/user_defined_network/ip_specification/
pytest --collect-only tests/network/upgrade/test_upgrade_network.py
\`\`\`

Expected: Tests marked with \`__test__ = False\` are deselected until implementation phase."

# Try using line parameter instead of position (for multi-line reviews on specific line)
# Line 120 is the first added line (`@pytest.mark.polarion`("CNV-13118"))
gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  "/repos/$REPO/pulls/$PR_NUMBER/reviews" \
  -f event="COMMENT" \
  -f commit_id="$COMMIT_SHA" \
  -F comments[][path]="$FIRST_FILE" \
  -F comments[][line]=120 \
  -F comments[][side]="RIGHT" \
  -F comments[][body]="$COMMENT_BODY"

Length of output: 1735

---

---

🧠 Learnings used

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

---

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

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3062
File: conftest.py:333-333
Timestamp: 2025-12-16T20:11:03.645Z
Learning: In the openshift-virtualization-tests repository, when determining smoke test impact for changes affecting py_config["os_login_param"], follow this verification methodology: (1) Find all smoke tests: `rg "pytest.mark.smoke" --type=py -B2 | grep "def test_"`, (2) For each smoke test file, search for VM creation patterns: `rg "VirtualMachineForTests|running_vm|VirtualMachineForTestsFromTemplate|wait_for_ssh|check_ssh_connectivity"`, (3) Trace the dependency chain: smoke test → VirtualMachineForTests/running_vm() → wait_for_ssh_connectivity() (default enabled) → vm.login_params property → py_config["os_login_param"][vm.os_flavor], (4) Check utilities/virt.py for login_params usage: `rg "os_login_param|login_params" utilities/virt.py -C3`. Any smoke test creating VMs with default SSH connectivity checks (running_vm with check_ssh_connectivity=True) depends on os_login_param, even if the test doesn't directly reference it.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-09-29T19:05:24.987Z
Learning: For PR `#1904` test execution, the critical validation point is test_connectivity_over_migration_between_localnet_vms which should fail gracefully on cloud clusters but pass on bare-metal/PSI clusters, representing the core nmstate conditional logic functionality.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 1904
File: tests/network/conftest.py:348-362
Timestamp: 2025-10-27T15:30:06.412Z
Learning: In tests/network/conftest.py, the _verify_nmstate_running_pods function currently runs unconditionally in network_sanity, but rnetser plans to implement marker-based conditional checking (following the pattern of _verify_dpdk, _verify_sriov, etc.) in a future PR after adding nmstate markers to the relevant tests.

---

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

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3062
File: conftest.py:333-333
Timestamp: 2025-12-16T15:09:49.597Z
Learning: In the openshift-virtualization-tests repository, when conftest.py or utilities/bitwarden.py changes affect py_config["os_login_param"], smoke test impact must be determined by: (1) finding all smoke tests using `rg "pytest.mark.smoke"`, (2) checking each for VM creation patterns (VirtualMachineForTests, running_vm, VirtualMachineForTestsFromTemplate), (3) tracing whether running_vm is called with default check_ssh_connectivity=True, which accesses vm.login_params property that reads py_config["os_login_param"][vm.os_flavor]. The dependency chain is: smoke test → VM creation → running_vm → wait_for_ssh_connectivity → vm.login_params → os_login_param. Any smoke test creating VMs with SSH connectivity (the default) depends on os_login_param.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-09-29T19:05:24.987Z
Learning: The test execution plan for PR `#1904` focuses on cluster-type conditional logic where nmstate functionality is bypassed on cloud clusters (Azure/AWS) but fully functional on bare-metal/PSI clusters, requiring different test strategies for each environment type.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 2469
File: utilities/sanity.py:139-142
Timestamp: 2025-11-08T07:36:57.616Z
Learning: In the openshift-virtualization-tests repository, user rnetser prefers to keep refactoring PRs (like PR `#2469`) strictly focused on moving/organizing code into more granular modules without adding new functionality, error handling, or behavioral changes. Such improvements should be handled in separate PRs.

---

Learnt from: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 3358
File: tests/network/sriov/test_sriov.py:21-21
Timestamp: 2026-01-07T09:52:22.771Z
Learning: For PRs that only remove or modify pytest markers (like removing pytest.mark.post_upgrade) without changing test logic in openshift-virtualization-tests, collection verification using `pytest --collect-only` is sufficient. Full test execution is not required to verify marker-only changes.

---

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

---

Learnt from: EdDev
Repo: RedHatQE/openshift-virtualization-tests PR: 3612
File: tests/network/user_defined_network/ip_specification/test_ip_specification.py:10-10
Timestamp: 2026-01-26T20:29:46.464Z
Learning: In the RedHatQE/openshift-virtualization-tests repository, when introducing STD (Standard Test Definition) PRs that define test case structure without implementation, it's acceptable and intentional to use `__test__ = False` to block pytest collection until the tests are fully implemented in a follow-up PR. The STD workflow involves: (1) defining test structure, markers, and documentation first, (2) implementing the actual test logic and removing the collection blocker in a subsequent PR.

---

Learnt from: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 3196
File: tests/network/upgrade/test_upgrade_network.py:4-4
Timestamp: 2025-12-22T16:27:44.327Z
Learning: For PRs that remove test cases (especially redundant test cleanup PRs in openshift-virtualization-tests), test collection verification (pytest --collect-only showing selected/deselected counts) is sufficient to confirm the removal was clean and the test module remains functional. Full test execution is not required for test deletion PRs.

---

Learnt from: servolkov
Repo: RedHatQE/openshift-virtualization-tests PR: 1776
File: libs/net/node_network.py:25-31
Timestamp: 2025-08-20T23:43:28.117Z
Learning: In the RedHatQE/openshift-virtualization-tests project, servolkov's team always uses bare metal (BM) clusters with IPv4 setup in their testing environment, making defensive checks for IPv4 data presence potentially redundant in their networking code.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3371
File: scripts/tests_analyzer/compare_coderabbit_decisions.py:199-289
Timestamp: 2026-01-13T10:06:14.822Z
Learning: In the openshift-virtualization-tests repository, user rnetser prefers to keep pagination loops inline rather than extracting them into generic helper functions when the loops have different URL patterns and unique post-processing logic, as the inline approach improves readability and makes each endpoint's behavior more explicit.

---

Learnt from: rnetser
Repo: RedHatQE/openshift-virtualization-tests PR: 3228
File: .coderabbit.yaml:30-41
Timestamp: 2026-01-05T10:33:55.037Z
Learning: In the openshift-virtualization-tests repository, user rnetser prefers minimal pre-merge checks in CodeRabbit configuration: only docstrings enforcement (80% threshold) is needed, not title or description checks.

---

Learnt from: jpeimer
Repo: RedHatQE/openshift-virtualization-tests PR: 1160
File: tests/storage/storage_migration/test_mtc_storage_class_migration.py:165-176
Timestamp: 2025-06-17T07:45:37.776Z
Learning: In the openshift-virtualization-tests repository, user jpeimer prefers explicit fixture parameters over composite fixtures in test methods, even when there are many parameters, as they find this approach more readable and maintainable for understanding test dependencies.

---

Learnt from: jpeimer
Repo: RedHatQE/openshift-virtualization-tests PR: 3571
File: tests/storage/storage_migration/utils.py:158-167
Timestamp: 2026-01-25T13:18:26.819Z
Learning: In the openshift-virtualization-tests repository, user jpeimer prefers to avoid nitpicky style changes (e.g., removing `.keys()` from dict membership checks) because verifying every change is expensive. Be cautious about suggesting low-impact stylistic improvements that require verification overhead.

---

Learnt from: akri3i
Repo: RedHatQE/openshift-virtualization-tests PR: 1210
File: tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py:24-64
Timestamp: 2025-06-23T19:28:20.281Z
Learning: In OpenShift Virtualization mass machine type transition tests, the machine type glob pattern "pc-q35-rhel8.*.*" is intentionally hard-coded in the kubevirt_api_lifecycle_automation_job as it's used only once for this specific test case, with plans to update it in the future if the job needs to support other machine types.

---

Learnt from: RoniKishner
Repo: RedHatQE/openshift-virtualization-tests PR: 1411
File: utilities/os_utils.py:246-279
Timestamp: 2025-07-22T17:13:59.166Z
Learning: In the RedHatQE/openshift-virtualization-tests repository, CentOS preferences follow the format "centos-stream<version>" (e.g., "centos-stream9", "centos-stream10"). The generate_instance_type_centos_os_matrix function correctly uses regex to extract numeric versions and constructs the latest version string in the same format as the input preferences for proper comparison.

---

Learnt from: akri3i
Repo: RedHatQE/openshift-virtualization-tests PR: 1210
File: tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py:83-97
Timestamp: 2025-06-23T19:19:31.961Z
Learning: In OpenShift Virtualization mass machine type transition tests, the kubevirt_api_lifecycle_automation_job requires cluster-admin privileges to function properly, as confirmed by the test maintainer akri3i.

---

Learnt from: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 0
File: :0-0
Timestamp: 2025-12-07T14:51:53.484Z
Learning: In the openshift-virtualization-tests repository, the team has decided to avoid using predefined time constants (like TIMEOUT_2MIN, TIMEOUT_5SEC) and prefers using explicit numeric values for timeout parameters.

---

Learnt from: vamsikrishna-siddu
Repo: RedHatQE/openshift-virtualization-tests PR: 2199
File: tests/storage/test_online_resize.py:108-113
Timestamp: 2025-09-28T14:43:07.181Z
Learning: In the openshift-virtualization-tests repo, PR `#2199` depends on PR `#2139` which adds architecture-specific OS_FLAVOR attributes to the Images.Cirros class (OS_FLAVOR_CIRROS for x86_64/ARM64, OS_FLAVOR_FEDORA for s390x), enabling conditional logic based on the underlying OS flavor in tests.

[rnetser]

/approve
/lgtm

[openshift-virtualization-qe-bot-4]

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