recipe handles address in zeo.conf incorrectly

Bug #484437 reported by ChrisW
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gocept.zeoraid
Fix Committed
Low
Christian Theune

Bug Description

So, I just figured out what the storage-manage scripts that the recipe generates are and tried them out.
They failed :-(

My zeo.conf value starts:

[zeoraid]
recipe = gocept.zeoraid:server
zeo.conf =
    <zeo>
    address 6001
    </zeo>
    %import gocept.zeoraid

...perfectly fine, except that the recipe assumes different to the zeo code and assumes 6100 is a server name and not a port. It shouldnt' do that ;-)

My work around for now is to use:

[zeoraid]
recipe = gocept.zeoraid:server
zeo.conf =
    <zeo>
    address 127.0.0.1:6001
    </zeo>
    %import gocept.zeoraid

Changed in gocept.zeoraid:
importance: Undecided → Low
Changed in gocept.zeoraid:
milestone: none → 1.0b8
Changed in gocept.zeoraid:
status: New → Confirmed
Changed in gocept.zeoraid:
assignee: nobody → Christian Theune (ct-gocept)
Revision history for this message
Christian Theune (ctheune) wrote :

Fixed in r106157.

Changed in gocept.zeoraid:
status: Confirmed → In Progress
status: In Progress → Fix Committed
Changed in gocept.zeoraid:
status: Fix Committed → Confirmed
status: Confirmed → Fix Committed
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.