Bug 856171

Summary: Installer did not ignore the invalid device lead to a installation failure
Product: Red Hat Enterprise Linux 6 Reporter: Meng Liang <mliang>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: acathrow, bsarathy, chchen, cshao, gouyang, hadong, jbiddle, jboggs, leiwang, mburns, ovirt-maint, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.5.0-5.el6 Doc Type: Bug Fix
Doc Text:
Previously, it was possible to set 'other device' as a storage device by mistake during installation, causing the process to eventually fail. This has been fixed so that an appropriate error message appears when trying to set 'other device' during installation.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 16:38:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
messages
none
ovirt.log
none
tmp_ovirt.log
none
Screenshot - error message of installation failure none

Description Meng Liang 2012-09-11 11:26:15 UTC 
Description of problem:
when entered a inappropriate 'Other device' as a storage device by mistake, the error message was ignored and the install process could be continue, however it leaded to a failure installation.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120815.0.el6_3
rhev-hypervisor6-6.3-20120910.0.el6_3

How reproducible:
Always

Steps to Reproduce:
1.Install RHEVH manually
2.select an device as booting disk
3.Select 'other device' as the storage disk and give a invalid value as input, for example 'a'.
4.press continue


Actual results:
Although message 'Storage Check: Invalid Block Device: a' shows, user still be able to go to password setting page. As a result, password provided, message 'An Exception Has Occurred' shows and RHEV Hypervisor Installation Failed.

Expected results:
Warning message should show and stop user from going to the next step of installation (password setting page).

Additional info:
Comment 1 Meng Liang 2012-09-11 11:30:07 UTC 
Created attachment 611730 [details]
messages
Comment 2 Meng Liang 2012-09-11 11:30:39 UTC 
Created attachment 611732 [details]
ovirt.log
Comment 3 Meng Liang 2012-09-11 11:31:44 UTC 
Created attachment 611733 [details]
tmp_ovirt.log
Comment 4 Meng Liang 2012-09-11 11:33:26 UTC 
Created attachment 611734 [details]
Screenshot - error message of installation failure
Comment 6 Mike Burns 2012-09-13 14:02:32 UTC 
Setting to low priority.  The Other Device options is an advanced option and we expect people to know what they're doing.  We should block if the device does not exist, but this appears to be a corner case.
Comment 9 cshao 2012-10-31 08:48:31 UTC 
Test version:
rhev-hypervisor6-6.4-20121015.1.el6.
ovirt-node-2.5.0-7.el6_4.noarch

Test step:
1.Install RHEVH manually
2.select an device as booting disk
3.Select 'other device' as the storage disk and give a invalid value as input, for example 'a'.
4.press continue

Test result:
1. RHEV-H will pop-up warning msg "invalid block device:a "
2. Press continue will not go to the next step of installation (password setting page), it still stay here. 
3. If continue the installation can successful.
So the bug is fixed, change bug status to VERIFIED.
Comment 10 cshao 2012-12-27 09:14:22 UTC 
Re-test with version rhev-hypervisor6-6.4-20121212.1.el6, 

Test step:
1.Install RHEVH manually
2.select an device as booting disk
3.Select 'other device' as the storage disk and give a invalid value as input, for example '/dev/sdz'.
4.press continue

Test result:
1. RHEV-H will pop-up warning msg "invalid block device:/dev/sdz"
2. Press continue will not go to the next step of installation (password setting page), it still stay here. 
3. If continue the installation can successful.
So the bug was fixed.
Comment 14 errata-xmlrpc 2013-02-28 16:38:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2013-0556.html