Elk and Kibana Version Incompatible
Bug #1553256 reported by
Antonio Rosales
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
elasticsearch (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
Elasticsearch and Kibana deploy currently results in a Kibana dashboard that is not functional which looks like it may be due to incompatible versions. The deploy was done as follows:
juju deploy elasticsearch
juju deploy logstash-indexer
juju add-relation logstash-indexer elasticsearch:
juju deploy kibana
juju add-relation kibana elasticsearch
juju expose kibana
> as per https:/
Opening this bug to look for root cause as well as possible suggestions on fixes.
-thanks,
Antonio
To post a comment you must log in.
Hi Antonio.
TL;DR: you may find if you use the elasticsearch2 charm, things will work.
Long version: I hit a similar issue after the trusty kibana charm updated to kibana4 (which requires Elasticsearch 2 [1]) in r19 [2]. Generally, I don't think we should ever be updating application major versions in a stable charm like that, unless the charm takes explicit care (and testing) so that upgrade-charm manages the upgrade correctly - otherwise it'll be fine for demos where you're deploying anew every time, but will break peoples existing deployments.
Anyway, bottom line for me was I could no longer deploy ELK because the kibana charm was now using kibana4 and needed ES2. I specifically *didn't* update the trusty elasticsearch charm to use ES2 because that will break existing deployments if they upgrade-charm (as the kibana update did). Instead, I've got a separate trusty elasticsearch2 charm [2], which is working with the kibana charm for me.
[1] https:/ /www.elastic. co/guide/ en/kibana/ current/ setup.html /code.launchpad .net/~chris. macnaughton/ charms/ trusty/ kibana/ version_ bump/+merge/ 276709 /code.launchpad .net/~onlineser vices-charmers/ charms/ trusty/ elasticsearch/ elasticsearch2
[2] https:/
[2] https:/