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

[DOCS] [Monitoring] Document License Change Impact #20937

Closed
pickypg opened this issue Jul 18, 2018 · 4 comments
Closed

[DOCS] [Monitoring] Document License Change Impact #20937

pickypg opened this issue Jul 18, 2018 · 4 comments

Comments

@pickypg
Copy link
Member

pickypg commented Jul 18, 2018

Due to the changing of how licensing worked in 6.3, versus earlier releases of 6.x, it had an impact on the pre-6.3 Monitoring UI's ability to display 6.3+ clusters. (Lots of versions here, but suffice to say that 6.0 - 6.2 monitoring UI cannot display 6.3+ clusters)

We have always said that the monitoring cluster should be upgraded first, but it may catch people off guard that it claims a licensing issue. As such, I am not really sure what all or even where we would want to document this since it's not really a breaking change due to that requirement. It may be enough to just have this issue and close it.

@pickypg
Copy link
Member Author

pickypg commented Jul 18, 2018

/cc @lcawl @GlenRSmith

@lcawl
Copy link
Contributor

lcawl commented Jul 18, 2018

@pickypg When you say it claims a licensing issue, do you mean that there are particular (licensing) errors that occur? If so, we could create troubleshooting information for those errors.

@pickypg
Copy link
Member Author

pickypg commented Jul 18, 2018

Yes, it should show a banner error (along the top):

You can't view the "${this.props.cluster_name}" cluster because the license information is invalid.

Naturally the variable would be replaced. That's the tip off that it's happening here.

@lcawl
Copy link
Contributor

lcawl commented Jul 18, 2018

There's a troubleshooting page being created for #18958 so this could be added there.

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