Problem
The kubevirt-datamover has limited e2e coverage in the OADP operator e2e suite. Before GA, we need comprehensive tests covering multiple cloud providers, VM configurations, and backup/restore scenarios.
Implementation lives in the oadp-operator repo. This issue tracks the requirement from the KDM side.
Current Coverage (oadp-operator)
The existing virt_backup_restore_suite_test.go covers (AWS/S3 only):
- CSI datamover backup/restore — CirrOS VM (WFFC + Immediate binding)
- CSI backup/restore — CirrOS VM (WFFC + Immediate binding)
- Powered-off VM backup/restore (CSI + CSI datamover)
- KDM CBT backup — CirrOS VM with VirtualMachineBackupTracker verification
- Fedora todolist — present but disabled (
PEntry, not running in CI)
Gaps
Cloud Providers
VM Configurations
Backup Scenarios
Restore Scenarios
Error / Edge Cases
Acceptance criteria
- e2e tests pass on AWS and at least one S3-compatible backend (MinIO) in CI
- GCP and Azure e2e tests pass once object store support lands
- Tests cover both single-disk and multi-PVC VMs
- Incremental backup chain and restore are tested end-to-end
References
Problem
The kubevirt-datamover has limited e2e coverage in the OADP operator e2e suite. Before GA, we need comprehensive tests covering multiple cloud providers, VM configurations, and backup/restore scenarios.
Implementation lives in the
oadp-operatorrepo. This issue tracks the requirement from the KDM side.Current Coverage (oadp-operator)
The existing
virt_backup_restore_suite_test.gocovers (AWS/S3 only):PEntry, not running in CI)Gaps
Cloud Providers
VM Configurations
Backup Scenarios
Restore Scenarios
Error / Edge Cases
Acceptance criteria
References
oadp-operator/tests/e2e/virt_backup_restore_suite_test.go