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 642719 - virt-install goes into indefinite loop looking up for a volume if the storage pool doesn't exist
Summary: virt-install goes into indefinite loop looking up for a volume if the storage...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-virtinst
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: alpha
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-13 16:15 UTC by Gurhan Ozen
Modified: 2013-11-04 02:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
virt-install may go into an indefinite loop when looking up a volume if the specified storage pool did not exist. This issue has been addressed and fixed.
Clone Of:
Environment:
Last Closed: 2011-05-19 13:42:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0636 0 normal SHIPPED_LIVE python-virtinst bug fix and enhancement update 2011-05-18 17:55:48 UTC

Description Gurhan Ozen 2010-10-13 16:15:40 UTC 
Description of problem:


virt-install --name x86_64_HVM_UP_guest_vol --cdrom /var/lib/libvirt/images/x86_64_HVM_UP_guest.iso --hvm --disk vol=virtimages000/x86_64_HVM_UP_guest_vol.img,size=8 --ram 512 --debug   --prompt --accelerate --os-variant=virtio26 --network bridge:br0   --noreboot --vnc

Where virtimages000 pool doesn't exist results in indefinite loops of printing:

...
ed, 13 Oct 2010 12:14:03 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:03 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:03 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:03 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:03 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
Wed, 13 Oct 2010 12:14:04 ERROR    Couldn't lookup volume object: Storage pool not found: no pool with matching name 'virtimages000'
...

messages.

Version-Release number of selected component (if applicable):
# rpm -q python-virtinst
python-virtinst-0.500.3-7.el6.noarch


How reproducible:
Very

Steps to Reproduce:
1. Install install a guest on a volume for which the storage pool doesn't exist.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Cole Robinson 2010-12-07 22:07:00 UTC 
Can't find the exact commit, but this isn't reproducible upstream, so assuming it's fixed.
Comment 2 Cole Robinson 2011-01-14 22:11:18 UTC 
Should be fixed in python-virtinst-0.500.5-1.el6
Comment 4 koka xiong 2011-01-20 09:39:47 UTC 
Verified with python-virtinst-0.500.5-1.el6 and libvirt-0.8.7-1.el6.x86_64
1. virt-install --name test1 --cdrom /root/Downloads/en_windows_server_2008_datacenter_enterprise_standard_x64_dvd_X14-26714.iso --hvm --disk vol=ttt/test1.img,size=1 --ram 512 --debug
Wed, 19 Jan 2011 16:24:02 DEBUG    Launched with command line:
/usr/sbin/virt-install --name test1 --cdrom /root/Downloads/en_windows_server_2008_datacenter_enterprise_standard_x64_dvd_X14-26714.iso --hvm --disk vol=ttt/test1.img,size=1 --ram 512 --debug
Wed, 19 Jan 2011 16:24:02 DEBUG    Requesting libvirt URI default
Wed, 19 Jan 2011 16:24:02 DEBUG    Received libvirt URI qemu:///system
Wed, 19 Jan 2011 16:24:02 DEBUG    Requesting virt method 'hvm', hv type 'default'.
Wed, 19 Jan 2011 16:24:02 DEBUG    Received virt method 'hvm'
Wed, 19 Jan 2011 16:24:02 DEBUG    Hypervisor name is 'kvm'
Wed, 19 Jan 2011 16:24:02 DEBUG    DISPLAY is not set: defaulting to nographics.
Wed, 19 Jan 2011 16:24:02 DEBUG    Parsed volume: as pool='ttt' vol='test1.img'
Wed, 19 Jan 2011 16:24:02 DEBUG    parse_disk: returning {'format': None, 'bus': None, 'readOnly': False, 'volInstall': None, 'path': 'ttt/test1.img', 'device': 'disk', 'volName': ('ttt', 'test1.img'), 'conn': <libvirt.virConnect instance at 0x24dcc68>, 'size': 1.0, 'driverType': None, 'driverCache': None, 'shareable': False, 'driverName': None, 'sparse': True}
Wed, 19 Jan 2011 16:24:02 ERROR    Error with storage parameters: Couldn't lookup volume object: Storage pool not found: no pool with matching name 'ttt'
Wed, 19 Jan 2011 16:24:02 DEBUG    Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/virtinst/cli.py", line 612, in disk_prompt
    dev = VirtualDisk(**arg_dict)
  File "/usr/lib/python2.6/site-packages/virtinst/VirtualDisk.py", line 593, in __init__
    volObject = _lookup_vol_name(conn, volName)
  File "/usr/lib/python2.6/site-packages/virtinst/VirtualDisk.py", line 256, in _lookup_vol_name
    raise ValueError(_("Couldn't lookup volume object: %s" % str(e)))
ValueError: Couldn't lookup volume object: Storage pool not found: no pool with matching name 'ttt'

NO indefinite loops of printing display

Verification is passed.
Comment 5 zhe peng 2011-04-15 10:29:03 UTC 
verified this bug with:
Linux localhost.localdomain 2.6.32-130.el6.x86_64 #1 SMP Tue Apr 5 19:58:31 EDT
2011 x86_64 x86_64 x86_64 GNU/Linux

python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-17.el6.x86_64

passed.
Comment 7 Michael Hideo 2011-05-16 02:59:24 UTC 
    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:
* virt-install may go into an indefinite loop when looking up a volume if the specified storage pool did not exist. This issue has been addressed and fixed. (BZ#642719)
Comment 8 Michael Hideo 2011-05-16 21:42:10 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-* virt-install may go into an indefinite loop when looking up a volume if the specified storage pool did not exist. This issue has been addressed and fixed. (BZ#642719)+virt-install may go into an indefinite loop when looking up a volume if the specified storage pool did not exist. This issue has been addressed and fixed.
Comment 9 errata-xmlrpc 2011-05-19 13:42:57 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0636.html
Note You need to log in before you can comment on or make changes to this bug.