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

Config setting 'server.defaultRoute' ignored #52076

Closed
peterpramb opened this issue Dec 3, 2019 · 4 comments · Fixed by #52308
Closed

Config setting 'server.defaultRoute' ignored #52076

peterpramb opened this issue Dec 3, 2019 · 4 comments · Fixed by #52308
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@peterpramb
Copy link

Kibana version:
7.5.0

Elasticsearch version:
7.5.0

Server OS version:
RHEL 7.6

Original install method (e.g. download page, yum, from source, etc.):
Download

Describe the bug:
According to #44678 an available config setting server.defaultRoute should be automatically mapped to an UI's advanced setting. Unfortunately this is not the case, and the setting is ignored alltogether, letting Kibana start with just the default route.

Additionally server.defaultRoute is gone alltogether from the documentation (https://www.elastic.co/guide/en/kibana/master/settings.html) without being mentioned in Breaking Changes.

Steps to reproduce:

  1. Set in Kibana config: server.defaultRoute: "/app/monitoring"
  2. Login in to Kibana: Start application is /app/kibana
  3. Advanced settings show: defaultRoute = /app/kibana

Expected behavior:
Kibana starts with /app/monitoring

Screenshots (if relevant):
Screenshot from 2019-12-03 16-23-53

@streamich streamich added bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! triaged labels Dec 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego
Copy link
Member

legrego commented Dec 6, 2019

@peterpramb,

Thanks so much for the bug report, and I'm sorry this ended up causing you problems. @restrry identified the issue and has merged a fix, which will be available in the 7.5.1 release.

Additionally server.defaultRoute is gone alltogether from the documentation (elastic.co/guide/en/kibana/master/settings.html) without being mentioned in Breaking Changes.

We migrated server.defaultRoute to uiSettings.overrides.defaultRoute in 7.5.0, so that it behaves in a way that does not introduce breaking changes. I wanted to remove it from the documentation so that folks just getting started don't end up configuring Kibana in a way that won't work in the near future.
Perhaps the more pragmatic solution would have been to keep the setting in the docs, but mark it as deprecated instead for the remainder of 7.x.

#46787 will introduce the actual breaking change of not supporting server.defaultRoute altogether. We do our best to reserve breaking changes for major version releases, so expect #46787 to happen for 8.0.0

@legrego
Copy link
Member

legrego commented Dec 6, 2019

Workaround

For anyone else running into this for 7.5.0 before 7.5.1 is available:

You can workaround this by changing server.defaultRoute to uiSettings.overrides.defaultRoute in your kibana.yml file:

# before
server.defaultRoute: /app/monitoring
# after
uiSettings.overrides.defaultRoute: /app/monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants