Issue during upgrade with nagios user and empty content

Bug #1896484 reported by Benjamin Allot
8
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://pastebin.canonical.com/p/2zf4dDNHgD/
[1]: https://pastebin.canonical.com/p/zHQx3MBHHF/

Tags: aubergine

Related branches

Revision history for this message
Benjamin Allot (ballot) wrote :
Adam Dyess (addyess)
Changed in charm-graylog:
status: New → In Progress
Xav Paice (xavpaice)
Changed in charm-graylog:
assignee: nobody → Benjamin Allot (ballot)
importance: Undecided → Medium
Revision history for this message
Xav Paice (xavpaice) wrote :

Can you provide any more info on how to reproduce the first point?

"1. The nagios user token cannot be retrieved, because the nagios user authentication fails with a 401."

The MP for fixing the exception with json.loads() is merged, but since this bug has two problems we can't call it closed yet.

Changed in charm-graylog:
status: In Progress → Incomplete
Celia Wang (ziyiwang)
Changed in charm-graylog:
status: Incomplete → Fix Released
milestone: none → 21.01
tags: added: aubergine
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.