Skip to content

CherryPicked: [4.22] eus upgrade alignment#5168

Merged
rnetser merged 1 commit into
RedHatQE:cnv-4.22from
hmeir:4.22-eus-upgrade-update
Jun 17, 2026
Merged

CherryPicked: [4.22] eus upgrade alignment#5168
rnetser merged 1 commit into
RedHatQE:cnv-4.22from
hmeir:4.22-eus-upgrade-update

Conversation

@hmeir

@hmeir hmeir commented Jun 10, 2026

Copy link
Copy Markdown
Contributor
Short description:

Cherry-pick from #5055

More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:

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

Summary by CodeRabbit

  • New Features

    • EUS upgrades now require --cnv-version, --cnv-image, --cnv-channel, and --eus-ocp-images parameters.
    • Extended timeout for machine config pool updates to 180 minutes during upgrades.
  • Documentation

    • Clarified that EUS-to-EUS upgrades work only between even-numbered minor OpenShift versions.
    • Updated EUS upgrade procedures and parameter documentation.
  • Bug Fixes

    • Improved KubeVirt virtual machine migration validation with enhanced image tracking.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The PR removes the --eus-cnv-target-version CLI option and its associated fixtures, replacing them with channel-aware EUS upgrade path computation. Seven new helper functions build a version→image mapping for intermediate EUS hops. MCP timeout is now parameterizable. Virt-launcher upgrade validation switches from single-image to set-based multi-image comparison.

Changes

EUS Upgrade Orchestration Rework

Layer / File(s) Summary
MCP timeout parameter threading
utilities/operator.py, utilities/unittests/test_operator.py
wait_for_mcp_update_end and wait_for_mcp_update_completion each gain an optional timeout=TIMEOUT_75MIN parameter that is forwarded through the call chain; the unit test assertion is updated to expect timeout=4500.
CLI option removal and EUS upgrade validation
conftest.py, tox.ini
Removes --eus-cnv-target-version option, consolidates CNV/EUS enforcement into a shared block, adds an even-minor-version check for the EUS target using Version().minor % 2, and adds --cnv-image=NA --cnv-version=NA to the tox EUS collect-only command.
EUS target fixture removal and cnv_channel addition
tests/conftest.py
Removes eus_hco_target_csv_name and eus_target_cnv_version fixtures; adds cnv_channel session fixture returning pytestconfig.option.cnv_channel; adjusts packaging.version import to only parse.
Channel-aware EUS upgrade path computation utilities
tests/install_upgrade_operators/product_upgrade/utils.py
Adds Subscription import and EUS constant; introduces seven new functions (find_path_with_start_version, get_cnv_image_url_for_version, get_stable_released_builds, get_stable_channel_iib, build_version_images, find_intermediate_cnv_versions, build_eus_upgrade_path_dict); reparameterizes get_upgrade_path and get_build_info_by_version to accept channel; adds optional subscription parameters to perform_cnv_upgrade; wires TIMEOUT_180MIN into verify_upgrade_ocp.
EUS upgrade orchestration fixtures rewired
tests/install_upgrade_operators/product_upgrade/conftest.py
Rewrites eus_cnv_upgrade_path to validate odd minor-version source and delegate to build_eus_upgrade_path_dict; replaces masters with control_plane_nodes in OCP upgrade fixtures; replaces updated_cnv_subscription_source with cnv_subscription_scope_session/cnv_registry_source in CNV upgrade fixtures, iterating per-version build_info; applies TIMEOUT_180MIN to the worker MCP unpause step.
EUS upgrade test and docs cleanup
tests/install_upgrade_operators/product_upgrade/test_eus_upgrade.py, docs/INSTALL_AND_UPGRADE.md
Removes eus_target_cnv_version from test_eus_upgrade_process; renames eus_created_target_hco_csv to created_target_hco_csv; adds pytestmark for node taint/label fixtures; rewrites EUS upgrade docs with new parameter table and CLI examples.
Virt-launcher multi-image validation refactor
tests/virt/upgrade/utils.py, tests/virt/upgrade/conftest.py, tests/virt/upgrade/test_upgrade_virt.py
Renames get_virt_launcher_image_from_csvget_virt_launcher_images_from_csv returning set[str]; updates validate_vms_pod_updated to accept a set and use vm.vmi.virt_launcher_pod; adds virt_launcher_images_from_csv_before_upgrade fixture; removes eus_hco_target_csv_name fallback from csv_after_upgrade; swaps fixture name in TestUpgradeVirt.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

  • RedHatQE/openshift-virtualization-tests#5055: Directly overlaps with this PR — both modify --eus-cnv-target-version removal, EUS even-minor-version validation in pytest_cmdline_main, and NAMESPACE_COLLECTION iteration in conftest.py.

Suggested reviewers

  • kbidarkar
  • geetikakay
  • dshchedr
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'CherryPicked: [4.22] eus upgrade alignment' clearly describes the cherry-pick nature and main objective of the change, aligning EUS upgrade functionality for the 4.22 branch.
Description check ✅ Passed The PR description includes all required template sections: What this PR does, issue fixes, special notes, and a valid Jira ticket link (CNV-89570), though some sections are minimally filled.
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 newly added test files or test functions detected in this PR; only existing files were modified. Requirement satisfied.

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

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

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

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • OhadRevah
  • RoniKishner
  • SamAlber
  • akri3i
  • albarker-rh
  • dshchedr
  • geetikakay
  • hmeir
  • rlobillo
  • rnetser
  • vsibirsk
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.

Signed-off-by: Harel Meir <hmeir@redhat.com>
@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

/retest all

Auto-triggered: Files in this PR were modified by merged PR #5156.

Overlapping files

tests/conftest.py

@hmeir

hmeir commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

/verified

2026-06-15T14:13:47.300860 tests.install_upgrade_operators.product_upgrade.utils INFO Upgrade path for EUS-to-EUS upgrade: {'non-eus': {'4.21.8': {'cnv_image_url': 'registry-proxy.engineering.redhat.com/rh-osbs/iib:1149374', 'channel': 'stable'}}, 'eus': {'4.22.0': {'cnv_image_url': 'registry-proxy.engineering.redhat.com/rh-osbs/iib:1159577', 'channel': 'stable'}}}

@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 conftest.py
@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
set -euo pipefail

echo "=== PR Files Changed ==="
gh pr view 5168 --repo RedHatQE/openshift-virtualization-tests --json files --jq '.files[].path'

echo ""
echo "=== PR Diff ==="
gh pr diff 5168 --repo RedHatQE/openshift-virtualization-tests

Length of output: 36094


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== Smoke-marked test files ==="
rg -l '`@pytest.mark.smoke`' tests/

echo ""
echo "=== Gating-marked test files ==="
rg -l '`@pytest.mark.gating`' tests/

echo ""
echo "=== Direct callers of wait_for_mcp_update_completion in tests/ ==="
rg -rn 'wait_for_mcp_update_completion' tests/

echo ""
echo "=== Direct callers of wait_for_mcp_update_end in tests/ ==="
rg -rn 'wait_for_mcp_update_end' tests/

echo ""
echo "=== Callers of wait_for_mcp_update_completion in utilities/ ==="
rg -rn 'wait_for_mcp_update_completion' utilities/

echo ""
echo "=== Who imports eus_target_cnv_version (removed fixture) ==="
rg -rn 'eus_target_cnv_version' tests/

echo ""
echo "=== Who imports eus_hco_target_csv_name (removed fixture) ==="
rg -rn 'eus_hco_target_csv_name' tests/

echo ""
echo "=== Who imports get_virt_launcher_image_from_csv (renamed function) ==="
rg -rn 'get_virt_launcher_image_from_csv' tests/

echo ""
echo "=== Who uses virt_launcher_from_csv_before_upgrade fixture ==="
rg -rn 'virt_launcher_from_csv_before_upgrade' tests/

echo ""
echo "=== Who uses cnv_channel fixture ==="
rg -rn 'cnv_channel' tests/

echo ""
echo "=== Who calls validate_vms_pod_updated ==="
rg -rn 'validate_vms_pod_updated' tests/

echo ""
echo "=== EUS upgrade test file markers ==="
rg -n 'pytest.mark' tests/install_upgrade_operators/product_upgrade/test_eus_upgrade.py

echo ""
echo "=== Virt upgrade test file markers ==="
rg -n 'pytest.mark' tests/virt/upgrade/test_upgrade_virt.py | head -30

Length of output: 5567


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Get the PR details to find the commit SHA for inline comment
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5168 --jq '{head_sha: .head.sha, base_sha: .base.sha}'

echo ""
echo "=== List commits in PR ==="
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/5168/commits --jq '.[].sha'

Length of output: 561


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Post inline review comment on the first changed line of conftest.py (line 24, the added `from packaging.version import Version`)
gh api \
  --method POST \
  repos/RedHatQE/openshift-virtualization-tests/pulls/5168/reviews \
  --field commit_id="e220bea976cdefc37faa051e83f8881087e403e7" \
  --field event="COMMENT" \
  --field body="" \
  --field "comments[][path]=conftest.py" \
  --field "comments[][line]=24" \
  --field "comments[][side]=RIGHT" \
  --field "comments[][body]=## Test Execution Plan

**Run smoke tests: False**
No smoke-marked test file traces through the modified symbols (\`wait_for_mcp_update_completion\`, \`wait_for_mcp_update_end\`, EUS fixture chain). Smoke files (e.g. \`tests/install_upgrade_operators/csv/test_csv.py\`) do not call into upgrade-path utilities.

**Run gating tests: True**
\`tests/virt/upgrade/test_upgrade_virt.py\`\`virt_launcher_images_from_csv_before_upgrade\` fixture (renamed from \`virt_launcher_from_csv_before_upgrade\`) → \`get_virt_launcher_images_from_csv\` (changed from single image to set). This file carries \`@pytest.mark.gating\`.

**Affected tests to run**

- \`tests/install_upgrade_operators/product_upgrade/test_eus_upgrade.py\` — directly modified; EUS upgrade path completely refactored (\`eus_cnv_upgrade_path\` now calls \`build_eus_upgrade_path_dict\`, removed \`eus_target_cnv_version\`/\`eus_hco_target_csv_name\` fixtures, \`created_target_hco_csv\` replaces \`eus_created_target_hco_csv\`)
- \`tests/virt/upgrade/test_upgrade_virt.py\`\`virt_launcher_images_from_csv_before_upgrade\` fixture rename + \`csv_after_upgrade\` fixture no longer falls back to \`eus_hco_target_csv_name\` (gating)
- \`utilities/unittests/test_operator.py\` — unit test updated for \`wait_for_mcp_update_end\` new \`timeout\` default (already updated in this PR; run to confirm)

**Real tests (cluster required)**

\`pytest_cmdline_main\` now validates EUS args at session startup — must verify both paths on a real cluster:

Error path (odd minor version rejected):
\`\`\`
pytest --tc-file=tests/global_config.py --upgrade=eus --cnv-version=4.21.0 --cnv-image=NA --eus-ocp-images=NA,NA --collect-only
\`\`\`
Expected: \`ValueError: EUS target version 4.21.0 must have an even minor version\`

Happy path (even minor passes validation):
\`\`\`
pytest --tc-file=tests/global_config.py --upgrade=eus --cnv-version=4.22.0 --cnv-image=NA --eus-ocp-images=NA,NA --collect-only
\`\`\`
Expected: session starts normally, no ValueError

Full EUS upgrade suite:
\`\`\`
pytest -m eus_upgrade --upgrade eus --cnv-version <target_version> --cnv-image <cnv_image> --eus-ocp-images <4.y+1.z_image>,<4.y+2.z_image>
\`\`\`"

Length of output: 4486



@hmeir

hmeir commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@conftest.py`:
- Line 24: This PR has an unresolved review thread that is blocking merge.
Navigate to the pull request review comments and locate the unresolved
conversation thread. Address all feedback, concerns, or questions raised in that
thread by either making the requested code changes, providing clarification, or
reaching consensus with the reviewer. Once the conversation is fully addressed
and the thread is marked as resolved, the can-be-merged check should pass and
the PR can proceed to merge.

In `@tests/install_upgrade_operators/product_upgrade/utils.py`:
- Around line 656-668: The else block in the upgrade path handling is creating a
fallback direct upgrade to the intermediate version without validation when
find_path_with_start_version returns None. This bypasses the version-explorer
path validation and allows unsupported upgrade sequences to proceed. Remove the
else block that creates the fallback non_eus_images dictionary and instead raise
an exception or fail the operation when intermediate_step is None, ensuring that
only validated upgrade paths from GetUpgradePath are used.
🪄 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: 15c8923c-993a-4b12-939d-a2f4b5582dc4

📥 Commits

Reviewing files that changed from the base of the PR and between 3212888 and e220bea.

📒 Files selected for processing (12)
  • conftest.py
  • docs/INSTALL_AND_UPGRADE.md
  • tests/conftest.py
  • tests/install_upgrade_operators/product_upgrade/conftest.py
  • tests/install_upgrade_operators/product_upgrade/test_eus_upgrade.py
  • tests/install_upgrade_operators/product_upgrade/utils.py
  • tests/virt/upgrade/conftest.py
  • tests/virt/upgrade/test_upgrade_virt.py
  • tests/virt/upgrade/utils.py
  • tox.ini
  • utilities/operator.py
  • utilities/unittests/test_operator.py

Comment thread conftest.py
Comment thread tests/install_upgrade_operators/product_upgrade/utils.py
@hmeir

hmeir commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

/check-can-merge

@OhadRevah

Copy link
Copy Markdown
Contributor

/lgtm

@rnetser

rnetser commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

/approve

@rnetser

rnetser commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

/retest security-committer-identity

/retest security-suspicious-paths

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

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

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