Skip to content

refactor(virt): migrate virt to direct constants submodule imports#5318

Merged
dshchedr merged 4 commits into
RedHatQE:mainfrom
vsibirsk:vk-migrate-virt-imports
Jun 29, 2026
Merged

refactor(virt): migrate virt to direct constants submodule imports#5318
dshchedr merged 4 commits into
RedHatQE:mainfrom
vsibirsk:vk-migrate-virt-imports

Conversation

@vsibirsk

@vsibirsk vsibirsk commented Jun 23, 2026

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

Replace all from utilities.constants import X with from utilities.constants.<submodule> import X across 76 files in tests/virt/. Imports of Images are intentionally kept via from utilities.constants import Images (computed alias in init.py; pending circular-import cleanup in utilities/architecture.py).

Generated-by: Claude Sonnet 4.6

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

This is a next PR in a series.
https://redhat.atlassian.net/browse/CNV-80952 and a follow up of #5188

jira-ticket:

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

Summary by CodeRabbit

Release Notes

  • Refactor
    • Reorganized how test suite constants are imported by splitting a single aggregated constants source into more specific submodules (e.g., timeouts, images, platform/virt, networking).
    • Applied across various test files and fixtures; no test behavior or assertions were changed.

…orts

Replace all `from utilities.constants import X` with
`from utilities.constants.<submodule> import X` across 76 files in
tests/virt/. Imports of `Images` are intentionally kept via
`from utilities.constants import Images` (computed alias in __init__.py;
pending circular-import cleanup in utilities/architecture.py).

Generated-by: Claude Sonnet 4.6
Signed-off-by: vsibirsk <vsibirsk@redhat.com>
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d72f2f5c-a38c-4692-aa7a-5e029a8043ec

📥 Commits

Reviewing files that changed from the base of the PR and between 7209838 and cf972e1.

📒 Files selected for processing (1)
  • tests/virt/node/general/test_cloud_init_disk_vm.py
💤 Files with no reviewable changes (1)
  • tests/virt/node/general/test_cloud_init_disk_vm.py

📝 Walkthrough

Walkthrough

Imports across tests/virt/ now reference themed utilities.constants.* submodules instead of the aggregated utilities.constants module. Test logic, fixtures, and assertions remain unchanged.

Changes

Import path migration to utilities.constants submodules

Layer / File(s) Summary
Cluster test import updates
tests/virt/cluster/aaq/*, tests/virt/cluster/common_templates/..., tests/virt/cluster/longevity_tests/*, tests/virt/cluster/migration_and_maintenance/*, tests/virt/cluster/operator_tests/*, tests/virt/cluster/sysprep/*, tests/virt/cluster/vm_cloning/*, tests/virt/cluster/vm_lifecycle/*
Constants previously grouped under utilities.constants are split into submodule imports across the cluster-level test and utility files.
Node test import updates
tests/virt/conftest.py, tests/virt/node/conftest.py, tests/virt/node/descheduler/*, tests/virt/node/general/*, tests/virt/node/gpu/..., tests/virt/node/high_performance_vm/*, tests/virt/node/hotplug/*, tests/virt/node/hyperv_support/*, tests/virt/node/log_verbosity/*, tests/virt/node/migration_and_maintenance/*, tests/virt/node/node_labeller/..., tests/virt/node/readonly_disk/*, tests/virt/node/workload_density/*
The same import split is applied across node-level test and utility files, routing each constant to its dedicated submodule.
Upgrade and shared utils import updates
tests/virt/upgrade/conftest.py, tests/virt/upgrade/test_upgrade_virt.py, tests/virt/upgrade/utils.py, tests/virt/upgrade_custom/aaq/*, tests/virt/upgrade_custom/vgpu/conftest.py, tests/virt/utils.py
Upgrade-related conftest/test/utils files and tests/virt/utils.py update constant imports to the matching submodules.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • RoniKishner
  • OhadRevah
  • albarker-rh
  • dshchedr
  • rlobillo
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title is under 120 characters and clearly states the import-refactor across virt tests.
Description check ✅ Passed The description matches the template headings and includes the PR purpose, review notes, and Jira ticket.
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.
Stp Link Required ✅ Passed No new test_*.py files were added; the only new test methods are in test_connectivity.py, whose module docstring already includes an STP URL.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Linked repositories: Your configuration references 1 linked repositories, but your current plan allows 0. Analyzed ``, skipped RedHatQE/openshift-virtualization-tests-design-docs.


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

❤️ Share

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

@openshift-virtualization-qe-bot-6

Copy link
Copy Markdown

Report bugs in Issues

Welcome! 🎉

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

🔄 Automatic Actions

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

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (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:

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

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

💡 Tips

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

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

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@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/virt/node/workload_density/test_kernel_samepage_merging.py`:
- Around line 12-15: For this import-only refactor that changes imports from
utilities.constants.timeouts without modifying any test logic, validate the
changes by running uv run pytest --collect-only on the
test_kernel_samepage_merging.py module rather than executing the full test
suite. This collect-only approach is sufficient to verify that the import paths
are correctly resolved without the overhead of full test execution.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

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

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 52f6cd69-bc70-4cc7-97f5-5f2c4d04d3c2

📥 Commits

Reviewing files that changed from the base of the PR and between ce56f21 and 7209838.

📒 Files selected for processing (76)
  • tests/virt/cluster/aaq/conftest.py
  • tests/virt/cluster/aaq/constants.py
  • tests/virt/cluster/aaq/test_arq.py
  • tests/virt/cluster/aaq/utils.py
  • tests/virt/cluster/common_templates/centos/test_centos_os_support.py
  • tests/virt/cluster/common_templates/conftest.py
  • tests/virt/cluster/common_templates/custom_namespace/conftest.py
  • tests/virt/cluster/common_templates/custom_namespace/test_custom_namespace.py
  • tests/virt/cluster/common_templates/custom_namespace/utils.py
  • tests/virt/cluster/common_templates/fedora/test_fedora_os_support.py
  • tests/virt/cluster/common_templates/general/test_base_custom_templates.py
  • tests/virt/cluster/common_templates/general/test_base_template.py
  • tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py
  • tests/virt/cluster/common_templates/rhel/test_rhel_tablet_device.py
  • tests/virt/cluster/common_templates/utils.py
  • tests/virt/cluster/common_templates/windows/test_windows_custom_options.py
  • tests/virt/cluster/common_templates/windows/test_windows_os_support.py
  • tests/virt/cluster/common_templates/windows/test_windows_tablet_device.py
  • tests/virt/cluster/general/mass_machine_type_transition_tests/conftest.py
  • tests/virt/cluster/longevity_tests/constants.py
  • tests/virt/cluster/longevity_tests/utils.py
  • tests/virt/cluster/migration_and_maintenance/rbac_hardening/test_migration_rights.py
  • tests/virt/cluster/migration_and_maintenance/test_evictionstrategy.py
  • tests/virt/cluster/migration_and_maintenance/test_migration_policy.py
  • tests/virt/cluster/operator_tests/test_critical_pods.py
  • tests/virt/cluster/operator_tests/test_ssp_custom_resources.py
  • tests/virt/cluster/sysprep/test_sysprep.py
  • tests/virt/cluster/vm_cloning/conftest.py
  • tests/virt/cluster/vm_cloning/test_vm_cloning.py
  • tests/virt/cluster/vm_cloning/utils.py
  • tests/virt/cluster/vm_lifecycle/test_vm_data_persistency.py
  • tests/virt/cluster/vm_lifecycle/test_vm_run_strategy.py
  • tests/virt/conftest.py
  • tests/virt/node/conftest.py
  • tests/virt/node/descheduler/conftest.py
  • tests/virt/node/descheduler/test_descheduler_psi_metrics.py
  • tests/virt/node/descheduler/utils.py
  • tests/virt/node/general/test_cloud_init_disk_vm.py
  • tests/virt/node/general/test_cloud_init_vm.py
  • tests/virt/node/general/test_disk_io_option.py
  • tests/virt/node/general/test_machinetype.py
  • tests/virt/node/general/test_networkinterfacemultiqueue_feature.py
  • tests/virt/node/general/test_oom.py
  • tests/virt/node/general/test_static_ssh_key_injection.py
  • tests/virt/node/general/test_windows_vtpm_bitlocker.py
  • tests/virt/node/general/test_wsl2.py
  • tests/virt/node/gpu/conftest.py
  • tests/virt/node/gpu/gpu_pci_passthrough/conftest.py
  • tests/virt/node/gpu/gpu_pci_passthrough/test_rhel_vm_with_gpu_pci_passthrough.py
  • tests/virt/node/gpu/utils.py
  • tests/virt/node/high_performance_vm/test_numa.py
  • tests/virt/node/hotplug/test_cpu_memory_hotplug.py
  • tests/virt/node/hyperv_support/test_hyperv_features_in_vm.py
  • tests/virt/node/hyperv_support/test_windows_crash_detection.py
  • tests/virt/node/log_verbosity/test_log_verbosity.py
  • tests/virt/node/log_verbosity/test_log_virt_launcher.py
  • tests/virt/node/migration_and_maintenance/test_node_maintenance.py
  • tests/virt/node/migration_and_maintenance/test_odf_vm_migration.py
  • tests/virt/node/migration_and_maintenance/test_post_copy_migration.py
  • tests/virt/node/migration_and_maintenance/test_vm_disk_load_with_migration.py
  • tests/virt/node/migration_and_maintenance/test_vm_memory_load_with_migration.py
  • tests/virt/node/node_labeller/cpu_features/test_node_feature_discovery.py
  • tests/virt/node/node_labeller/cpu_features/test_vm_with_cpu_features.py
  • tests/virt/node/node_labeller/cpu_features/test_vm_with_cpu_flag.py
  • tests/virt/node/node_labeller/test_node_labeller_annotation.py
  • tests/virt/node/readonly_disk/test_vm_with_windows_guest_tools.py
  • tests/virt/node/workload_density/test_kernel_samepage_merging.py
  • tests/virt/node/workload_density/test_swap.py
  • tests/virt/upgrade/conftest.py
  • tests/virt/upgrade/test_upgrade_virt.py
  • tests/virt/upgrade/utils.py
  • tests/virt/upgrade_custom/aaq/conftest.py
  • tests/virt/upgrade_custom/aaq/constants.py
  • tests/virt/upgrade_custom/aaq/test_upgrade_virt_aaq.py
  • tests/virt/upgrade_custom/vgpu/conftest.py
  • tests/virt/utils.py

Comment thread tests/virt/node/workload_density/test_kernel_samepage_merging.py
@vsibirsk

Copy link
Copy Markdown
Collaborator Author

/verified

collect only since it's only import path updates (no logic change)

$ uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/virt --collect-only
...
================================================================================= 535/560 tests collected (25 deselected) in 1.35s =================================================================================

================================================================================= 535/560 tests collected (25 deselected) in 1.35s =================================================================================

@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/virt/cluster/aaq/conftest.py
@coderabbitai

coderabbitai Bot commented Jun 24, 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

PR_NUMBER=5318
REPO="RedHatQE/openshift-virtualization-tests"

# Get list of changed files to find the first one
gh pr diff "$PR_NUMBER" --repo "$REPO" --name-only | head -5

echo "---DIFF_HEADER---"
# Get the first changed file and its first changed line number
gh pr diff "$PR_NUMBER" --repo "$REPO" | head -60

Length of output: 3215


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Check for smoke markers in changed test files under tests/virt/
rg -l '`@pytest.mark.smoke`' tests/virt/ 2>/dev/null | head -20
echo "---GATING---"
rg -l '`@pytest.mark.gating`' tests/virt/ 2>/dev/null | head -20

Length of output: 1687


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PR_NUMBER=5318
REPO="RedHatQE/openshift-virtualization-tests"

# Get the list of changed files in this PR
CHANGED_FILES=$(gh pr diff "$PR_NUMBER" --repo "$REPO" --name-only)
echo "Changed files:"
echo "$CHANGED_FILES" | head -10

FIRST_FILE=$(echo "$CHANGED_FILES" | head -1)
echo "First file: $FIRST_FILE"

# Get the diff for the first file to find the first changed line number
gh pr diff "$PR_NUMBER" --repo "$REPO" -- "$FIRST_FILE" 2>/dev/null | head -30

Length of output: 1417


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PR_NUMBER=5318
REPO="RedHatQE/openshift-virtualization-tests"

# Check if test_container_disk_vm.py is in the PR changes
gh pr diff "$PR_NUMBER" --repo "$REPO" --name-only | grep -E "test_container_disk_vm|test_rhel_os_support" || echo "Not found in PR"

Length of output: 488


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PR_NUMBER=5318
REPO="RedHatQE/openshift-virtualization-tests"

# Get the commit SHA for the PR head (needed for inline comment)
HEAD_SHA=$(gh pr view "$PR_NUMBER" --repo "$REPO" --json headRefOid --jq '.headRefOid')
echo "Head SHA: $HEAD_SHA"

# Post a non-blocking inline review comment (COMMENT, not REQUEST_CHANGES or APPROVE)
# First changed line in tests/virt/cluster/aaq/conftest.py is position in diff
# The hunk is @@ -23,15 +23,19 @@ — first changed line ("+") is line 26 in the new file

gh api \
  --method POST \
  "/repos/${REPO}/pulls/${PR_NUMBER}/reviews" \
  --field commit_id="$HEAD_SHA" \
  --field event="COMMENT" \
  --field "comments[][path]=tests/virt/cluster/aaq/conftest.py" \
  --field "comments[][line]=26" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=## Test Execution Plan

**Run smoke tests: True**
Dependency path: \`tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py\` (smoke) → imports \`LINUX_STR\` directly changed from \`utilities.constants\` to \`utilities.constants.instance_types\` in this PR.

**Run gating tests: True**
Dependency paths (gating-marked files directly modified in this PR — import paths changed):
- \`tests/virt/upgrade/test_upgrade_virt.py\`
- \`tests/virt/cluster/vm_lifecycle/test_vm_run_strategy.py\`
- \`tests/virt/cluster/vm_cloning/test_vm_cloning.py\`
- \`tests/virt/cluster/migration_and_maintenance/test_migration_policy.py\`
- \`tests/virt/cluster/migration_and_maintenance/test_evictionstrategy.py\`
- \`tests/virt/node/node_labeller/cpu_features/test_vm_with_cpu_flag.py\`
- \`tests/virt/node/node_labeller/cpu_features/test_node_feature_discovery.py\`
- \`tests/virt/node/general/test_machinetype.py\`
- \`tests/virt/node/general/test_static_ssh_key_injection.py\`
- \`tests/virt/node/general/test_disk_io_option.py\`

**Affected tests to run**

All 76 modified files under \`tests/virt/\` have import-path-only changes (no logic). The PR author already validated collection succeeds:
\`\`\`
pytest tests/virt --collect-only  # 535/560 collected ✅
\`\`\`

Prioritized subset for runtime validation:

**Smoke (verify import resolution at runtime):**
- \`tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py\` (smoke)

**Gating (verify import resolution at runtime):**
- \`tests/virt/upgrade/test_upgrade_virt.py\` (gating)
- \`tests/virt/cluster/vm_lifecycle/test_vm_run_strategy.py\` (gating)
- \`tests/virt/cluster/vm_cloning/test_vm_cloning.py\` (gating)
- \`tests/virt/cluster/migration_and_maintenance/test_evictionstrategy.py\` (gating)
- \`tests/virt/node/general/test_machinetype.py\` (gating)

**Notes:**
- No \`utilities/\` or \`libs/\` files were modified — transitive fixture impact is nil.
- \`Images\` is intentionally kept at \`utilities.constants\` (computed alias in \`__init__.py\`); no action needed.
- \`--collect-only\` passed (535/560); collection errors from bad import paths would have surfaced there." \
  2>&1

Length of output: 4913



@openshift-virtualization-qe-bot-6

Copy link
Copy Markdown

Clean rebase detected — no code changes compared to previous head (ba6fa21).
The following labels were preserved: verified.

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Clean rebase detected — no code changes compared to previous head (cf972e1).
The following labels were preserved: verified, lgtm-coderabbitai[bot].

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

/retest tox
/retest build-container

@rnetser

rnetser commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@SamAlber

Copy link
Copy Markdown
Contributor

/lgtm

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

/retest tox

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

/retest tox

@dshchedr

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@dshchedr

Copy link
Copy Markdown
Collaborator

/retest tox

@dshchedr
dshchedr merged commit 47971f3 into RedHatQE:main Jun 29, 2026
22 checks passed
@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

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

@vsibirsk
vsibirsk deleted the vk-migrate-virt-imports branch June 30, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants