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

Doing rolling upgrade without enterprise key should produce better error message #11602

Closed
Holmistr opened this issue Oct 17, 2017 · 2 comments · Fixed by #11603
Closed

Doing rolling upgrade without enterprise key should produce better error message #11602

Holmistr opened this issue Oct 17, 2017 · 2 comments · Fixed by #11603
Assignees
@Donnerbart
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Milestone
3.10

Comments

@Holmistr
Copy link
Contributor

When you try to do rolling upgrade with OS version (by accident or because you just missed it), the rolling upgrade fails with:
Reason of failure for node join: Joining node's version 3.10.0 is not compatible with 3.8.6
Since rolling upgrade is an enterprise feature, it would be nice to provide better error message that would guide you in the right direction.
@Donnerbart Donnerbart self-assigned this Oct 17, 2017
@Donnerbart
Copy link
Contributor

I'm having a look at this right now. I have two improvements in mind:

  • if the versions are rolling upgrade compatible (just one minor version difference), we should print that this requires EE
  • if the versions are not rolling upgrade compatible, we should inform the user about that

@Holmistr
Copy link
Contributor Author

+1

@Donnerbart Donnerbart mentioned this issue Oct 17, 2017
Merged
@Donnerbart Donnerbart added this to the 3.10 milestone Oct 18, 2017
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Donnerbart Donnerbart

Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Projects
None yet
Milestone
3.10
Development

Successfully merging a pull request may close this issue.

Improved message of VersionMismatchException in validateJoinRequest()
3 participants
@Donnerbart @Holmistr @mmedenjak