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.
Created attachment 1178232[details]
gdb backtrace info
Description of problem:
As subject
Version-Release number of selected component (if applicable):
libvirt-python-2.0.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Execute event-test.py:
# python `locate event-test.py`
Using uri:qemu:///system
2. In another terminal, do pool-refresh:
# virsh pool-refresh default
Pool default refreshed
Then we can find python coredump in the former terminal
Using uri:qemu:///system
Fatal Python error: GC object already tracked
Actual results:
As step2
Expected results:
No Fatal Python error
Additional info:
libvirt-python-1.3.5-1.el7 not reproduced. So it's a regression
Verified on libvirt-python-2.0.0-2.el7.x86_64.
1. In one terminal.
[root@localhost ~]# python `locate event-test.py`
Using uri:qemu:///system
2. In another terminal.
[root@localhost ~]# virsh pool-refresh default
Pool default refreshed
3. In the first terminal, the output as follows:
Using uri:qemu:///system
myStoragePoolEventRefreshCallback: Storage pool default
No fatal python error. Move this bug to VERIFIED.
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://rhn.redhat.com/errata/RHBA-2016-2186.html
Created attachment 1178232 [details] gdb backtrace info Description of problem: As subject Version-Release number of selected component (if applicable): libvirt-python-2.0.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Execute event-test.py: # python `locate event-test.py` Using uri:qemu:///system 2. In another terminal, do pool-refresh: # virsh pool-refresh default Pool default refreshed Then we can find python coredump in the former terminal Using uri:qemu:///system Fatal Python error: GC object already tracked Actual results: As step2 Expected results: No Fatal Python error Additional info: libvirt-python-1.3.5-1.el7 not reproduced. So it's a regression