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.

Sign up for GitHub

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

Jump to bottom

Rolling upgrade from 6.5.4 to 6.6.1 do not work well #32341

Closed
vbohata opened this issue Mar 1, 2019 · 2 comments
Closed

Rolling upgrade from 6.5.4 to 6.6.1 do not work well #32341

vbohata opened this issue Mar 1, 2019 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team

Comments

@vbohata
Copy link

vbohata commented Mar 1, 2019

Kibana version:
6.6.1

Elasticsearch version:
6.6.1

Server OS version:
Centos 7

Describe the bug:
Rolling upgrade made all the Kibana unavailable until the cluster including all Kibanas has been fully upgraded. I did rolling upgrade of ES. Worked well after that. Then I upgraded Kibana, restarted it and the remaining Kibana including the upgraded one started to report errors like "Multiple versions of Kibana are running against the same Elasticsearch cluster, unable to authorize user." and returning 500. After upgrading all the Kibanas I had to restart them to make them work again.
This behaviour is new, I did not have issues during previous upgrades. This bug makes life upgrade impossible.
@vbohata vbohata changed the title Rolling upgrade from 6.5.4 to 6.6.1 Rolling upgrade from 6.5.4 to 6.6.1 do not work well Mar 1, 2019
@nreese nreese added the bug Fixes for quality problems that affect the customer experience label Mar 6, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@nreese nreese added the Team:Operations Team label for Operations Team label Mar 6, 2019
@tylersmalley
Copy link
Contributor

Kibana does not currently support rolling upgrades and shutting down the existing instances is mentioned in the upgrade procedure.

This is something we are actively working towards. #41795 #66056

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tylersmalley @nreese @elasticmachine @vbohata