Bug 219270 - virt-install will crash if invalid memory parameter is passed
Summary: virt-install will crash if invalid memory parameter is passed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: python-virtinst
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Glauber Costa
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-12 12:03 UTC by Glauber Costa
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: RC
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-08 01:40:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Fix for that. (353 bytes, patch)
2006-12-12 12:03 UTC, Glauber Costa 		no flags Details | Diff
View All

Description Glauber Costa 2006-12-12 12:03:18 UTC 
Description of problem:

Instead of displaying an error message and moving along, virt-install will crash
if invalid memory parameter is passed.

How reproducible:
Always

Steps to Reproduce:
1. call virt-install
2. when prompted for guest's memory, type anything that does not resemble a number

  
Actual results:
virt-install crashes

Expected results:
virt-install prints an error and try again.
Comment 1 Glauber Costa 2006-12-12 12:03:18 UTC 
Created attachment 143379 [details]
Fix for that.
Comment 3 RHEL Program Management 2006-12-12 13:30:28 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 Jay Turner 2006-12-14 19:14:48 UTC 
QE ack for RHEL5.
Comment 7 RHEL Program Management 2007-02-08 01:40:57 UTC 
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.
Note You need to log in before you can comment on or make changes to this bug.