Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1514942 - Add option to specify the host when uploading an image via the API
Add option to specify the host when uploading an image via the API
Status: CLOSED CURRENTRELEASE
Product: ovirt-engine
Classification: oVirt
Component: RestAPI (Show other bugs)
4.2.0
Unspecified Unspecified
high Severity high (vote)
: ovirt-4.2.0
: ---
Assigned To: Daniel Erez
Avihai
: Improvement
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-19 10:31 EST by Allon Mureinik
Modified: 2018-01-25 00:20 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
This release adds the ability to specify a host in the ImageTransfer entity. This is useful if you prefer to use a specific host for uploading.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-20 06:34:50 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2+
ratamir: testing_plan_complete-


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 84342 master MERGED restapi: ImageTransfer creation - support host attribute 2017-11-23 11:18 EST

  None (edit)
Description Allon Mureinik 2017-11-19 10:31:52 EST
Description of problem:
org.ovirt.engine.core.bll.storage.StorageHandlingCommandBase#initializeVds picks a random active host if not host is supplied (as is, e.g., by the GUI).

For performance considerations, REST API users may also want to select a specific host.
Comment 1 Avihai 2017-12-07 08:23:43 EST
verified on 4.2.0-0.6.el7
Comment 2 Sandro Bonazzola 2017-12-20 06:34:50 EST
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.