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:
On RHEL6, virt-who crashes with VirtError message when create new VM.
Version-Release number of selected component (if applicable):
- RHEL6.5
- virt-who-0.8-9.el6.noarch
- libvirt-0.10.2-29.el6.x86_64
- libvirt-client-0.10.2-29.el6.x86_64
- libvirt-python-0.10.2-29.el6.x86_64
How reproducible:
No reproducer
Actual results:
The following messages were written in /var/log/messages:
kernel: device vnet4 entered promiscuous mode
kernel: virbr0: topology change detected, propagating
kernel: virbr0: port 2(vnet4) entering forwarding state
qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
abrt: detected unhandled Python exception in '/usr/share/virt-who/virt-who.py'
abrtd: New client connected
abrt-server[22680]: Saved Python crash dump of pid 5291 to /var/spool/abrt/pyhook-2014-03-18-09:05:55-5291
abrtd: Directory 'pyhook-2014-03-18-09:05:55-5291' creation detected
The following files is in ABRT report:
-- backtrace --
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3571, in _dispatchDomainEventCallbacks
cb(self,dom,event,detail,opaque)
File "/usr/share/virt-who/virt.py", line 74, in changed
l = self.listDomains()
File "/usr/share/virt-who/virt.py", line 64, in listDomains
raise VirtError(str(e))
VirtError: invalid connection pointer in virConnectNumOfDomains
Local variables in innermost frame:
domains: []
self: <virt.Virt instance at 0x18b50e0>
e: libvirtError('invalid connection pointer in virConnectNumOfDomains',)
-- reason --
virt.py:64:listDomains:VirtError: invalid connection pointer in virConnectNumOfDomains
Expected results:
It shouldn't appear error message.
Additional info:
It looks similarly to bugid:1004247.
Can't reproduce on RHEL6.6-20140812.1-Server-x86_64. Therefore, Verified it
Verified version
virt-who-0.10-6.el6.noarch
libvirt-0.10.2-43.el6.x86_64
libvirt-client-0.10.2-43.el6.x86_64
libvirt-python-0.10.2-43.el6.x86_64
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.
http://rhn.redhat.com/errata/RHBA-2014-1513.html
Description of problem: On RHEL6, virt-who crashes with VirtError message when create new VM. Version-Release number of selected component (if applicable): - RHEL6.5 - virt-who-0.8-9.el6.noarch - libvirt-0.10.2-29.el6.x86_64 - libvirt-client-0.10.2-29.el6.x86_64 - libvirt-python-0.10.2-29.el6.x86_64 How reproducible: No reproducer Actual results: The following messages were written in /var/log/messages: kernel: device vnet4 entered promiscuous mode kernel: virbr0: topology change detected, propagating kernel: virbr0: port 2(vnet4) entering forwarding state qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory abrt: detected unhandled Python exception in '/usr/share/virt-who/virt-who.py' abrtd: New client connected abrt-server[22680]: Saved Python crash dump of pid 5291 to /var/spool/abrt/pyhook-2014-03-18-09:05:55-5291 abrtd: Directory 'pyhook-2014-03-18-09:05:55-5291' creation detected The following files is in ABRT report: -- backtrace -- Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3571, in _dispatchDomainEventCallbacks cb(self,dom,event,detail,opaque) File "/usr/share/virt-who/virt.py", line 74, in changed l = self.listDomains() File "/usr/share/virt-who/virt.py", line 64, in listDomains raise VirtError(str(e)) VirtError: invalid connection pointer in virConnectNumOfDomains Local variables in innermost frame: domains: [] self: <virt.Virt instance at 0x18b50e0> e: libvirtError('invalid connection pointer in virConnectNumOfDomains',) -- reason -- virt.py:64:listDomains:VirtError: invalid connection pointer in virConnectNumOfDomains Expected results: It shouldn't appear error message. Additional info: It looks similarly to bugid:1004247.