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.

virt-manager can crash when creating a storage pool. Reproducer:

- virt-manager --debug --connect test:///default
- Edit->Connection Details->Storage Tab
- + button, name=aaaaaa, type=dir pool, forward, finish

Crashes for me after a few attempts. Using upstream code on fedora it crashes 100% for me

The culprit is the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1435064 : the cb_add_new_pool is usually (always?) called from a non-main thread, but the impl of the function in vmmConnection calls vmmConnection._new_object_cb, which always expects to run in the main thread because it touches UI stuff. Running it from a non-main thread means there will be gtk collisions talking to the X server or accessing internal state, which will give intermittent crashes

For upstream I think the cb_add_new_pool direction is correct but it will need some testing to get it working correctly. I think for RHEL we should revert that patch and solve in a different way. I'll post comments there

Hi,Cole

Actually QE has found this regression bug during rhel7.4 testing,pls see bug 1457170 which can be reproduced all the time,I think they are the same problem,would you pls help to confirm and if so this bug can be closed as duplicated as bug 1457170.

Yes it's the same bug, I'll dupe

*** This bug has been marked as a duplicate of bug 1457170 ***