Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1305209

Summary: Wrong error info when import non-existent disk image from virt-manager GUI
Product: Red Hat Enterprise Linux 6 Reporter: tingting zheng <tzheng>
Component: virt-managerAssignee: Pavel Hrdina <phrdina>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.8CC: juzhou, mxie, mzhan, phrdina, rbalakri, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-manager-0.9.0-32.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1305210 (view as bug list) Environment:
Last Closed: 2017-03-21 10:42:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1305210    

Description tingting zheng 2016-02-06 06:23:04 UTC
Description:
Wrong error info when import non-existent disk image from virt-manager GUI

Version:
virt-manager-0.9.0-31.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Lauch virt-manager GUI.

2.Create a new guest,choose "Import existing disk image",click "Forward",input non-existent disk image path in input field "Provide the existing storage path",eg:sdfsfd,error shows as below:
Size must be specified for non-existent volume path '/root/sdfsfd

Actual results:
As description.

Expected results:
No input field in virt-manager GUI for input size,the error info is confusing for users,changed to something like "The volume path doesn't exist".

Additional info:
It can also be reproduced on rhel7.

Comment 4 zhoujunqin 2016-12-05 08:32:37 UTC
I can reproduce with package:
virt-manager-0.9.0-31.el6.x86_64
python-virtinst-0.600.0-29.el6.noarch

Then try to verify this bug with new build:
python-virtinst-0.600.0-30.el6.noarch
virt-manager-0.9.0-33.el6.x86_64

Steps:

1.Launch virt-manager .
#virt-manager

2.Create a new guest,choose "Import existing disk image",click "Forward",input non-existent disk image path in input field "Provide the existing storage path",eg:sdfsfd

Results:
After step2, An input error "The import path must point to an existing storage" pops up.

According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED.

Comment 6 errata-xmlrpc 2017-03-21 10:42:05 UTC
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.

https://rhn.redhat.com/errata/RHBA-2017-0686.html