Issue with OVS metrics collection: "br-data is not a bridge or a socket"
Bug #1892129 reported by
Jose Guedez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Telegraf Charm |
Fix Released
|
Critical
|
Jose Guedez |
Bug Description
Using charm release cs:telegraf-38, a unit with OVS installed but without a bridge called br-data reported the following errors in the telegraf log:
2020-08-
The current check has a hardcoded list of OVS bridges (br-int, br-tun, br-data), but the actual bridges available vary depending on the specific application or deployment. It would probably be better to query OVS for the list of available bridges.
Related branches
~jfguedez/charm-telegraf:backport-1891781-1892129
- James Hebden (community): Approve
- Celia Wang: Approve
-
Diff: 275 lines (+129/-23)4 files modifiedsrc/files/telegraf_exec_metrics.py (+18/-7)
src/files/telegraf_sudoers (+1/-0)
src/reactive/telegraf.py (+35/-11)
src/tests/unit/test_telegraf.py (+75/-5)
~jfguedez/charm-telegraf:bug/1892129
- Alvaro Uria (community): Approve
- Edin S (community): Approve
- Canonical IS Reviewers: Pending requested
- Canonical IS Reviewers: Pending requested
-
Diff: 93 lines (+46/-9)3 files modifiedsrc/files/telegraf_exec_metrics.py (+14/-9)
src/files/telegraf_sudoers (+1/-0)
src/tests/unit/test_telegraf.py (+31/-0)
Changed in charm-telegraf: | |
assignee: | nobody → Jose Guedez (jfguedez) |
importance: | Undecided → Critical |
status: | New → Triaged |
status: | Triaged → In Progress |
Changed in charm-telegraf: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Released at cs:~llama- charmers- next/telegraf- 4