Bug 2041165

Summary: Finalization of a backup after the VM was powered off from guest fails with non-informative response
Product: [oVirt] ovirt-engine Reporter: Amit Sharir <asharir>
Component: BLL.StorageAssignee: Mark Kemel <mkemel>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.10CC: ahadas, bugs, michal.skrivanek, Yury.Panchenko
Target Milestone: ovirt-4.5.0Flags: asharir: needinfo-
pm-rhel: ovirt-4.5?
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-12 19:34:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amit Sharir 2022-01-16 07:43:23 UTC
Description of problem:

In case you power off a VM via the guest in the middle of a backup operation, when you try to finalize the backup of the powered-off VM (using post API call) the API response is not informative. 

Version-Release number of selected component (if applicable):

ovirt-engine-4.4.10.2-0.1.el8ev.noarch
vdsm-4.40.100.2-1.el8ev.x86_64


Steps to Reproduce:

1. Create VM from a template.
2. Attach a 10GB disk to the VM and run it.
3. Start backup using post API call - https://<env_fqdn>/ovirt-engine/api/vms/<vm_id>/backups.
5. Poweroff the VM via the guest.
6. Finalize the back using post API call: https://<env_fqdn>/ovirt-engine/api/vms/<vm_id>/backups/<backup_id>/finalize.


Actual results:

For step 5 I got the following API response: 
"<fault>
    <detail>[]</detail>
    <reason>Operation Failed</reason>
</fault>"

It is important to note that after I did the finalization API call and despite the error message the VM was UNLOCKED.

Expected results:

A more informative API response.

Comment 1 RHEL Program Management 2022-01-16 07:43:29 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 RHEL Program Management 2022-01-16 07:44:40 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Michal Skrivanek 2022-04-11 08:53:24 UTC
still relevant for hybrid backup? if not please close

Comment 5 Arik 2022-04-12 19:34:20 UTC
The new backup mechanism ("hybrid backup") is not affected by state changes of the VM during backup and so even after the VM shuts down from within the guest, the finalization would succeed

Comment 6 Sandro Bonazzola 2022-04-20 06:32:24 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 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.