Bug 1554117 - Can't boot from ISO (in data domain) via Run-Once
Summary: Can't boot from ISO (in data domain) via Run-Once
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.2
: ---
Assignee: Arik
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-11 14:58 UTC by Yaniv Kaul
Modified: 2018-08-22 14:04 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.2.2.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:00:09 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
ebenahar: testing_plan_complete+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 88772 0 'None' 'MERGED' 'core: fix handling of iso on block storage via run-once' 2019-11-13 19:48:45 UTC
oVirt gerrit 88775 0 'None' 'MERGED' 'core: cleanup in writing cd-rom to engine xml' 2019-11-13 19:48:45 UTC
oVirt gerrit 88782 0 'None' 'MERGED' 'core: fix handling of iso on block storage via run-once' 2019-11-13 19:48:45 UTC
oVirt gerrit 88934 0 'None' 'MERGED' 'core: cleanup in writing cd-rom to engine xml' 2019-11-13 19:48:45 UTC

Description Yaniv Kaul 2018-03-11 14:58:01 UTC 
Description of problem:
I've uploaded disk to a data domain (block, iSCSI) and tried to boot from it via Run Once.

Although it is since in the libvirt XML in VDSM, it is not in the qemu command line and boot fails.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0-0.0.master.20180309171125.git1840d82
vdsm-4.3.0-0-127.git537df0e

How reproducible:
Always

Steps to Reproduce:
1. Upload an ISO disk to a block data domain.
2. Use Run-once to try and boot from that ISO
Comment 1 Avihai 2018-03-18 09:11:23 UTC 
Verified on ovirt-engine-4.2.2.4
Comment 2 Sandro Bonazzola 2018-03-29 11:00:09 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.
Note You need to log in before you can comment on or make changes to this bug.