bin/zeozaid-storage-manage gives incorrect error when a storage is closed
Bug #484729 reported by
ChrisW
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gocept.zeoraid |
Won't Fix
|
Medium
|
Christian Theune | ||
Bug Description
So, as a result of #484727, one of the storages served by zeoraid became closed.
Doing "bin/zeozaid-
Could not connect to ZEO server at 0.0.0.0:6001
That feels like a bug to me. The ZEO server is running, it's just that
the storage is closed.
My guess is that the storage should really show as failed here.
At the very least, it would be useful to have the storage name in the
"Could not connect" message.
| Changed in gocept.zeoraid: | |
| importance: | Undecided → Medium |
| milestone: | none → 1.0b8 |
| status: | New → Confirmed |
| Changed in gocept.zeoraid: | |
| assignee: | nobody → Christian Theune (ct-gocept) |
Revision history for this message
| Christian Theune (ctheune) wrote | #1 |
| Changed in gocept.zeoraid: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
I'm afraid with the current implementation that uses in-band-signalling for transferring status this won't happen. I'm opening up a new wish list item which describes basing the monitoring/control client on a separate communication port/protocol.