Red Hat Bugzilla – Bug 1457170
virt-manager segment fault when creating a new dir pool
Last modified: 2018-04-10 07:42:12 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.
Created attachment 1283669 [details] virt-maanger debug log
Created attachment 1283670 [details] core dump log
I'm not able to reproduce it, could you please provide the core itself?
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.
*** Bug 1472894 has been marked as a duplicate of this bug. ***
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
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.
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