Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1511420

Summary: [RFE] API for running VM with an ISO from the DATA domain
Product: [oVirt] ovirt-engine Reporter: Raz Tamir <ratamir>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, ebenahar, herrold, tnisan, ylavi
Target Milestone: ovirt-4.2.1Keywords: FutureFeature
Target Release: ---Flags: rule-engine: ovirt-4.2+
ratamir: testing_plan_complete+
ylavi: planning_ack+
rule-engine: devel_ack+
ratamir: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-22 10:00:21 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:
Bug Depends On: 1122970, 1533356, 1536826    
Bug Blocks:    

Description Raz Tamir 2017-11-09 10:17:50 UTC
Description of problem:
The feature described here https://bugzilla.redhat.com/show_bug.cgi?id=1122970
requires a python SDK api.
We need it to be able to automate it


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Allon Mureinik 2017-11-09 12:02:06 UTC
Uploading is just a regular disk upload, nothing special here.

Running a VM with this ISO of course needs an API, which, indeed, is not present yet.

Comment 2 Yaniv Kaul 2017-12-27 14:46:15 UTC
(In reply to Allon Mureinik from comment #1)
> Uploading is just a regular disk upload, nothing special here.

So why is this BZ in NEW state?

Comment 3 Tal Nisan 2017-12-27 16:11:49 UTC
We have just a small gap in adding the content type field and type to the API in order for it to be used when creating the disk via REST, a patch was posted earlier

Comment 5 Avihai 2018-01-25 15:19:08 UTC
This is the current status of this flow (running VM with ISO disk) :

* Uploading ISO file via UI - works
* Uploading ISO file via SDK which includes :
    - Creating ISO disk via SDK - DOES NOT WORK - see Bug 1533356 
    - Uploading ISO file - works as this is a regular upload as a data type disk.

* Attaching the ISO to the VM as CD via UI-works (should work for REST as this is an old function)
* Running the attached VM - does not work - Bug 1536826 

As I see it until bugs 1533356&1536826 is not fixed I can not verify this bug.
Please correct me if I'm wrong.

Comment 6 Tal Nisan 2018-01-29 09:39:50 UTC
Avihai, bug 1533356 should be ON_QA, not sure why it wasn't moved automatically as there is a tracker attached.
Please check, as for the bug 1536826, we looked into it and it will be fixed soon.

Comment 7 Avihai 2018-02-11 10:03:46 UTC
(In reply to Tal Nisan from comment #6)
> Avihai, bug 1533356 should be ON_QA, not sure why it wasn't moved
> automatically as there is a tracker attached.
> Please check, as for the bug 1536826, we looked into it and it will be fixed
> soon.

Tal , the same issue still occurs on latest downstream with the following Engine/VDSM/libvirt:

ovirt-engine-4.2.1.6-0.1.el7.noarch
vdsm-client-4.20.17-1.el7ev.noarch
libvirt-3.9.0-7.el7.x86_64
qemu-kvm-rhev-2.10.0-20.el7.x86_64

So this issue can not be verified yet .

Comment 8 Avihai 2018-02-19 12:39:14 UTC
Verified on engine 4.2.2

* Uploading ISO file via UI - works
* Uploading ISO file via SDK 
    - Creating ISO disk via SDK -works
    - Uploading ISO file - works
* Running the attached VM - works

Comment 9 Sandro Bonazzola 2018-02-22 10:00:21 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

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