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.
Description:
In RHEL6, when click the button of refresh volume list, virt-manager would make virt-manager hang and lost response.
Version-Release number of selected component (if applicable):
libvirt-0.10.2-29.el6_5.5.x86_64
virt-manager-0.9.0-19.el6.x86_64
Steps:
1. Open virt-manager, click 'Edit'-->'Connection Details'-->'Storage'.
2. Ensure there is at least one volume in your pool, click 'refresh volume list' button.
Actual result:
1. virt-manager hang and lost response. Click virt-manager, after a while, 'Metacity' warning message pop up, give your two options, 'Force Quit' or 'Wait'
Expect result:
1. Refresh the volume list, no hang. virt-manager could work well then.
Additional info:
virt-manager works well in RHEL7
Comment 1Giuseppe Scrivano
2014-04-30 19:44:00 UTC
I couldn't reproduce the problem here, either locally or connected to a remote host. Could you attach the output of --debug? Have you done something particular to trigger this problem or it occurs every time?
Please ensure there is at least one volume in the pool, we can reproduce this issue with three different hosts by virt-manager-0.9.0-19.el6.x86_64.
Please refer to the attached --debug output log.
Cui, we need the exact details of your environment; what you've provided as steps to reproduce is insufficient as Giuseppe has tried several times with those steps without success. What kind of pool are you using? Please attach the pool and volume xml.
I had tried both 10.66.5.24: /root/virt-manager-0.9.0-22.1.el6.x86_64.rpm and virt-manager-0.9.0-23.el6, but the issue still there.
So change the status from 'ON_QA' to 'ASSIGNED'.
BTW, please feel free to access 10.66.5.24
I can reproduce this issue as comment6.
Verify the issue with virt-manager-0.9.0-24.el6
Scenario1:
1. Open virt-manager, click 'Edit'-->'Connection Details'-->'Storage'.
2. Ensure there is at least one volume in your pool, click 'refresh volume list' button.
Actual result:
Refresh button works well. virt-manager do not hang.
Scenario2:
1. Add one volume with 'Allocation' 1000M, click 'Finish' button
2. Check the pool size part.
Actual result:
'Free' size reduced around 1GB, virt-manager worked well
Scenario3:
Delete the volume in scenario2, then click refresh button.
Actual result:
'Free' size added around 1GB, virt-manager worked well.
According to above all, change the status from 'ON_QA' to 'VERIFIED'.
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-2014-1447.html