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

[6.7] Allow running Kibana against the next major of Elasticsearch #30390

Merged
merged 1 commit into from
Feb 7, 2019
Merged

[6.7] Allow running Kibana against the next major of Elasticsearch #30390

merged 1 commit into from
Feb 7, 2019

Conversation

epixa
Copy link
Contributor

@epixa epixa commented Feb 7, 2019 •
edited
Loading

To support rolling major upgrades of Elasticsearch, Kibana no longer
fails to start when it encounters an Elasticsearch cluster that is one
major version higher. This change requires that the version of Kibana in
which it ships be compatible with the next major version of
Elasticsearch.

See the corresponding change we made in 5.6 for the same reason: d401c01

@epixa
[6.7] Allow running Kibana against the next major of Elasticsearch
e680f7c 
To support rolling major upgrades of Elasticsearch, Kibana no longer
fails to start when it encounters an Elasticsearch cluster that is one
major version higher. This change requires that the version of Kibana in
which it ships be compatible with the next major version of
Elasticsearch.
@epixa epixa added release_note:enhancement blocker Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v6.7.0 labels Feb 7, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

LeeDr
LeeDr approved these changes Feb 7, 2019
View reviewed changes
Copy link
Contributor

@LeeDr LeeDr left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - I patched my 6.7.0-SNAPSHOT build with this change and restarted it. Now the elasticsearch plugin status is green and no errors about it in the log.

Fixes: #30287

(I didn't run the tests included in this PR)

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@epixa epixa merged commit 8f7444b into elastic:6.7 Feb 7, 2019
@epixa epixa deleted the 6.7-relax-es-version branch February 7, 2019 15:51
@epixa epixa mentioned this pull request Feb 7, 2019
Closed
This was referenced Feb 7, 2019
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@LeeDr LeeDr LeeDr approved these changes

Assignees
No one assigned
Labels
blocker release_note:enhancement Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v6.7.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@epixa @elasticmachine @LeeDr