Red Hat Bugzilla – Bug 920688
VDSM attribute error exception when trying to write to vdsm log.
Last modified: 2016-02-10 14:10:00 EST
Created attachment 709004 [details] vdsm log vdsm attribute error exception when trying to write to log. Here is the exception: -------------------- Thread-311651::DEBUG::2013-03-10 23:25:38,437::misc::1161::Event.Storage.DomainMonitor.onDomainConnectivityStateChange::(_emit) Emitting event Thread-311651::WARNING::2013-03-10 23:25:38,437::misc::1179::Event.Storage.DomainMonitor.onDomainConnectivityStateChange::(_emit) Could not run registered method because of an exception Traceback (most recent call last): File "/usr/share/vdsm/storage/misc.py", line 1171, in _emit logUtils.funcName(func)) File "/usr/share/vdsm/logUtils.py", line 30, in funcName return func.func_name AttributeError: 'functools.partial' object has no attribute 'func_name' full vdsm log attached.
This issue has been solved upstream and should be easily backported commit 297f05889f292c2803f3e7b0d470c59cba8e1c7e Author: Dan Kenigsberg <danken@redhat.com> Date: Wed Jan 23 14:37:03 2013 +0200 logUtils.funcName: work on partial methods
*** Bug 920692 has been marked as a duplicate of this bug. ***
This bug is currently attached to errata RHBA-2012:14332. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
no need for DOC. unable to reproduce in vdsm-4.10.2-14.0.el6ev.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/RHSA-2013-0886.html