Open kibanamachine opened 2 years ago
Pinging @elastic/fleet (Team:Fleet)
New failure: CI Build - 8.1
New failure: CI Build - 8.2
This, https://github.com/elastic/kibana/issues/124780, https://github.com/elastic/kibana/issues/134529, and https://github.com/elastic/kibana/issues/124781 all seem to be caused because the docker registry still fails to start for some reason:
{
"ecs": {
"version": "8.0.0"
},
"@timestamp": "2022-06-15T17:15:41.721-04:00",
"message": "[Elastic Cloud agent policy 0001] could not be added. [fleet_server] could not be installed due to error: [PackageNotFoundError: [fleet_server] package not found in registry]",
"error": {
"message": "[Elastic Cloud agent policy 0001] could not be added. [fleet_server] could not be installed due to error: [PackageNotFoundError: [fleet_server] package not found in registry]",
"type": "Error",
"stack_trace": "Error: [Elastic Cloud agent policy 0001] could not be added. [fleet_server] could not be installed due to error: [PackageNotFoundError: [fleet_server] package not found in registry]\n at /var/lib/buildkite-agent/builds/kb-n2-4-spot-ec638bb99f0408cd/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/services/preconfiguration.ts:212:21\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async Promise.all (index 0)\n at ensurePreconfiguredPackagesAndPolicies (/var/lib/buildkite-agent/builds/kb-n2-4-spot-ec638bb99f0408cd/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/services/preconfiguration.ts:202:40)\n at createSetupSideEffects (/var/lib/buildkite-agent/builds/kb-n2-4-spot-ec638bb99f0408cd/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/services/setup.ts:105:5)\n at awaitIfPending (/var/lib/buildkite-agent/builds/kb-n2-4-spot-ec638bb99f0408cd/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/services/setup_utils.ts:30:20)\n at /var/lib/buildkite-agent/builds/kb-n2-4-spot-ec638bb99f0408cd/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/plugin.ts:415:9"
},
"log": {
"level": "WARN",
"logger": "plugins.fleet"
},
"process": {
"pid": 2757
}
}
...
Setup failed: {
"level": "available",
"summary": "Fleet setup failed",
"meta": {
"error": "[Elastic Cloud agent policy 0001] could not be added. [fleet_server] could not be installed due to error: [PackageNotFoundError: [fleet_server] package not found in registry]"
}
}
Do you think there is more we can do to avoid this @jen-huang? Is there still an external dependency here? I thought we had the registry running locally now. Can packages still just disappear randomly?
@spalger We do have registry running locally but it pulls from docker.elastic.co
so that would be the external dependency. We do a custom way of spinning up this docker image as it's not from within functional tests runner:
https://github.com/elastic/kibana/blob/95d3090f1ae714ffdf6d239e6fad4aeabe29d924/x-pack/plugins/fleet/server/integration_tests/helpers/docker_registry_helper.ts
@nchaulet Two questions:
kbn-test
instead of rolling our own? https://github.com/elastic/kibana/tree/main/packages/kbn-test/src/functional_test_runner/lib/docker_serverswaitForLogLine: 'package manifests loaded'
configuration in our version in conjunction with or replacing our current timeouts and retries?cc @kpollich
@nchaulet Two questions:
waitForLogLine
it will be an easy change and probably more robust Flakiness should be better after #136438.
New failure: CI Build - main
New failure: CI Build - 8.5
New failure: CI Build - 8.6
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
failed due to https://github.com/elastic/kibana/pull/161343
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
Kibana never came up in CI. False positives in most recent runs.
New failure: CI Build - main
A test failed on a tracked branch
First failure: CI Build - main