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

Failing test: Jest Integration Tests.x-pack/plugins/fleet/server/integration_tests - Fleet setup preconfiguration with multiple instances Kibana preconfiguration setup sets up Fleet correctly with single Kibana instance #142495

Closed
kibanamachine opened this issue Oct 3, 2022 · 14 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 3, 2022

A test failed on a tracked branch

Error: Command failed with exit code 1: docker pull docker.elastic.co/package-registry/distribution:production-v2-experimental
Error response from daemon: Get "https://docker.elastic.co/v2/": dial tcp 34.68.230.202:443: connect: connection refused
    at makeError (/var/lib/buildkite-agent/builds/kb-n2-4-spot-09dbf37f8e4c1477/elastic/kibana-on-merge/kibana/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/var/lib/buildkite-agent/builds/kb-n2-4-spot-09dbf37f8e4c1477/elastic/kibana-on-merge/kibana/node_modules/execa/index.js:114:26)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at pullDockerImage (/var/lib/buildkite-agent/builds/kb-n2-4-spot-09dbf37f8e4c1477/elastic/kibana-on-merge/kibana/x-pack/plugins/fleet/server/integration_tests/helpers/docker_registry_helper.ts:97:5)
    at RetryOperation._fn (/var/lib/buildkite-agent/builds/kb-n2-4-spot-09dbf37f8e4c1477/elastic/kibana-on-merge/kibana/node_modules/p-retry/index.js:50:12)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 3, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 3, 2022
@mistic mistic added the Team:Fleet Team label for Observability Data Collection Fleet team label Oct 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 3, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kpollich
Copy link
Member

kpollich commented Dec 5, 2022

Fixed by #146673

@kpollich kpollich closed this as completed Dec 5, 2022
@kibanamachine kibanamachine reopened this Dec 7, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@jen-huang
Copy link
Contributor

Intermittent issue, #147139 will help as it is a reduced distribution size. Closing for now, let's see if it pops back up.

@jen-huang jen-huang closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 2023
@kibanamachine kibanamachine reopened this Feb 3, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.6

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@juliaElastic
Copy link
Contributor

failed due to #161343

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kpollich
Copy link
Member

Sep 29 false positives

@kpollich kpollich closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

6 participants