Hide Forgot
Description of problem: When create storage volume, if I input 50 characters as volume name, the error message will popup "Volume Parameter Error: Storage object name must be a string between 0 and 50 characters". Version-Release number of selected component (if applicable): virt-manager-0.8.6-4.el6.noarch How reproducible: Always Steps to Reproduce: 1. Open the "Host Details" page. 4. Click Storage tab on Host Details dialogue. 5. Click on one active storage pool at the left area. 6. Click New Volume button 7. Input the Volume name include 50 characters, such as "aaaaaaaaaabbbbbbbbbbccccccccccddddddddddeeeeeeeeee" Actual results: Get the error message: "Volume Parameter Error: Storage object name must be a string between 0 and 50 characters" I think the volume name include 4 default characters : '.img', so we only can input 46 characters. But the VM name support 50 characters. Expected results: The volume should be created successfully Additional info:
And the error message "Volume Parameter Error: Storage object name must be a string between 0 and 50 characters" is not proper. The name should not be 0 characters, it should between 1 and 50.
We need to tweak this validation check in virtinst
Upstream now: http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=e4435e59332b7fe7b8b40be33d2cdd5759bfce39
Fixed in python-virtinst-0.600.0-1.el6
Verify with : python-virtinst-0.600.0-1.el6 virt-manager-0.9.0-4.el6 libvirt-0.9.4-0rc1.el6 qemu-kvm-0.12.1.2-2.172.el6 step: lanch virt-manager 1. Open the "Host Details" page. 2. Click Storage tab on Host Details dialogue. 3. Click on one active storage pool at the left area. 4. Click New Volume button 5. Input the Volume name include 50 characters,"aaaaaaaaaabbbbbbbbbbccccccccccddddddddddeeeeeeeeee" no error occur,the volume can be created successfully. verification passed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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-2011-1643.html