Bug 1032069

Summary:	hosted-engine setup using cdrom image doesn't check if file is really image file
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	movciari
Component:	ovirt-hosted-engine-setup	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.3.0	CC:	gklein, mavital, nbarcet, oblaut, stirabos, ykaul
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, the correctness of an ISO file type was not enforced at the customization level, so the user could pass an invalid file, causing the virtual machine to refuse to boot. This error has now been fixed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-17 07:17:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description movciari 2013-11-19 13:44:36 UTC

Description of problem:
when running hosted-engine --deploy, when trying to install from cdrom file, after you provide path to file setup script checks to if file exists but doesn't check if it's really iso file

setup creates VM and tries to boot it from this file, inside VM boot fails and VM boots from PXE


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

How reproducible:
always


Steps to Reproduce:
1. create some file that's not an iso image file (for example empty file or text file)
2. try using it as cdrom file in ovirt-hosted-engine-setup

Actual results:
setup will not fail, it will create VM and try to boot it from that file, which will result in VM booting from PXE because it couldn't boot from cdrom

Expected results:
setup should check if file is really iso file and if it's not, it should give appropriate error message and let user choose another file

Additional info:

Comment 1 Gil Klein 2016-02-17 07:17:16 UTC

This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA