abh1sar commented on PR #13074: URL: https://github.com/apache/cloudstack/pull/13074#issuecomment-4789527735
## Test Status - 24 June
Remaining - 8
Failing - 5 (Review comments posted for fixes)
Passing - 25
| Status | Count | Test case numbers
|
|-----------|-------|--------------------------------------------------------|
| Pass | 25 | 1–12, 14–16, 18, 20–22, 31–34, 36, 38 |
| Fail | 5 | 13, 17, 19, 35, 37
|
| Remaining | 8 | 23–30
|
| # | Section | TestCase
| Expected
| Result
|
|-----|---------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | No Harm test (config disabled) | Create backup
| No change in behaviour
| Pass
|
| 2 | | Delete backups
| No change in behaviour
| Pass
|
| 3 | | Restore from backup
| No change in behaviour
| Pass
|
| 4 | | Restore and attach volume from backup
| No change in behaviour
| Pass
|
| 5 | | Create new instance from Backup
| No change in behaviour
| Pass
|
| 6 | | Assign/Remove backup offering
| No change in behaviour
| Pass
|
| 7 | | Backup VM with multiple data disks
| No change in behaviour — all disks backed up, no extra metadata
| Pass
|
| | |
|
|
|
| 8 | Create Backups | Create incremental backups
| Verify incremental backups are taken with the correct
db entries and bitmap in the qcow2 file. Verify that the backing file is set to
the parent | Pass
|
| 9 | | Incremental backups after stop-start VM
| Verify that incremental backup was taken after stopping and starting
the VM
| Pass
|
| 10 | | Test backup chain is terminated after N backups
| Verify that a full backup is taken after `nas.backup.full.every`
backups
| Pass
|
| 11 | | Full Backup after VM migration
| Backup should be successful
| Pass
|
| 12 | | Incremental backup after Volume migration
| Backup should be successful
| Pass
|
| 13 | | Full Backup after Volume migration — followed by incremental
backup | Parent path in the incremental backup should reflect the
migrated volume path correctly; backup should succeed
| Fail — backup fails because parent path is not correct (volume
path is `uuid.qcow2` after migration but backing file reference is `uuid`) |
| 14 | | Delete backup followed by create backup
| Backup should be successful
| Pass
|
| 15 | | Backup stopped VM
| Backup should be successful
| Pass
|
| 16 | | Backup Running VM after Backup of stopped VM
| Verify that the running VM backup was incremental
| Pass
|
| 17 | | Backup after volume snapshot restore
| Snapshot restores remove all bitmap information. Backup should fall
back to full backup.
| Fail - volume restore removes all the bitmaps - backup fails as it
doesn't check bitmap present on all disks |
| 18 | | Incremental backup when parent bitmap is missing from all qcow2
files | Self-heal: fall back to full backup automatically; backup succeeds;
DB records it as full
| Pass
|
| 19 | | Incremental backup when parent bitmap is missing from only one
qcow2 file | Self-heal: fall back to full backup automatically; backup
succeeds; DB records it as full
| Fail - backup fails as it doesn't check bitmap present on all
disks. |
| 20 | | Incremental backup for VM with multiple data disks
| Each disk is backed up incrementally; each has its own bitmap chain;
all backing file references are correct
| Pass
|
| 21 | | Incremental backup size is smaller than full backup
| Verify that incremental backup file size is strictly less than a full
backup for the same VM state after write-few-blocks workload
| Pass
|
| 22 | | Backup after VM disk resize
| Backup should be successful
| Pass
|
| 23 | | Backup mid-failure cleanup
| If backup fails partway through, verify partial qcow2 file and bitmap
are cleaned up; next backup attempt succeeds
|
|
| 24 | | Backup chain integrity after agent crash during backup
| After host/agent crash during backup, reconcile should mark the
in-progress backup as failed; next backup produces a valid full or incremental
|
|
| | |
|
|
|
| 25 | Scheduled backups | Incremental backups
| Verify incremental backup chain is ended after the
correct length (`nas.backup.full.every` interval)
|
|
| 26 | | Scheduled full backup after chain length reached
| Verify next scheduled backup is full when chain limit is reached; new
chain begins from the full backup
|
|
| 27 | | Scheduled backup with VM stopped at scheduled time
| Backup of stopped VM is taken at the scheduled time; backup is marked
correctly
|
|
| 28 | | Backup autodelete
| Verify older backups are autodeleted after reaching the max backup
limit configured in the offering
|
|
| 29 | | Autodelete respects chain boundaries
| Autodelete does not delete a backup that is the parent of a
still-valid child; chain integrity is maintained
|
|
| 30 | | Autodelete of the last backup in chain triggers cascade
| All backups marked as Hidden in the chain are also deleted; resource
counts are updated correctly
|
|
| | |
|
|
|
| 31 | Restore | Restore incremental backup
| Verify the data is restored correctly
| Pass
|
| 32 | | Create instance from incremental backups
| Verify the data is restored correctly
| Pass
|
| 33 | | Restore and attach volume from incremental backup
| Verify the data is restored correctly
| Pass
|
| 34 | | Restore from a mid-chain incremental backup (not the latest)
| Verify the data is restored correctly
| Pass
|
| | |
|
|
|
| 35 | Delete | Delete last backup
| Should set VM's active checkpoint ID to null in
`vm_instance_details`; backup record removed from DB and file deleted from NFS
| Fail
|
| 36 | | Delete a leaf backup
| Backup is deleted from DB and file; resource counts decremented
| Pass
|
| 37 | | Delete non-leaf backup
| The backup should be deleted; dependent child backups should either be
collapsed or also deleted; backup should not appear in list view after deletion
| Fail — backup still showing in list view
|
| 38 | | Delete all backups for a VM and then re-assign backup offering
| After full deletion, VM can be assigned a new offering; next backup is
a fresh full backup with no stale chain references
| Pass
|
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
