Your window into the Elastic Stack
Find a file
Jill Guyonnet 2dba27e8ba
[Fleet] Add automatic agent upgrades functional tests (#220829)
## Summary

Closes https://github.com/elastic/ingest-dev/issues/5303

This PR adds functional tests for automatic upgrades of Fleet agents.

The test cases aim to cover the logic of whether agents should be
upgraded or not in a single run.

I noticed some rare flakiness when running these tests locally, hence
the few Flaky Test Runner runs. Since these all passed, I am leaving the
task interval and sleep parameters as is for now (with a comment in case
flakiness does happen).

Running:
```
yarn test:ftr:server --config x-pack/test/fleet_tasks/config.ts
```
```
yarn test:ftr:runner --config x-pack/test/fleet_tasks/config.ts
```

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- 🟢 25 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8264
- 🟢 100 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8265
- 🟢 100 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8267
- 🟢 100 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8268
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

No impact on functionality. Risk of functional tests flakiness.

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-05-20 09:33:23 +02:00
.buildkite [Fleet] Add automatic agent upgrades functional tests (#220829) 2025-05-20 09:33:23 +02:00
.devcontainer
.github [Fleet] Add automatic agent upgrades functional tests (#220829) 2025-05-20 09:33:23 +02:00
api_docs
config
dev_docs
docs
examples
kbn_pm
legacy_rfcs
licenses
oas_docs
packages
plugins
scripts
src Update dependency diff to v8 (main) (#220898) 2025-05-20 01:05:23 -03:00
typings
x-pack [Fleet] Add automatic agent upgrades functional tests (#220829) 2025-05-20 09:33:23 +02:00
.backportrc.json
.bazelignore
.bazeliskversion
.bazelrc
.bazelrc.common
.bazelversion
.browserslistrc
.editorconfig
.eslintignore
.eslintrc.js
.gitattributes
.gitignore
.i18nrc.json
.node-version
.npmrc
.nvmrc
.prettierignore
.prettierrc
.puppeteerrc
.stylelintignore
.stylelintrc
.telemetryrc.json
.yarnrc
BUILD.bazel
catalog-info.yaml
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md
fleet_packages.json
github_checks_reporter.json
kibana.d.ts
LICENSE.txt
NOTICE.txt
package.json Update dependency diff to v8 (main) (#220898) 2025-05-20 01:05:23 -03:00
preinstall_check.js
README.md
renovate.json Update dependency diff to v8 (main) (#220898) 2025-05-20 01:05:23 -03:00
RISK_MATRIX.mdx
run_fleet_setup_parallel.sh
SECURITY.md
sonar-project.properties
STYLEGUIDE.mdx
tsconfig.base.json
tsconfig.browser.json
tsconfig.browser_bazel.json
tsconfig.json
TYPESCRIPT.md
updatecli-compose.yaml
versions.json
WORKSPACE.bazel
yarn.lock Update dependency diff to v8 (main) (#220898) 2025-05-20 01:05:23 -03:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.

Getting Started

If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.

If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.

Using a Kibana Release

If you want to use a Kibana release in production, give it a test run, or just play around:

Building and Running Kibana, and/or Contributing Code

You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

Documentation

Visit Elastic.co for the full Kibana documentation.

For information about building the documentation, see the README in elastic/docs.

Version Compatibility with Elasticsearch

Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.

Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.

Situation Example Kibana version Example ES version Outcome
Versions are the same. 7.15.1 7.15.1 💚 OK
ES patch number is newer. 7.15.0 7.15.1 ⚠️ Logged warning
ES minor number is newer. 7.14.2 7.15.0 ⚠️ Logged warning
ES major number is newer. 7.15.1 8.0.0 🚫 Fatal error
ES patch number is older. 7.15.1 7.15.0 ⚠️ Logged warning
ES minor number is older. 7.15.1 7.14.2 🚫 Fatal error
ES major number is older. 8.0.0 7.15.1 🚫 Fatal error

Questions? Problems? Suggestions?

  • If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
  • Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.