the default for rest_transport_uri leads to non deterministic behavior
Bug #1818615 reported by
Andrea Ieri
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Graylog Charm |
Fix Released
|
Medium
|
Wouter van Bommel |
Bug Description
The default for the charm setting rest_transport_uri is unset, which in conjunction with a hardcoded default of "rest_listen_uri = http://
If the graylog unit is hosting LXDs, that address may be lxdbr0, and since ordering does not appear to be numeric or alphabetic, the "first" address can vary across reboots.
I propose that the default be changed to the IP address of the interface residing in the space the website endpoint is bound to.
[0] https:/
Related branches
~xavpaice/charm-graylog:bug/1818615
Merged
into
~graylog-charmers/charm-graylog:master
at
revision de6bd7915f570fff8d5c483a260e0a4af63e93ba
- Haw Loeung: Approve (+1)
- Xav Paice: Pending requested
- Canonical IS Reviewers: Pending requested
-
Diff: 139 lines (+52/-17)3 files modifiedconfig.yaml (+6/-3)
lib/charms/layer/graylog/utils.py (+42/-10)
reactive/graylog.py (+4/-4)
~woutervb/charm-graylog:bug/1818615
Superseded
for merging
into
~graylog-charmers/charm-graylog:master
- Xav Paice (community): Needs Fixing
- Canonical IS Reviewers: Pending requested
-
Diff: 97 lines (+42/-7)3 files modifiedconfig.yaml (+6/-3)
lib/charms/layer/graylog/utils.py (+32/-0)
reactive/graylog.py (+4/-4)
tags: | added: canonical-bootstack |
Changed in graylog-charm: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in graylog-charm: | |
assignee: | nobody → Wouter van Bommel (woutervb) |
Changed in charm-graylog: | |
status: | Confirmed → In Progress |
Changed in charm-graylog: | |
status: | In Progress → Fix Committed |
Changed in charm-graylog: | |
status: | Fix Committed → Fix Released |
Changed in charm-graylog: | |
milestone: | none → 20.05 |
To post a comment you must log in.
+1 to this.
The standard FCB bundle now has graylog-mongodb deployed in an lxd container on the graylog unit. This didn't used to be the case, which is why this bug has only recently surfaced.
We worked around this by changing the juju config for rest_transport_uri to the "real" primary IP of the graylog unit:
juju config graylog rest_transport_uri=http:// 10.1.2. 3:9001/ api/
Another work-around would be to not put graylog-mongodb in a lxd container on the graylog unit.