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.
Cause: When de-registering last callback for an event, improper variable was used for the de-registration of the event itself.
Consequence: Error "libvirt: XML-RPC error : internal error: domain event 0 not registered" was returned even though the code was used properly.
Fix: We changed the code to use the proper variable.
Result: Now de-registering last callback for any event will not return an error and the event will be de-registered as it should've been.
Can reproduce this with build :libvirt-0.10.2-29.el6.x86_64
verify with build:libvirt-0.10.2-29.el6_5.2.x86_64
step:
write a c file to test this:
add below in file:
....
callback1ret = virConnectDomainEventRegisterAny(conn,
dom1,
VIR_DOMAIN_EVENT_ID_REBOOT,
VIR_DOMAIN_EVENT_CALLBACK(myDomainEventCallback2),
strdup("cb1"), myFreeFunc);
....
#gcc test.c -o test -lvirt
push Ctrl+C
^CExiting on signal 2
^CExiting on signal 2
^CExiting on signal 2
^CExiting on signal 2
the error not occured. check souce file, patch applied, move 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.
http://rhn.redhat.com/errata/RHBA-2013-1856.html