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.

Description of problem:
As summary.

Version-Release number of selected component (if applicable):
virt-manager-0.8.4-2.el6.noarch
libvirt-0.8.1-4.el6.x86_64
python-virtinst-0.500.3-2.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a pool named 'VirtualMachines', path to '/var/lib/libvirt/images/',
and set the state with 'Active'.
2. Create a new VM, and proceeding to the dialog of disk image creation. 
3. Hit the 'Browse' button and manually create a storage volume.
4. Choosing created volume and hit 'Forward'.
  
Actual results:
Popup 'Input Error' dialog.

Expected results:
No error occurs.

Additional info:

We can try to work around this in virt-manager, but this is mostly a libvirt issue with not sanitizing pool target paths. I've posted an upstream libvirt patch to fix this:

https://www.redhat.com/archives/libvir-list/2010-May/msg00748.html

Re-assigning to libvirt.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Created attachment 417727 [details]
Sanitize pool target paths (mail message, misplaced the original patch!)

libvirt-0_8_1-8_el6 has been built in RHEL-6-candidate with the fix.

Dave

Verified under libvirt-0.8.1-8.el6 using virt-manager-0.8.4-3.el6.noarch

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.