Bug 524083 - virt-manager storage "Allocation" field can be set higher than "Max Capacity"
virt-manager storage "Allocation" field can be set higher than "Max Capacity"
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Cole Robinson
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F12VirtTarget
  Show dependency treegraph
 
Reported: 2009-09-17 15:40 EDT by Evan McNabb
Modified: 2009-10-05 14:54 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-10-05 14:54:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Evan McNabb 2009-09-17 15:40:12 EDT
Description of problem:
It is possible to set "Allocation" higher than "Max Capacity" on the "Add a Storage Volume" page. If Allocation is set to a value higher than Max Capacity, it should probably dynamically set Max Capacity to whatever Allocation value is entered (at least this is how it behaves in the screen for changing guest memory).

Version-Release number of selected component (if applicable):
virt-manager-0.8.0-3.fc12.noarch

How reproducible:
Every time.

Steps to Reproduce:
1. Go to "Add a Storage Volume" page
2. Set "Max Capacity" to 5000, and "Allocation" to 10000.
3. Click "Create Volume" and this is considered valid.
  
Actual results:


Expected results:


Additional info:
Comment 1 Cole Robinson 2009-10-05 14:54:50 EDT
This is fixed in virt-manager-0.8.0-7.fc12 which is queued up for F12 GA. Closing as CURRENTRELEASE.

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