Issue during upgrade with nagios user and empty content
Bug #1896484 reported by
Benjamin Allot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Graylog Charm |
Fix Released
|
Medium
|
Benjamin Allot |
Bug Description
Hello,
Upon upgrading to the latest version of the charm, I encountered 2 issues:
1. The nagios user token cannot be retrieved, because the nagios user authentication fails with a 401.
2. The code doesn't handle well an empty response and try to json.loads of "None" in such case, resulting in an exception.
A workaround for the first issue was to delete the nagios user altogether. It was then recreated fine and could be authenticated again.
Here are the logs when doing the upgrade [0] and the juju status after [1].
The second issue will be fixed by a proposed MP.
[0]: https:/
[1]: https:/
Related branches
~ballot/charm-graylog/+git/charm-graylog:lp1896484
- Xav Paice (community): Approve
- Joe Guo (community): Needs Fixing
- Paul Goins: Approve
-
Diff: 23 lines (+3/-2)1 file modifiedsrc/lib/charms/layer/graylog/api.py (+3/-2)
Changed in charm-graylog: | |
status: | New → In Progress |
Changed in charm-graylog: | |
assignee: | nobody → Benjamin Allot (ballot) |
importance: | Undecided → Medium |
Changed in charm-graylog: | |
status: | Incomplete → Fix Released |
milestone: | none → 21.01 |
tags: | added: aubergine |
To post a comment you must log in.
Here is a MP fixing the JSONDecodeError exception : https:/ /code.launchpad .net/~ballot/ charm-graylog/ +git/charm- graylog/ +merge/ 391046