[ZOOKEEPER-921] zkPython incorrectly checks for existence of required ACL elements

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.1, 3.4.0
• Fix Version/s: 3.3.3, 3.4.0
• Component/s: contrib-bindings

Environment

Mac OS X 10.6.4, included Python 2.6.1

• Hadoop Flags: Reviewed
• Assignee: Nicholas Knight
• Reporter: Nicholas Knight
• Created: 08/Nov/10 08:51
• Updated: 23/Nov/11 19:22
• Resolved: 29/Dec/10 00:46

Description

Calling zookeeper.create() seems, under certain circumstances, to be corrupting a subsequent call to Python's logging module.

Specifically, if the node does not exist (but its parent does), I end up with a traceback like this when I try to make the logging call:

Traceback (most recent call last):
  File "zktest.py", line 21, in <module>
    logger.error("Boom?")
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/logging/__init__.py", line 1046, in error
    if self.isEnabledFor(ERROR):
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/logging/__init__.py", line 1206, in isEnabledFor
    return level >= self.getEffectiveLevel()
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/logging/__init__.py", line 1194, in getEffectiveLevel
    while logger:
TypeError: an integer is required

But if the node already exists, or the parent does not exist, I get the appropriate NodeExists or NoNode exceptions.

I'll be attaching a test script that can be used to reproduce this behavior.