log sink read errors are not logged
Bug #1852815 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.6 |
Fix Released
|
High
|
John A Meinel |
Bug Description
We are seeing log sink read disconnect messages on Prodstack. However, bumping logging to a higher level isn't useful for debugging because we print:
logger.
So we declare that it was disconnected but we just print the hex socket identifier, which isn't useful. We need to log the error.
Changed in juju: | |
milestone: | 2.7-rc5 → none |
Changed in juju: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
https:/ /github. com/juju/ juju/pull/ 10914