Bug 1091878

Summary: Click 'refresh volume list' button would make virt-manager hang and lost response
Product: Red Hat Enterprise Linux 6 Reporter: Cui Lei <lcui>
Component: virt-managerAssignee: Giuseppe Scrivano <gscrivan>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 6.5CC: codong, dyuan, gscrivan, juzhou, lcui, mzhan, rbalakri, tzheng, xuzhang, zsong
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-manager-0.9.0-24.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 06:26:37 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:
Attachments:
Description Flags
debug output none

Description Cui Lei 2014-04-28 09:24:37 UTC 
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 1 Giuseppe 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?
Comment 2 Cui Lei 2014-05-04 03:28:25 UTC 
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.
Comment 3 Cui Lei 2014-05-04 03:29:01 UTC 
Created attachment 892237 [details]
debug output
Comment 5 Dave Allan 2014-05-06 17:41:16 UTC 
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.
Comment 10 Cui Lei 2014-05-19 09:20:02 UTC 
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
Comment 13 Cui Lei 2014-05-22 02:39:55 UTC 
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'.
Comment 14 errata-xmlrpc 2014-10-14 06:26:37 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.

http://rhn.redhat.com/errata/RHBA-2014-1447.html