Cherry-pick: Change test_common_templates_data_volumes.py sc to be dynamic (PR #1641)

[github-actions]

🍒 Automated Cherry-pick from PR

This PR contains the cherry-pick of PR #1641 from RoniKishner/openshift-virtualization-tests.

Original PR: Change test_common_templates_data_volumes.py sc to be dynamic
Author: @RoniKishner
Merge Commit: 14a4f05

The cherry-pick was applied cleanly to cnv-4.99 without conflicts.

Original PR Link: #1641
Original Commit: 14a4f05

Original PR Description

Short description:

Update the storage class used in test_common_templates_data_volumes.py to be dynamic according to global_config

More details:

The current test uses constant storage classes, this changes the storage classes to be dynamic according to the used global_config file.

Added a QUARANTINED on test_vm_from_data_source_missing_default_storage_class

What this PR does / why we need it:

Allow the test to run on different clusters without specific storage classes

*Some global configs only have 1 storage class defined in storage_class_matrix. in those the test will use the default (same) storage class.

Summary by CodeRabbit

• Tests
  • Removed fail-fast session checks for specific storage classes; tests now skip when appropriate.
  • Golden-image workflows switched to a Fedora-based data source and corresponding test parameterization.
  • Renamed and reparameterized tests and fixtures; VM and volume flows updated to use the new data-source approach.
  • Marked one data-source path test as expected to fail due to missing default storage class.
• Refactor
  • Consolidated and decoupled fixtures for more flexible, config-driven test selection.
• Chores
  • Removed unused imports and deprecated test utilities.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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

---

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

[openshift-virtualization-qe-bot-2]

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
• Pre-commit Checks: pre-commit runs automatically if .pre-commit-config.yaml exists
• Branch Labeling: Branch-specific labels are applied to track the target branch
• Auto-verification: Auto-verified users have their PRs automatically marked as verified

📋 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

Review & Approval

• /lgtm - Approve changes (looks good to me)
• /approve - Approve PR (approvers only)
• /automerge - Enable automatic merging when all requirements are met (maintainers and 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 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, or 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:

• RoniKishner
• RoniKishner
• dshchedr
• geetikakay
• rnetser
• vsibirsk

Available Labels

• hold
• verified
• wip
• lgtm
• approve
• automerge

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

[openshift-virtualization-qe-bot]

D/S test tox -e verify-bugs-are-open failed: cnv-tests-tox-executor/16779

[geetikakay]

/lgtm