Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] [epicli upgrade] Filebeat stops working when legacy Elasticsearch (v6) is used for storing logs #1774

Closed
to-bar opened this issue Oct 15, 2020 · 1 comment
Assignees
Milestone

Comments

@to-bar
Copy link
Contributor

to-bar commented Oct 15, 2020

Describe the bug
Before Epiphany v0.5 there was no logging role but elasticsearch role was used for storing logs.
After running epicli upgrade on Epiphany cluster v0.4.5 Filebeat was upgraded to 7.8.1 and service stopped working because groups.logging was undefined. There was the following error in syslog:

Exiting: error initializing publisher: empty array accessing 'output.elasticsearch.hosts' (source:'/etc/filebeat/filebeat.yml')

To Reproduce
Steps to reproduce the behavior:
Run epicli upgrade for cluster created by Epiphany v0.4

Expected behavior
Filebeat should not be upgraded to version 7.x if there is no Elasticsearch v7.x for storing logs.

Config files
n/a

OS
any

Cloud Environment
any

Additional context
n/a

@to-bar to-bar added this to the S20201022 milestone Oct 15, 2020
@to-bar to-bar self-assigned this Oct 15, 2020
@przemyslavic przemyslavic self-assigned this Oct 20, 2020
@przemyslavic
Copy link
Collaborator

Checked:

  • upgrade from 0.4.5: filebeat update was skipped ✔️

  • upgrade from 0.5.5: filebeat updated to 7.8.1 ✔️

@mkyc mkyc closed this as completed Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants