Skip to content

[IUO] Migrate install and EUS upgrade paths to Konflux IDMS#4070

Merged
rnetser merged 1 commit intoRedHatQE:mainfrom
rlobillo:CNV-81192
Mar 4, 2026
Merged

[IUO] Migrate install and EUS upgrade paths to Konflux IDMS#4070
rnetser merged 1 commit intoRedHatQE:mainfrom
rlobillo:CNV-81192

Conversation

@rlobillo
Copy link
Contributor

@rlobillo rlobillo commented Mar 4, 2026

Short description:

Move Konflux IDMS constants and functions (apply_konflux_idms, idms_has_all_mirrors) from product_upgrade/utils.py to shared utilities/operator.py. Replace legacy ICSP/IDMS fixtures in the install path with a new install_konflux_idms fixture, and replace EUS upgrade fixtures (created_eus_icsps, eus_applied_all_icsp) with eus_updated_konflux_idms. This aligns install and EUS paths with the Konflux migration done for upgrades in PR #4061.

More details:

Complements #4061

What this PR does / why we need it:

Fix the IDMS to use Konflux.

Which issue(s) this PR fixes:

N/A

Special notes for reviewer:

N/A

jira-ticket:

https://issues.redhat.com/browse/CNV-81192
https://issues.redhat.com/browse/CNV-81195

Summary by CodeRabbit

Release Notes

  • Tests

    • Modernized test infrastructure to use Konflux IDMS-based mirror management system.
    • Removed legacy mirror management test utilities.
  • Refactor

    • Reorganized utility functions and constants across test modules for improved fixture management and code maintainability.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 4, 2026

Warning

Rate limit exceeded

@rlobillo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 37 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2bb79e2c-23f9-44c8-b7c4-5189aefc3f92

📥 Commits

Reviewing files that changed from the base of the PR and between fa74be2 and d1c8fa2.

📒 Files selected for processing (4)
  • tests/install_upgrade_operators/product_install/conftest.py
  • tests/install_upgrade_operators/product_upgrade/conftest.py
  • tests/install_upgrade_operators/product_upgrade/utils.py
  • tests/install_upgrade_operators/utils.py
📝 Walkthrough

Walkthrough

This PR consolidates Konflux-based IDMS utilities into the main test utils module and refactors product install/upgrade configurations to use this Konflux workflow instead of ICSP-based IDMS generation. The migration removes duplicated code, updates fixture dependencies, and centralizes mirror management logic.

Changes

Cohort / File(s) Summary
Konflux IDMS Utilities Consolidation
tests/install_upgrade_operators/utils.py
Added KONFLUX_IDMS_NAME, KONFLUX_MIRROR_BASE_URL, KONFLUX_IDMS_SOURCE constants and two new functions: apply_konflux_idms() (creates/patches ImageDigestMirrorSet with pause/resume MCP logic) and idms_has_all_mirrors() (validates IDMS contains required mirrors). Includes necessary imports for ImageDigestMirrorSet, MachineConfigPool, Node, ResourceEditor, and wait_for_mcp_update_completion.
Product Install Configuration
tests/install_upgrade_operators/product_install/conftest.py
Replaced ICSP/IDMS generation logic with new installed_konflux_idms fixture that validates/applies Konflux mirrors. Updated installed_openshift_virtualization to depend on installed_konflux_idms instead of updated_icsp_hyperconverged. Removed old ICSP-related imports and constants.
Product Upgrade Configuration
tests/install_upgrade_operators/product_upgrade/conftest.py
Replaced created_eus_icsps and eus_applied_all_icsp with new eus_updated_konflux_idms fixture. Updated eus_paused_worker_mcp to depend on eus_updated_konflux_idms. Imported and integrated Konflux utilities (KONFLUX_IDMS_NAME, KONFLUX_MIRROR_BASE_URL, apply_konflux_idms, idms_has_all_mirrors).
Product Upgrade Utilities Cleanup
tests/install_upgrade_operators/product_upgrade/utils.py
Removed three Konflux constants (KONFLUX_IDMS_NAME, KONFLUX_MIRROR_BASE_URL, KONFLUX_IDMS_SOURCE), two functions (apply_konflux_idms, idms_has_all_mirrors), and related imports (ImageDigestMirrorSet, Node). Code migrated to centralized utils.py.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

The changes involve moderate complexity: moving and consolidating functions across modules requires verification of logic correctness and impact tracing, fixture dependency updates demand careful validation that the new flow maintains test isolation, and removal of duplicated code necessitates confirming all references are updated. However, the pattern is relatively consistent across files (Konflux utilities migration), reducing the cognitive load compared to heterogeneous changes.

Possibly related PRs

Suggested labels

commented-coderabbitai[bot]

Suggested reviewers

  • dshchedr
  • rnetser
  • vsibirsk
  • geetikakay
  • OhadRevah
🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 41.67% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title '[IUO] Migrate install and EUS upgrade paths to Konflux IDMS' accurately and concisely describes the main change: migrating multiple test fixtures and utilities to use Konflux IDMS instead of legacy ICSP/IDMS approaches.
Description check ✅ Passed The PR description includes all required template sections with substantive information: short description clearly states the change scope, detailed explanation of what moved and why, references complementary PR #4061, and provides two linked JIRA tickets.

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

✨ Finishing Touches
🧪 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

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

@openshift-virtualization-qe-bot-3
Copy link
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, conflict labels
  5. Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

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

@codecov
Copy link

codecov bot commented Mar 4, 2026

Codecov Report

❌ Patch coverage is 25.00000% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.98%. Comparing base (84584c3) to head (76a7686).
⚠️ Report is 54 commits behind head on main.

Files with missing lines Patch % Lines
utilities/operator.py 25.00% 15 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4070      +/-   ##
==========================================
- Coverage   98.56%   97.98%   -0.58%     
==========================================
  Files          25       25              
  Lines        2297     2388      +91     
==========================================
+ Hits         2264     2340      +76     
- Misses         33       48      +15     
Flag Coverage Δ
utilities 97.98% <25.00%> (-0.58%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@rlobillo
Copy link
Contributor Author

rlobillo commented Mar 4, 2026

/build-and-push-container

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

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 the current code and only fix it if needed.

Inline comments:
In `@tests/install_upgrade_operators/product_install/conftest.py`:
- Around line 64-90: Rename the fixture function install_konflux_idms to a
noun-based name (e.g., konflux_idms or installed_konflux_idms) while keeping the
`@pytest.fixture`(scope="module") decorator and all parameters the same; update
any tests or fixtures that reference install_konflux_idms to use the new name
(ensure the dependency injection that references this fixture is updated
accordingly), and leave the internal logic that computes required_mirrors,
checks idms.exists and calls apply_konflux_idms unchanged (references:
install_konflux_idms -> new fixture name; apply_konflux_idms,
ImageDigestMirrorSet, idms_has_all_mirrors keep as-is).

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: acd3198e-9149-4b3f-8a11-84584c16c17c

📥 Commits

Reviewing files that changed from the base of the PR and between 5a74c7f and 76a7686.

📒 Files selected for processing (4)
  • tests/install_upgrade_operators/product_install/conftest.py
  • tests/install_upgrade_operators/product_upgrade/conftest.py
  • tests/install_upgrade_operators/product_upgrade/utils.py
  • utilities/operator.py
💤 Files with no reviewable changes (1)
  • tests/install_upgrade_operators/product_upgrade/utils.py

@openshift-virtualization-qe-bot-2
Copy link
Contributor

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

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 the current code and only fix it if needed.

Inline comments:
In `@tests/install_upgrade_operators/product_upgrade/conftest.py`:
- Around line 416-422: The loop building required_mirrors manually checks
duplicates; replace that with a set to deduplicate: create a set (e.g.,
required_mirrors_set) and add each mirror computed from eus_cnv_upgrade_path
using Version and KONFLUX_MIRROR_BASE_URL, then convert the set back to a list
assigned to required_mirrors (or use a list(sorted(...)) if deterministic
ordering is needed). Update references to required_mirrors in this scope
accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2a021cbc-a761-4308-a952-ffb729555bcb

📥 Commits

Reviewing files that changed from the base of the PR and between 76a7686 and fa74be2.

📒 Files selected for processing (4)
  • tests/install_upgrade_operators/product_install/conftest.py
  • tests/install_upgrade_operators/product_upgrade/conftest.py
  • tests/install_upgrade_operators/product_upgrade/utils.py
  • tests/install_upgrade_operators/utils.py
💤 Files with no reviewable changes (1)
  • tests/install_upgrade_operators/product_upgrade/utils.py

CNV operator builds migrated from Brew to Konflux, so the install and
EUS upgrade test paths need Konflux IDMS instead of the legacy
ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from both install and EUS upgrade
conftest files, and replaces them with new Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms (product_upgrade/conftest.py)
- Upgrade path: add missing client param to updated_konflux_idms

Follows up on PR RedHatQE#4061 which fixed the upgrade path only.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rlobillo
Copy link
Contributor Author

rlobillo commented Mar 4, 2026

/verified

Tested install of 4.20.7 and then upgrading to 4.21.0:

$ oc get installplan,csv -n openshift-cnv && oc get idms/zz-cnv-icsp-fallback  -o yaml
NAME                                             CSV                                        APPROVAL    APPROVED
installplan.operators.coreos.com/install-4xd4p   kubevirt-hyperconverged-operator.v4.21.0   Manual      true
installplan.operators.coreos.com/install-wt4rx   kubevirt-hyperconverged-operator.v4.20.7   Automatic   true

NAME                                                                                  DISPLAY                    VERSION   RELEASE   REPLACES                                   PHASE
clusterserviceversion.operators.coreos.com/kubevirt-hyperconverged-operator.v4.21.0   OpenShift Virtualization   4.21.0              kubevirt-hyperconverged-operator.v4.20.7   Succeeded
apiVersion: config.openshift.io/v1
kind: ImageDigestMirrorSet
metadata:
  creationTimestamp: "2026-03-03T12:58:39Z"
  generation: 4
  name: zz-cnv-icsp-fallback
  resourceVersion: "1357040"
  uid: ee3a9c96-108e-4b18-9877-5d2937706b02
spec:
  imageDigestMirrors:
  - mirrors:
    - quay.io/openshift-virtualization/konflux-builds/v4-21
    - quay.io/openshift-virtualization/konflux-builds/v4-20
    source: registry.redhat.io/container-native-virtualization

@openshift-virtualization-qe-bot-3
Copy link
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 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

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 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
Copy link
Contributor

coderabbitai bot commented Mar 4, 2026

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get the list of changed files in the PR and their first changed lines
gh pr view 4070 --repo RedHatQE/openshift-virtualization-tests --json files --jq '.files[] | .path'

Length of output: 217


🏁 Script executed:

#!/bin/bash
# Get the diff to find first changed line of first file
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/4070/files --jq '.[0] | {filename: .filename, patch: .patch}'

Length of output: 5140


🏁 Script executed:

#!/bin/bash
# Find smoke tests and check if they depend on install/upgrade fixtures
rg "pytest.mark.smoke" --type=py -B2 | grep "def test_" | head -20

Length of output: 0


🏁 Script executed:

#!/bin/bash
# Check if smoke tests import or depend on install_upgrade_operators
rg "install_upgrade_operators|installed_konflux_idms|eus_updated_konflux_idms|apply_konflux_idms|idms_has_all_mirrors" --type=py -l

Length of output: 6056


🏁 Script executed:

#!/bin/bash
# Get PR head SHA and details needed for inline review
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/4070 --jq '{head_sha: .head.sha, base_sha: .base.sha}'

Length of output: 109


🏁 Script executed:

#!/bin/bash
# Check if there are any smoke tests in the repo at all
rg "pytest\.mark\.smoke" --type=py -l | head -10

Length of output: 456


🏁 Script executed:

#!/bin/bash
# Check if the smoke test in install_upgrade_operators uses any of the changed fixtures
rg "installed_konflux_idms|eus_updated_konflux_idms|apply_konflux_idms|idms_has_all_mirrors|updated_icsp_hyperconverged|installed_openshift_virtualization|eus_applied_all_icsp|created_eus_icsps" tests/install_upgrade_operators/csv/test_csv.py

Length of output: 0


🏁 Script executed:

#!/bin/bash
# Check what fixtures test_csv.py uses and how it's scoped
head -50 tests/install_upgrade_operators/csv/test_csv.py

Length of output: 1395


🏁 Script executed:

#!/bin/bash
# Post inline review comment with test execution plan
gh api repos/RedHatQE/openshift-virtualization-tests/pulls/4070/reviews \
  --method POST \
  --field commit_id="d1c8fa288f7a6d93ca452ce9ec86a3734796ec94" \
  --field event="COMMENT" \
  --field "comments[][path]=tests/install_upgrade_operators/product_install/conftest.py" \
  --field "comments[][position]=4" \
  --field "comments[][body]=## Test Execution Plan

**Run smoke tests: False**

No smoke test dependency path exists. The smoke test in \`tests/install_upgrade_operators/csv/test_csv.py\` uses only \`csv_scope_session\` and has no dependency on the changed install/EUS upgrade fixtures.

### Tests to run

- \`tests/install_upgrade_operators/product_install/test_install_openshift_virtualization.py\` — validates the new \`installed_konflux_idms\` fixture replacing the old ICSP/IDMS flow
- \`tests/install_upgrade_operators/product_upgrade/test_eus_upgrade.py\` — validates the new \`eus_updated_konflux_idms\` fixture replacing \`created_eus_icsps\`/\`eus_applied_all_icsp\`
- \`tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py\` — regression check for standard upgrade path"

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: 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: 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: 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: 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: 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: 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: 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: 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:54.623Z
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: 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: yossisegev
Repo: RedHatQE/openshift-virtualization-tests PR: 3873
File: tests/network/localnet/test_non_udn_localnet.py:7-9
Timestamp: 2026-02-25T10:52:23.378Z
Learning: In the RedHatQE/openshift-virtualization-tests repository, networking infrastructure requirements such as nmstate, localnet bridge mappings, and NIC availability are NOT considered special/platform-specific infrastructure that would warrant a tier3 marker. These are standard test environment capabilities in this repository's test environment, and tests requiring them do not automatically qualify as tier3 unless they involve other truly platform-specific/complex/time-consuming characteristics beyond standard network test infrastructure.

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: vsibirsk
Repo: RedHatQE/openshift-virtualization-tests PR: 2045
File: tests/virt/cluster/vm_lifecycle/conftest.py:46-47
Timestamp: 2025-09-15T06:49:53.478Z
Learning: In the openshift-virtualization-tests repo, large fixture refactoring efforts like the golden image data source migration are handled incrementally by directory/team ownership. The virt/cluster directory is handled separately from virt/node, tests/infra, tests/storage, etc., with each area managed by relevant teams in follow-up PRs.

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 the OS_FLAVOR attribute to the Images.Cirros class, making Images.Cirros.OS_FLAVOR available for conditional logic in tests.

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.

Learnt from: dshchedr
Repo: RedHatQE/openshift-virtualization-tests PR: 1716
File: tests/virt/conftest.py:289-297
Timestamp: 2025-08-09T01:52:26.683Z
Learning: When user dshchedr moves working code from one location to another in the openshift-virtualization-tests repository, they prefer not to modify it unless there's a real issue, maintaining the original implementation to avoid introducing unnecessary changes.

@albarker-rh
Copy link
Contributor

/lgtm

@rnetser
Copy link
Collaborator

rnetser commented Mar 4, 2026

/approve
/lgtm

@rnetser
Copy link
Collaborator

rnetser commented Mar 4, 2026

/check-can-merge

@rnetser rnetser merged commit efd31ab into RedHatQE:main Mar 4, 2026
22 of 23 checks passed
@openshift-virtualization-qe-bot-5

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

rnetser pushed a commit that referenced this pull request Mar 4, 2026
…lux IDMS (#4076)

Manual Cherry pick of
#4070 and
#4061

##### Short description:
CNV operator builds migrated from Brew to Konflux, so install, upgrade
and EUS upgrade test paths now require Konflux IDMS instead of the
legacy ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from install, upgrade and EUS upgrade
conftest files, and replaces them with Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- Upgrade path: updated_konflux_idms (product_upgrade/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms
(product_upgrade/conftest.py)

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

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
openshift-virtualization-qe-bot-5 pushed a commit that referenced this pull request Mar 4, 2026
…lux IDMS (#4076)

Manual Cherry pick of
#4070 and
#4061

##### Short description:
CNV operator builds migrated from Brew to Konflux, so install, upgrade
and EUS upgrade test paths now require Konflux IDMS instead of the
legacy ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from install, upgrade and EUS upgrade
conftest files, and replaces them with Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- Upgrade path: updated_konflux_idms (product_upgrade/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms
(product_upgrade/conftest.py)

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

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
openshift-virtualization-qe-bot-5 pushed a commit that referenced this pull request Mar 4, 2026
…lux IDMS (#4076)

Manual Cherry pick of
#4070 and
#4061

##### Short description:
CNV operator builds migrated from Brew to Konflux, so install, upgrade
and EUS upgrade test paths now require Konflux IDMS instead of the
legacy ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from install, upgrade and EUS upgrade
conftest files, and replaces them with Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- Upgrade path: updated_konflux_idms (product_upgrade/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms
(product_upgrade/conftest.py)

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

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-virtualization-qe-bot-5

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

rlobillo added a commit to rlobillo/openshift-virtualization-tests that referenced this pull request Mar 4, 2026
…lux IDMS

Manual Cherry pick of
RedHatQE#4070 and
RedHatQE#4061

CNV operator builds migrated from Brew to Konflux, so install, upgrade
and EUS upgrade test paths now require Konflux IDMS instead of the
legacy ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from install, upgrade and EUS upgrade
conftest files, and replaces them with Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- Upgrade path: updated_konflux_idms (product_upgrade/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms
(product_upgrade/conftest.py)

N/A
N/A
N/A
N/A
N/A

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
rlobillo added a commit to rlobillo/openshift-virtualization-tests that referenced this pull request Mar 4, 2026
…lux IDMS

Manual Cherry pick of
RedHatQE#4070 and
RedHatQE#4061

CNV operator builds migrated from Brew to Konflux, so install, upgrade
and EUS upgrade test paths now require Konflux IDMS instead of the
legacy ICSP/IDMS generated via `oc adm catalog mirror`.

This change consolidates Konflux IDMS helpers (apply_konflux_idms,
idms_has_all_mirrors) into tests/install_upgrade_operators/utils.py,
removes the legacy ICSP fixtures from install, upgrade and EUS upgrade
conftest files, and replaces them with Konflux-based fixtures:

- Install path: installed_konflux_idms (product_install/conftest.py)
- Upgrade path: updated_konflux_idms (product_upgrade/conftest.py)
- EUS upgrade path: eus_updated_konflux_idms (product_upgrade/conftest.py)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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.

8 participants