Errors from rpc do not appear in logs
Bug #1504272 reported by
Martin Packman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Discovering the regression described in bug 1501563 was too hard as neither client nor server logged any relevent errors.
The underlying issue was a "json: cannot unmarshal string into Go value of type []string" error that was not being propogated or recored from rpc/Conn.loop.
Revision history for this message
| Casey Marshall (cmars) wrote | #1 |
| tags: | added: logging |
Revision history for this message
| Martin Packman (gz) wrote | #2 |
Revision history for this message
| Casey Marshall (cmars) wrote | #3 |
| Changed in juju-core: | |
| assignee: | nobody → Casey Marshall (cmars) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| assignee: | Casey Marshall (cmars) → nobody |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks for opening this .. we should add TRACE-level log messages for these serialization errors -- the root cause of the problem would have been much easier to find.