when a backend fails, nothing is logged

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

Bug Description

When zeoraid notices a back end has failed, the status changes to "degraded" and the details show which back end has failed.

However, nothing appears to be logged, even at debug level, when this happens. I assume zeoraid first notices this when a client (which may be bin/zeoraid) does something?

Anyway, would be *really* good to have something logged at ERROR or even CRITICAL as soon as that happens...

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

Fixed in 105944.

Changed in gocept.zeoraid:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
ChrisW (chris-simplistix) wrote :

Okay, so we currently get:

Storage zeo2 degraded. Reason: storage is not connected

This doesn't seem quote correct, it should be:

Storage 'packed' on backend 'zeo2' degraded. Reason: storage is not connected

Could you make this change for the next beta?

Changed in gocept.zeoraid:
status: Fix Released → In Progress
Revision history for this message
Christian Theune (ctheune) wrote :

Sure. Committed in revision 105975

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