Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1964241

Summary:	[RFE][CBT][Veeam]Allow providing the created backup ID when starting a VM backup
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Evelina Shames <eshames>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.6	CC:	aefrat, ahadas, bugs, michal.skrivanek
Target Milestone:	ovirt-4.5.0	Keywords:	FutureFeature, ZStream
Target Release:	4.5.0	Flags:	pm-rhel: ovirt-4.5? pm-rhel: planning_ack? pm-rhel: devel_ack+ pm-rhel: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-20 06:33:59 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 Eyal Shenitzky 2021-05-25 05:47:18 UTC

Description of problem:

When a VM backup is taken the engine generates the backup ID.
After bug 1849861 will be fixed, the correlation between
the command ID and the backup ID can be detached so the user can provide
the ID for the created VM backup.

It will allow the user to have recovery options when something goes wrong and the created backup ID was not provided to him in the response.

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


How reproducible:


Steps to Reproduce:
1. Create a VM with a disk enabled for backup
2. Start a VM backup


Actual results:
The engine generates the backup ID

Expected results:
The user should be able to provide the backup ID

Additional info:

Comment 1 Arik 2021-12-06 08:28:01 UTC

Seems all the posted patches were merged, anything missing?

Comment 2 Eyal Shenitzky 2021-12-06 09:41:45 UTC

Nope, moving to modified.

Comment 4 Evelina Shames 2022-03-06 14:55:21 UTC

Verified on nightly build:
ovirt-engine-4.5.0-24530d17874e.212.el8ev

POST /ovirt-engine/api/vms/3ace6cd7-e7f4-471e-957a-5b1d5df25aad/backups
<backup id="87b7912c-5e2c-4712-8dd9-7c76ca51b60e">
    <disks>
        <disk id="310f5984-cb8b-4306-8607-4ecef5c6969c"/>
    </disks>
</backup>

Result:
<backups>
    <backup href="/ovirt-engine/api/vms/3ace6cd7-e7f4-471e-957a-5b1d5df25aad/backups/87b7912c-5e2c-4712-8dd9-7c76ca51b60e" id="87b7912c-5e2c-4712-8dd9-7c76ca51b60e">
...
    </backup>
</backups>

Moving to 'Verified'.

Comment 6 Sandro Bonazzola 2022-04-20 06:33:59 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.