Bug 2078500

Summary: [RFE] Add support for parallel migration connections to the REST API
Product: [oVirt] ovirt-engine Reporter: Milan Zamazal <mzamazal>
Component: RestAPIAssignee: Milan Zamazal <mzamazal>
Status: CLOSED CURRENTRELEASE QA Contact: Qin Yuan <qiyuan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5.0.4CC: ahadas, bugs, dfodor, gdeolive, mavital
Target Milestone: ovirt-4.5.1Keywords: FutureFeature
Target Release: ---Flags: pm-rhel: ovirt-4.5?
pm-rhel: planning_ack?
pm-rhel: devel_ack+
gdeolive: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-23 05:54:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Zamazal 2022-04-25 13:15:51 UTC
We have introduced support for parallel migration connections some time ago but it is not configurable via the REST API. Support for configuring the corresponding cluster and VM migration properties should be added to the REST API.

Comment 1 Arik 2022-05-23 20:02:38 UTC
Setting high severity since it is needed for automated tests

Comment 2 Arik 2022-06-19 12:28:24 UTC
The verification here should ideally be adding an automated test for setting parallel migration

Comment 3 Qin Yuan 2022-06-21 10:11:34 UTC
Verified with:
ovirt-engine-4.5.1.2-0.11.el8ev.noarch
vdsm-4.50.1.3-1.el8ev.x86_64

Steps:
Run all test cases in the attached Polarion test plan using REST API.

Results:
All cases passed.

Comment 4 Sandro Bonazzola 2022-06-23 05:54:58 UTC
This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 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.