NO-JIRA: feat(e2e): add Azure platform support for backup/restore tests#8144
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
openshift-ci-robot
added
the
jira/valid-reference
|
@mgencur: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis change extends the backup_restore_test.go test suite to support the Azure platform by adding hyperv1.AzurePlatform to the backupRestorePlatforms map with excludeWorkloads set to ["router","karpenter","karpenter-operator"] and postRestoreHook set to nil. As a result, the test's BeforeAll platform selection logic will recognize Azure and apply the specified workload exclusions instead of skipping Azure-based hosted cluster tests. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
bot
added
area/testing
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Enable backup/restore e2e tests to run on AzurePlatform by adding it to the backupRestorePlatforms with no post-restore hook. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
mgencur
force-pushed
the
backup_restore_aks
branch
from
5e9e503 to
ddc502d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8144 +/- ##
=======================================
Coverage 29.89% 29.89%
=======================================
Files 1050 1050
Lines 97819 97819
=======================================
Hits 29240 29240
Misses 66075 66075
Partials 2504 2504 🚀 New features to boost your workflow:
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jparrill, mgencur The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/verified by tests |
openshift-ci-robot
added
the
verified
|
@jparrill: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
Scheduling tests matching the |
Test Resultse2e-aws
e2e-aks
|
|
@mgencur: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
5 participants
What this PR does / why we need it:
Enable backup/restore e2e tests to run on AzurePlatform by adding it
to the backupRestorePlatforms with no post-restore hook.
Which issue(s) this PR fixes:
Related to https://redhat.atlassian.net/browse/CNTRLPLANE-2033
Special notes for your reviewer:
Checklist:
Note
Low Risk
Low risk: test-only change that just extends platform gating/configuration and does not affect production code paths.
Overview
Backup/restore e2e tests now recognize
hyperv1.AzurePlatformby adding it tobackupRestorePlatformswith the same workload exclusions as Agent/KubeVirt and no post-restore hook, allowing the suite to run (instead of skipping) on Azure clusters.Written by Cursor Bugbot for commit 5e9e503. This will update automatically on new commits. Configure here.
Summary by CodeRabbit