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 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.
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.
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