CherryPicked: [cnv-4.21] Add SecureExecution feature gate to expected KubeVirt feature gates for s390x#4618
Conversation
…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>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (4)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Report bugs in Issues Welcome! 🎉This pull request will be automatically processed with the following features: 🔄 Automatic Actions
📋 Available CommandsPR Status Management
Review & Approval
Testing & Validation
Container Operations
Cherry-pick Operations
Label Management
✅ Merge RequirementsThis PR will be automatically approved when the following conditions are met:
📊 Review ProcessApprovers and ReviewersApprovers:
Reviewers:
Available Labels
AI Features
💡 Tips
For more information, please refer to the project documentation or contact the maintainers. |
for more information, see https://pre-commit.ci
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: