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.

Bug 738522

Summary:	Traceback in event-test.py when revert to a snapshot
Product:	Red Hat Enterprise Linux 6	Reporter:	Nan Zhang <nzhang>
Component:	libvirt	Assignee:	Eric Blake <eblake>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	acathrow, dallan, dyuan, mzhan, rwu, whuang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-03 21:13:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nan Zhang 2011-09-15 05:11:00 UTC

Description of problem:
As subject.
Refer to Comment 6 of BZ#737010 for reproduced steps.

Version-Release number of selected component (if applicable):
libvirt-0.9.4-11.el6.x86_64

How reproducible:
always

Steps to Reproduce:
# python /usr/share/doc/libvirt-python-0.9.4/events-python/event-test.py
Using uri:qemu:///system
myDomainEventCallback1 EVENT: Domain foo(3) Started Booted
myDomainEventCallback2 EVENT: Domain foo(3) Started Booted
myDomainEventCallback1 EVENT: Domain foo(3) Suspended Paused
myDomainEventCallback2 EVENT: Domain foo(3) Suspended Paused
myDomainEventCallback1 EVENT: Domain foo(3) Resumed Unpaused
myDomainEventCallback2 EVENT: Domain foo(3) Resumed Unpaused
myDomainEventCallback1 EVENT: Domain foo(-1) Stopped Saved
myDomainEventCallback2 EVENT: Domain foo(-1) Stopped Saved
myDomainEventCallback1 EVENT: Domain foo(4) Started Restored
myDomainEventCallback2 EVENT: Domain foo(4) Started Restored
myDomainEventCallback1 EVENT: Domain foo(4) Suspended Paused
myDomainEventCallback2 EVENT: Domain foo(4) Suspended Paused
myDomainEventCallback1 EVENT: Domain foo(-1) Stopped Destroyed
myDomainEventCallback2 EVENT: Domain foo(-1) Stopped Destroyed
myDomainEventCallback1 EVENT: Domain foo(5) Started Snapshot
myDomainEventCallback2 EVENT: Domain foo(5) Started Snapshot
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2979, in _dispatchDomainEventCallbacks
    cb(self,dom,event,detail,opaque)
  File "/usr/share/doc/libvirt-python-0.9.4/events-python/event-test.py", line 450, in myDomainEventCallback1
    detailToString(event, detail))
  File "/usr/share/doc/libvirt-python-0.9.4/events-python/event-test.py", line 445, in detailToString
    return eventStrings[event][detail]
IndexError: tuple index out of range
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2990, in _dispatchDomainEventLifecycleCallback
    cb(self, virDomain(self, _obj=dom), event, detail, opaque)
  File "/usr/share/doc/libvirt-python-0.9.4/events-python/event-test.py", line 455, in myDomainEventCallback2
    detailToString(event, detail))
  File "/usr/share/doc/libvirt-python-0.9.4/events-python/event-test.py", line 445, in detailToString
    return eventStrings[event][detail]
IndexError: tuple index out of range

  
Actual results:
Traceback occurs when revert to a snapshot

Expected results:
No any trackback.

Additional info:
event-c version works well.

Comment 4 Dave Allan 2011-12-19 21:28:03 UTC

Is this behavior reproducible on the current 6.3 builds?

Comment 5 Nan Zhang 2011-12-21 06:41:39 UTC

Yes, it's also reproducible on libvirt-0.9.8-1.el6.x86_64 build.

Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3042, in _dispatchDomainEventCallbacks
    cb(self,dom,event,detail,opaque)
  File "/usr/share/doc/libvirt-python-0.9.8/events-python/event-test.py", line 452, in myDomainEventCallback1
    detailToString(event, detail))
  File "/usr/share/doc/libvirt-python-0.9.8/events-python/event-test.py", line 447, in detailToString
    return eventStrings[event][detail]
IndexError: tuple index out of range
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 3053, in _dispatchDomainEventLifecycleCallback
    cb(self, virDomain(self, _obj=dom), event, detail, opaque)
  File "/usr/share/doc/libvirt-python-0.9.8/events-python/event-test.py", line 457, in myDomainEventCallback2
    detailToString(event, detail))
  File "/usr/share/doc/libvirt-python-0.9.8/events-python/event-test.py", line 447, in detailToString
    return eventStrings[event][detail]
IndexError: tuple index out of range

Comment 6 Dave Allan 2012-01-03 21:13:22 UTC

It's unlikely that we're ever going to get to this BZ, so I'm going to close as WONTFIX.