odd error when backend is down during zeoraid startup

Bug #487670 reported by ChrisW
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gocept.zeoraid
Invalid
Undecided
Unassigned

Bug Description

Could not open storage zeo2
Traceback (most recent call last):
  File "/var/buildout-eggs/gocept.zeoraid-1.0b7-py2.6.egg/gocept/zeoraid/storage.py", line 681, in _open_storage
    assert hasattr(storage, 'supportsUndo') and storage.supportsUndo()
AssertionError

Any idea what that means? I wouldn't expect this to be logged...

Revision history for this message
Christian Theune (ctheune) wrote :

Yes. It looks weird but it's OK.

I log any error that occurs and during opening I have a sanity check that adheres to the API and is pretty reliable in figuring out whether the storage really is ready to use. Under ZEO conditions this causes clients that haven't been set up correctly to raise an assertion error.

Changed in gocept.zeoraid:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.