Description of problem: After sucessfull backup, I want to delete older checkpoints. But if vm's in poweroff state, i can't do that. Version-Release number of selected component (if applicable): ovirt-4.4.5 How reproducible: poweroff vm and try to delete checkpoint Actual results: Checkpoint deletion failed Expected results: Checkpoint sucessfully deleted
Will be fixed as part of bug 1952577.
Version: ovirt-engine-4.4.7.5-0.9.el8ev.noarch rhv-release-4.4.7-5-001.noarch redhat-release-8.4-0.6.el8.x86_64 redhat-release-eula-8.4-0.6.el8.x86_64 vdsm-4.40.70.5-1.el8ev.x86_64 Verification steps: 1. I created a VM and disk (incremental backup enabled). 2. Did a successful backup (including finalization) - using API calls. 3. Powered off the VM. 4. Deleted checkpoint using SDK - {root@storage-{name}-vdsm1 examples]# python3 remove_checkpoint.py c1e713a1-ad3c-4f6a-9c62-29c754d12fb2 083235e9-1194-4050-a5db-3d8e7f47a4b8 -c engine}. Verification procedure: 1. After step 2 I used an API call to see the relevant checkpoint {api call : {{engine}}vms/c1e713a1-ad3c-4f6a-9c62-29c754d12fb2/checkpoints} I saw the relevant checkpoint is: <checkpoint href="/ovirt-engine/api/vms/c1e713a1-ad3c-4f6a-9c62-29c754d12fb2/checkpoints/083235e9-1194-4050-a5db-3d8e7f47a4b8" id="083235e9-1194-4050-a5db-3d8e7f47a4b8"> 2. Then a proceeded and completed step 3. 3. After completing step 4 I got the following: [ 0.0 ] Removing VM 'c1e713a1-ad3c-4f6a-9c62-29c754d12fb2' checkpoint '083235e9-1194-4050-a5db-3d8e7f47a4b8' [ 0.5 ] Checkpoint '083235e9-1194-4050-a5db-3d8e7f47a4b8' removed successfully 4. I also double-checked with an additional API call that the checkpoint was deleted and indeed got an empty checkpoint list: <checkpoints/> Verification conclusions: The expected output matched the actual output. The total flow mentioned was done with no errors/unexpected logs. I was able to delete checkpoints when the VM was powered off. Bug verified.
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.