Bug 138887 - LV creation with decimal values: "Undefined type conversion"
Summary: LV creation with decimal values: "Undefined type conversion"
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: system-config-lvm   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Jim Parsons
QA Contact: Jim Parsons
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-11 20:03 UTC by Derek Anderson
Modified: 2009-04-16 23:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-12 16:45:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Derek Anderson 2004-11-11 20:03:40 UTC
Description of problem:
Use the GUI to create an LV.  Select Megabytes and click "Use
Remaining Space".  The value inserted included two decimal places. 
Click "OK" to create and get the Error dialog:

"Undefined type conversion error in model factory. Unable to complete

This worked for me in previous versions.  It's not necessary to use
remaining space to get the error.  Any KB/MB/GB value as a decimal
will produce the error.

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

How reproducible:

Steps to Reproduce:
1. Attempt to create an LV with decimal value for KB/MB/GB
Actual results:
Type conversion error.

Expected results:
LV created.

Additional info:

Comment 1 Jim Parsons 2004-11-11 23:26:03 UTC
This is fixed in the upcoming 0.9.9-1.0. The Type Conversion error is
now changed to another  error handler that gives a much better message
if the user types garbage into the Size field.

Comment 2 Derek Anderson 2004-11-12 16:45:56 UTC
Verified in system-config-lvm-0.9.9-1.0.

If you put garbage in the size field you now get:

"There is a problem with the value entered in the Size field. The
value should be a numeric value with no alphabetical characters or
symbols of any other kind."

Note You need to log in before you can comment on or make changes to this bug.