-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fix interactive Setup UI never reaches Finished state #165273
Fix interactive Setup UI never reaches Finished state #165273
Conversation
Pinging @elastic/kibana-security (Team:Security) |
…com/thomheymann/kibana into fix-post-interactive-setup-redirect
@@ -13,6 +13,7 @@ export default function ({ loadTestFile }: FtrProviderContext) { | |||
loadTestFile(require.resolve('./management')); | |||
|
|||
// platform security | |||
loadTestFile(require.resolve('./security/api_keys')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test suite was added as part of #164886 but was not referenced correctly so never got executed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
…t-interactive-setup-redirect
💚 Build Succeeded
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as expected.
@@ -13,6 +13,7 @@ export default function ({ loadTestFile }: FtrProviderContext) { | |||
loadTestFile(require.resolve('./management')); | |||
|
|||
// platform security | |||
loadTestFile(require.resolve('./security/api_keys')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
Resolves #162518
This PR updates the logic that detects whether Kibana has booted correctly during interactive setup.
The issue described in #162518 was a false positive and only effected Kibana when run in development mode.
We already have end-to-end tests which go through the entire enrollment flow and ensure that Kibana correctly redirects to the login page once interactive setup completes:
https://github.com/elastic/kibana/blob/main/test/interactive_setup_functional/tests/enrollment_token.ts#L78-L81
These tests passed with both the previous and the updated logic. However, the end-to-end tests do not check development mode which is why the build never failed and we started seeing this issue.