Collective zc.buildout recipes

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

Reported by Tim on 2012-05-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
collective.buildout
Undecided
Unassigned

Bug Description

Basically I'm taking about this bit of code in __init__.py

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

Unfortunately in my case zeo_address is '0.0.0.0:8100' 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 0.0.0.0:8100 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 __init__.py 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