Skip to content

[4.20] Add OCS to AWS global config#5482

Open
jpeimer wants to merge 1 commit into
RedHatQE:cnv-4.20from
jpeimer:420_aws_global_config_ocs
Open

[4.20] Add OCS to AWS global config#5482
jpeimer wants to merge 1 commit into
RedHatQE:cnv-4.20from
jpeimer:420_aws_global_config_ocs

Conversation

@jpeimer

@jpeimer jpeimer commented Jul 2, 2026

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

Add CEPH_RBD_VIRTUALIZATION entry, move default flag from TRIDENT_CSI_FSX to IO2_CSI to align with main.

Assisted-by: Claude noreply@anthropic.com

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

Add CEPH_RBD_VIRTUALIZATION entry, move default flag from
TRIDENT_CSI_FSX to IO2_CSI to align with main.

Assisted-by: Claude <noreply@anthropic.com>
Signed-off-by: Jenia Peimer <jpeimer@redhat.com>
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e1cbb167-0387-4624-a670-2144462ab947

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

❤️ Share

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

@openshift-virtualization-qe-bot-4

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

Custom Commands

  • /test-plan - Triggers CodeRabbit to analyze the PR's changed files and post a test execution plan
  • /rerun-smoke - Adds `retest-smoke` label on the PR to trigger smoke tests exectuion

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
  • dshchedr
  • 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.

@jpeimer

jpeimer commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

/verified

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

Images.Windows.DEFAULT_DV_SIZE = "75Gi"

storage_class_matrix = [
{

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.

Test Execution Plan

  • Run smoke tests: Falsetests/global_config_aws.py is a pytest_testconfig data file loaded only when tests are executed with the AWS-specific --tc-file option; it is not imported by tests/conftest.py or any autouse fixture by default, so no smoke-marked test is exercised through the standard collection path.
  • Run gating tests: False — No gating-marked test imports this file or the changed symbols (CEPH_RBD_VIRTUALIZATION, IO2_CSI, TRIDENT_CSI_FSX) directly; impact is limited to the AWS storage-class matrix used only when this config is explicitly selected.
  • Affected tests to run (only when executed against the AWS config, i.e. with --tc-file=tests/global_config_aws.py or equivalent AWS job config):
    • -m storage (any test consuming the storage_class_matrix fixture, e.g. tests/storage/test_wffc.py, tests/storage/test_hotplug.py, tests/storage/cdi_clone/, tests/storage/cdi_import/, tests/storage/cdi_upload/, tests/storage/snapshots/) — new CEPH_RBD_VIRTUALIZATION entry adds a new matrix parametrization, and moving default: True from TRIDENT_CSI_FSX to IO2_CSI changes which storage class is used for non-matrixed/default-storage-class tests.
    • Any test using storage_class_a / storage_class_b (both now resolve to IO2_CSI, unchanged) — low risk, verify no regression.

Real tests (cluster required, AWS)
Happy path (regression, default storage class now IO2_CSI):
pytest tests/storage/test_wffc.py --tc-file=tests/global_config_aws.py --collect-only
Expected: collection succeeds, IO2_CSI used as default storage class, TRIDENT_CSI_FSX matrix entry still present without default flag.

New entry sanity check (CEPH_RBD_VIRTUALIZATION):
pytest tests/storage/test_hotplug.py --tc-file=tests/global_config_aws.py -k ceph_rbd_virtualization
Expected: new storage-class matrix entry is picked up and tests run/skip appropriately based on cluster storage-class availability.

@coderabbitai

coderabbitai Bot commented Jul 2, 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
gh pr view 5482 --repo RedHatQE/openshift-virtualization-tests --json files,title,body -q '.files[].path'
echo "---DIFF---"
gh pr diff 5482 --repo RedHatQE/openshift-virtualization-tests

Length of output: 1388


🏁 Script executed:

#!/bin/bash
set -euo pipefail
echo "== storage_class_matrix usage =="
rg -l 'storage_class_matrix' tests/ | head -30
echo "== StorageClassNames.CEPH_RBD_VIRTUALIZATION =="
rg -n 'CEPH_RBD_VIRTUALIZATION' -r ''  --hidden -g '!*.pyc' . | head -30
echo "== IO2_CSI / TRIDENT_CSI_FSX =="
rg -n 'IO2_CSI|TRIDENT_CSI_FSX' . | head -30
echo "== storage_class_matrix fixture definition =="
rg -n 'def storage_class_matrix' -A 15 tests/ | head -60
echo "== smoke marker in storage tests =="
rg -l '`@pytest.mark.smoke`' tests/storage/ | head -30
echo "== gating marker in storage tests =="
rg -l '`@pytest.mark.gating`' tests/storage/ | head -30

Length of output: 4765


🏁 Script executed:

#!/bin/bash
set -euo pipefail
cat -n tests/global_config_aws.py | sed -n '1,60p'

Length of output: 2342


🏁 Script executed:

#!/bin/bash
set -euo pipefail
gh pr view 5482 --repo RedHatQE/openshift-virtualization-tests --json headRefOid -q '.headRefOid'

Length of output: 307


🏁 Script executed:

#!/bin/bash
set -euo pipefail

REPO="RedHatQE/openshift-virtualization-tests"
PR=5482
SHA="e1000a01aa27f9573d4e151b194b16ad41aba9b2"

BODY=$(cat <<'EOF'
**Test Execution Plan**

- **Run smoke tests: False** — `tests/global_config_aws.py` is a `pytest_testconfig` data file loaded only when tests are executed with the AWS-specific `--tc-file` option; it is not imported by `tests/conftest.py` or any autouse fixture by default, so no smoke-marked test is exercised through the standard collection path.
- **Run gating tests: False** — No gating-marked test imports this file or the changed symbols (`CEPH_RBD_VIRTUALIZATION`, `IO2_CSI`, `TRIDENT_CSI_FSX`) directly; impact is limited to the AWS storage-class matrix used only when this config is explicitly selected.
- **Affected tests to run** (only when executed against the AWS config, i.e. with `--tc-file=tests/global_config_aws.py` or equivalent AWS job config):
  - `-m storage` (any test consuming the `storage_class_matrix` fixture, e.g. `tests/storage/test_wffc.py`, `tests/storage/test_hotplug.py`, `tests/storage/cdi_clone/`, `tests/storage/cdi_import/`, `tests/storage/cdi_upload/`, `tests/storage/snapshots/`) — new `CEPH_RBD_VIRTUALIZATION` entry adds a new matrix parametrization, and moving `default: True` from `TRIDENT_CSI_FSX` to `IO2_CSI` changes which storage class is used for non-matrixed/default-storage-class tests.
  - Any test using `storage_class_a` / `storage_class_b` (both now resolve to `IO2_CSI`, unchanged) — low risk, verify no regression.

**Real tests (cluster required, AWS)**
Happy path (regression, default storage class now `IO2_CSI`):
`pytest tests/storage/test_wffc.py --tc-file=tests/global_config_aws.py --collect-only`
Expected: collection succeeds, `IO2_CSI` used as default storage class, `TRIDENT_CSI_FSX` matrix entry still present without `default` flag.

New entry sanity check (`CEPH_RBD_VIRTUALIZATION`):
`pytest tests/storage/test_hotplug.py --tc-file=tests/global_config_aws.py -k ceph_rbd_virtualization`
Expected: new storage-class matrix entry is picked up and tests run/skip appropriately based on cluster storage-class availability.
EOF
)

gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  "/repos/${REPO}/pulls/${PR}/comments" \
  -f body="$BODY" \
  -f commit_id="$SHA" \
  -f path="tests/global_config_aws.py" \
  -F line=14 \
  -f side="RIGHT"

Length of output: 7118


Inline test execution plan comment posted on tests/global_config_aws.py (line 14).

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.

5 participants