collective.recipe.filestorage does not detect zope parts if zeo-address differs

Bug #992481 reported by Tim on 2012-05-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Basically I'm taking about this bit of code in

                elif part['recipe'] == 'plone.recipe.zope2instance':
                    if zeo_address is None or zeo_address == part.get('zeo-address', 8100):

Unfortunately in my case zeo_address is '' and part.get('zeo-address', 8100) evaluates to 'DB01:8100'

They do not equal therefore it's never added to the list. Is is necessary to configure zeo to bind to since otherwise the zope clients on seperate cannot connect to it in our Amazon cluster.

I understand this is a bit of an edge case, but technically there is nothing wrong with my buildout.

I have attached a patch for that solves my problem and still maintains original functionality

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers