Skip to content

CherryPicked: [cnv-4.21] Add SecureExecution feature gate to expected KubeVirt feature gates for s390x#4618

Open
laxmi-333 wants to merge 2 commits intoRedHatQE:cnv-4.21from
laxmi-333:feature_gates_s390x-cnv-4.21
Open

CherryPicked: [cnv-4.21] Add SecureExecution feature gate to expected KubeVirt feature gates for s390x#4618
laxmi-333 wants to merge 2 commits intoRedHatQE:cnv-4.21from
laxmi-333:feature_gates_s390x-cnv-4.21

Conversation

@laxmi-333
Copy link
Copy Markdown
Contributor

Cherry-pick from main branch, original PR: #4156

Short description:

Add SecureExecution featuregate support for s390x in featuregate tests

More details:

SecureExecution is a feature gate present in the KubeVirt CR on s390x clusters. The existing feature gate tests were failing on s390x because the expected feature gate set did not include SecureExecution.

This PR introduces EXPECTED_KUBEVIRT_S390X_FEATUREGATES and conditionally merges it into the expected feature gates using the is_s390x_cluster fixture.

What this PR does / why we need it:

Ensures feature gate tests pass on s390x by including SecureExecution in the expected KubeVirt feature gates. Without this change, the following tests fail on s390x clusters because SecureExecution is present in the KubeVirt CR but missing from the expected set:

test_managed_cr_featuregate_reconcile[delete_featuregates_kubevirt_cr]
test_default_featuregates_by_resource[verify_defaults_featuregates_kubevirt_cr]

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

…or s390x (RedHatQE#4156)

Add SecureExecution featuregate support for s390x in featuregate tests
SecureExecution is a feature gate present in the KubeVirt CR on s390x
clusters. The existing feature gate tests were failing on s390x because
the expected feature gate set did not include SecureExecution.

This PR introduces `EXPECTED_KUBEVIRT_S390X_FEATUREGATES` and
conditionally merges it into the expected feature gates using the
`is_s390x_cluster` fixture.

Ensures feature gate tests pass on s390x by including SecureExecution in
the expected KubeVirt feature gates. Without this change, the following
tests fail on s390x clusters because SecureExecution is present in the
KubeVirt CR but missing from the expected set:

- test_managed_cr_featuregate_reconcile[delete_featuregates_kubevirt_cr]
-
test_default_featuregates_by_resource[verify_defaults_featuregates_kubevirt_cr]

<!-- full-ticket-url needs to be provided. This would add a link to the
pull request to the jira and close it when the pull request is merged
If the task is not tracked by a Jira ticket, just write "NONE".
-->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

* **Tests**
* Added s390x-specific expected feature-gates and a fixture that
computes expected feature-gates per architecture.
* Introduced an expected-value fixture and updated test
parameterization/parameter names for clarity.
* Expanded test coverage to validate default and reconciled KubeVirt
feature-gates across architectures.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Laxmi Adavalli <laxmi.adavalli@ibm.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 28, 2026

Important

Review skipped

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

🗂️ Base branches to auto review (4)
  • main
  • cnv-4.20
  • cnv-4.19
  • cnv-4.18

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 990e7fa3-b3d3-4562-9167-b59da54ca204

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

@openshift-virtualization-qe-bot-5
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

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

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.

3 participants