another bin/zeoraid reload bug
Bug #464339 reported by
ChrisW
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gocept.zeoraid |
Fix Released
|
Undecided
|
Christian Theune | ||
Bug Description
Steps to reproduce starting with the following zeo.conf:
%import gocept.zeoraid
<zeo>
address 127.0.0.1:8200
</zeo>
<raidstorage main>
<zeoclient 1>
server localhost:8100
storage 1
</zeoclient>
<zeoclient 2>
server localhost:8101
storage 1
</zeoclient>
</raidstorage>
<eventlog>
<logfile>
path STDOUT
</logfile>
</eventlog>
1. Start server
2. remove zeoclient 2 from zeo.conf
3. bin/zeoraid reload -> client 2 removed as expected
4. add zeoclient 2 back into zeo.conf
5. bin/zeoraid reload -> client 2 does not get added back :-(
You have to restart the zeoraid server for client 2 to come back.
Revision history for this message
| Christian Theune (ctheune) wrote | #1 |
| Changed in gocept.zeoraid: | |
| status: | New → In Progress |
| assignee: | nobody → Christian Theune (ct-gocept) |
Revision history for this message
| Christian Theune (ctheune) wrote | #2 |
| Changed in gocept.zeoraid: | |
| status: | In Progress → Fix Committed |
| Changed in gocept.zeoraid: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| ChrisW (chris-simplistix) wrote | #3 |
To post a comment you must log in.
Yeah, that's broken. There's no test for that. I'm fixing this right now and will provide a test.