Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1457170 - virt-manager segment fault when creating a new dir pool
virt-manager segment fault when creating a new dir pool
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager (Show other bugs)
7.4
x86_64 Unspecified
high Severity high
: rc
: ---
Assigned To: Pavel Hrdina
Virtualization Bugs
: Regression
: 1472894 (view as bug list)
Depends On:
Blocks: 1456511 1473046 1469590
  Show dependency treegraph
 
Reported: 2017-05-31 05:00 EDT by xiaodwan
Modified: 2018-04-10 07:42 EDT (History)
9 users (show)

See Also:
Fixed In Version: virt-manager-1.4.2-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 07:40:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
virt-maanger debug log (11.13 KB, text/plain)
2017-05-31 05:02 EDT, xiaodwan
no flags Details
core dump log (111.52 KB, text/plain)
2017-05-31 05:03 EDT, xiaodwan
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0726 None None None 2018-04-10 07:42 EDT

  None (edit)
Description xiaodwan 2017-05-31 05:00:15 EDT
Description of problem:
virt-manager segment fault when creating a new dir pool

Version-Release number of selected component (if applicable):
virt-manager-1.4.1-5.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a new dir pool (type a new name and leave all others by default).

Actual results:
virt-manager segment fault when creating a new dir pool

Expected results:
virt-manager should not segment fault.

Additional info:
1. The pool in step 1 has been created successfully when re-openning virt-manager.
2. This problem doesn't happen in virt-manager-1.4.1-4.el7.noarch.
Comment 2 xiaodwan 2017-05-31 05:02 EDT
Created attachment 1283669 [details]
virt-maanger debug log
Comment 3 xiaodwan 2017-05-31 05:03 EDT
Created attachment 1283670 [details]
core dump log
Comment 5 Pavel Hrdina 2017-06-01 10:58:39 EDT
I'm not able to reproduce it, could you please provide the core itself?
Comment 8 zhoujunqin 2017-06-12 06:03:42 EDT
Hi Pavel,
I can also reproduce this bug when i created dir/netfs type pool.
Host: Snapshot-3.0 (Select 'GUI' and selected 'Virtualization* add-on package)

Package version:
virt-manager-1.4.1-7.el7.noarch
libvirt-3.2.0-9.el7.x86_64
qemu-kvm-rhev-2.9.0-9.el7.x86_64
libvirt-python-3.2.0-3.el7.x86_64

Please help have a look, thanks.
Comment 11 Cole Robinson 2017-07-20 17:13:33 EDT
*** Bug 1472894 has been marked as a duplicate of this bug. ***
Comment 13 Pavel Hrdina 2017-08-09 08:17:23 EDT
Upstream commit:

commit 5cffae0c684b3331e3631c0c0d43450caf8dc6ae
Author: Cole Robinson <crobinso@redhat.com>
Date:   Mon Jul 17 16:21:13 2017 -0400

    connection: Fix virt-manager UI cache_new_pool impl
Comment 15 zhoujunqin 2017-09-14 06:52:30 EDT
I can reproduce it with package:
virt-manager-1.4.1-5.el7.noarch

Then try to verify it with package:
virt-manager-1.4.2-1.el7.noarch

Steps:
1. Launch virt-manager: #virt-manager.	
2. Click Edit->Connection Details.	
3. Click Storage tab on Host Details dialogue.	
4. Click Add pool button.	
5. Fill out pool name and select the type 'dir', then click Forward button.	
6. Leave all others as default setting.
7. Click Finish button.

Result:
1. dir-pool can be created correctly and added on left storage list and virt-manager works well
3. virt-manager also works well when i created other types of pools, such as disk, netfs and rbd.

So move this bug from ON_QA to VERIFIED, thanks.
Comment 18 errata-xmlrpc 2018-04-10 07:40:46 EDT
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://access.redhat.com/errata/RHEA-2018:0726

Note You need to log in before you can comment on or make changes to this bug.