[Storage] Use correct fedora img arch in multi-arch testing

[jpeimer]

Short description:

Use correct fedora img arch in multi-arch testing

More details:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for reviewer:

Assisted-by: Claude noreply@anthropic.com

jira-ticket:

[coderabbitai]

Warning

Rate limit exceeded

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

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ff52200d-b362-4e22-bbee-900d718c8935

📥 Commits

Reviewing files that changed from the base of the PR and between 6206af2 and 237c57f.

📒 Files selected for processing (2)

• tests/storage/cdi_import/conftest.py
• tests/storage/constants.py

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 1 minute and 43 seconds.}

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

[openshift-virtualization-qe-bot-3]

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:

• jpeimer

Reviewers:

• Ahmad-Hafe
• acinko-rh
• dalia-frank
• ema-aka-young
• josemacassan
• jpeimer
• kgoldbla
• kshvaika

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.

[jpeimer]

verified on non-multi-arch cluster
need to verify also on a multi-arch cluster

[josemacassan]

/lgtm

[kshvaika]

/lgtm

[jpeimer]

/verified

[openshift-virtualization-qe-bot-3]

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

1. Examine code changes in each modified file
2. Identify affected code paths, functions, and classes
3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
4. Trace test dependencies through imports, shared utilities, and fixture inheritance
5. Detect new tests introduced in the PR
6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
   • Changes to files/functions used by tests marked with @pytest.mark.smoke
   • Changes to fixtures or utilities imported by smoke tests
   • Changes to conftest.py files that may affect smoke test execution
   • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

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

Test Execution Plan

• Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
• path/to/test_file.py - When the entire test file needs verification
• path/to/test_file.py::TestClass::test_method - When specific test(s) needed
• path/to/test_file.py::test_function - When specific test(s) needed
• -m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

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

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]

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get PR details and changed files
gh pr view 4699 --repo RedHatQE/openshift-virtualization-tests --json files,headRefName,baseRefName

echo "---DIFF---"
gh pr diff 4699 --repo RedHatQE/openshift-virtualization-tests

Length of output: 1965

---

🏁 Script executed:

#!/bin/bash
# Check if smoke tests use the changed fixtures or constants
echo "=== Smoke tests using QUAY_FEDORA_CONTAINER_IMAGE ==="
rg -rn "QUAY_FEDORA_CONTAINER_IMAGE" --type py

echo "=== Smoke tests using created_vm_list fixture ==="
rg -rn "created_vm_list" --type py

echo "=== Files with `@pytest.mark.smoke` in cdi_import ==="
rg -rn "pytest.mark.smoke" tests/storage/cdi_import/ --type py

echo "=== All smoke tests in storage ==="
rg -rn "pytest.mark.smoke" tests/storage/ --type py -l

echo "=== Check which tests use cdi_import conftest fixtures ==="
rg -rn "created_vm_list\|QUAY_FEDORA_CONTAINER_IMAGE" tests/storage/cdi_import/ --type py

echo "=== First changed line number (line 26) in conftest.py ==="
cat -n tests/storage/cdi_import/conftest.py | head -30

Length of output: 2706

---

🏁 Script executed:

#!/bin/bash
# Get the latest commit SHA for the PR
COMMIT_SHA=$(gh pr view 4699 --repo RedHatQE/openshift-virtualization-tests --json headRefOid --jq '.headRefOid')
echo "Commit SHA: $COMMIT_SHA"

# Post inline review comment on line 26 of conftest.py (first changed line)
gh api \
  --method POST \
  -H "Accept: application/vnd.github+json" \
  /repos/RedHatQE/openshift-virtualization-tests/pulls/4699/comments \
  -f body="**Test Execution Plan**

- **Run smoke tests: True**
  - Smoke test \`test_import_registry.py\` imports \`QUAY_FEDORA_CONTAINER_IMAGE\` from \`tests/storage/constants.py\` → **changed**
  - Smoke test \`test_import_http.py\` uses \`created_vm_list\` fixture → **changed** (now uses \`ArchImages\` per \`cpu_arch\`)

**Tests to run:**
- \`tests/storage/cdi_import/test_import_registry.py\` (smoke, uses \`QUAY_FEDORA_CONTAINER_IMAGE\`)
- \`tests/storage/cdi_import/test_import_http.py\` (smoke, uses \`created_vm_list\` fixture)
- \`tests/storage/general/conftest.py\` — uses \`QUAY_FEDORA_CONTAINER_IMAGE\`; run affected tests under \`tests/storage/general/\`
- \`tests/storage/data_import_cron/\` — uses \`QUAY_FEDORA_CONTAINER_IMAGE\`; run affected tests
- \`tests/storage/cdi_clone/\` — uses \`QUAY_FEDORA_CONTAINER_IMAGE\`; run affected tests

**Must verify on:**
- ✅ Multi-arch cluster (aarch64 / s390x / ppc64le) — primary target of this fix
- ✅ x86_64 cluster — regression check" \
  -f commit_id="$COMMIT_SHA" \
  -f path="tests/storage/cdi_import/conftest.py" \
  -F line=26 \
  -f side="RIGHT"

Length of output: 3616

---

[jpeimer]

/check-can-merge