Bug 527714 - Entering a non-numeric capacity creates a volume with 10000 MB
Entering a non-numeric capacity creates a volume with 10000 MB
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Cole Robinson
Fedora Extras Quality Assurance
Depends On:
Blocks: F11VirtTarget
  Show dependency treegraph
Reported: 2009-10-07 09:00 EDT by Darryl L. Pierce
Modified: 2015-06-21 20:07 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-01 18:39:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Darryl L. Pierce 2009-10-07 09:00:10 EDT
Description of problem:
When creating a new storage volume for a pool, if I enter a non-numeric value into the max capacity field and click create then a volume is created with the previous numeric value that was in the capacity field.

Version-Release number of selected component (if applicable):
(mcpierce@mcpierce-laptop:~)$ rpm -qf `which virt-manager`

How reproducible:

Steps to Reproduce:
1. Open virt-manager, go to details, go to storage tab
2. Click "New Volume"
3. Enter a non-numeric value in the max capacity field
4. Without leaving the field, click "Create Volume"
Actual results:
A volume is created that is the size of previous value in the capacity field.

Expected results:
An error message if the value was non-numeric. Or, if the current value is numeric then that value is used.

Additional info:
Comment 1 Cole Robinson 2009-12-01 18:39:32 EST
I can't reproduce on rawhide: if you enter text in the box then click away, the box sets itself to 1, so maybe this was changed at the gtk level.

Either way, fixing this would require registering focus-in/out events AFAIUI, which I think is more trouble then its worth. Closing as WONTFIX.

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