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.

Sign up for GitHub

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

Jump to bottom

Failing test: X-Pack EPM API Integration Tests.x-pack/test/fleet_api_integration/apis/epm/get·ts - EPM Endpoints EPM - get Installed Packages Allows the fetching of installed packages #163203

Closed
kibanamachine opened this issue Aug 4, 2023 · 9 comments · Fixed by #174679
Closed

Failing test: X-Pack EPM API Integration Tests.x-pack/test/fleet_api_integration/apis/epm/get·ts - EPM Endpoints EPM - get Installed Packages Allows the fetching of installed packages #163203

kibanamachine opened this issue Aug 4, 2023 · 9 comments · Fixed by #174679
Assignees
@juliaElastic
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 Aug 4, 2023 •
edited
Loading

A test failed on a tracked branch

Error: expected 2 to equal 3
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at Context.<anonymous> (get.ts:126:36)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Aug 4, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 4, 2023
@mistic mistic added the Team:Fleet Team label for Observability Data Collection Fleet team label Aug 4, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Aug 4, 2023
@hop-dev hop-dev self-assigned this Aug 23, 2023
@hop-dev hop-dev mentioned this issue Aug 23, 2023
Merged
@hop-dev
Copy link
Contributor

hop-dev commented Aug 23, 2023 •
edited
Loading 

 proc [kibana] [2023-08-04T18:52:25.527+00:00][ERROR][plugins.fleet] Failed to fetch latest version of endpoint from registry: Error connecting to package registry: request to http://localhost:6104/search?package=endpoint&prerelease=false&kibana.version=8.10.0 failed, reason: connect ECONNREFUSED 127.0.0.1:6104
2023-08-04 19:52:25 BST	 proc [kibana] [2023-08-04T18:52:25.527+00:00][DEBUG][plugins.fleet] kicking off bulk install of endpoint
2023-08-04 19:52:25 BST	 proc [kibana] [2023-08-04T18:52:25.528+00:00][WARN ][plugins.fleet] Failed installing package [endpoint] due to error: [PackageNotFoundError: [endpoint] package not found in registry]

It looks like the endpoint package failed to install because we are looking for it in the registry. endpoint is a bundled package so we should never be searching for it in the registry, I can only think that something went wrong with the bundling here?

I have a PR to make the assertion in the test more granular, then we can confirm that it is endpoint if this failure happens again and investigate further.

@hop-dev hop-dev closed this as completed Aug 23, 2023
hop-dev added a commit that referenced this issue Aug 23, 2023
@hop-dev
[Fleet] Make fetch installed packages test assertions more granular (#…
40ba6b6 
…164567)

## Summary

For investigating #163203 I want
to double check which package is not being returned.
@kibanamachine kibanamachine reopened this Sep 18, 2023
@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

mistic added a commit that referenced this issue Nov 15, 2023
@mistic
skip flaky suite (#163203)
46322ce
@mistic
Copy link
Member

mistic commented Nov 15, 2023

Skipped.

main: 46322ce

This was referenced Jan 11, 2024
Merged
Closed
@juliaElastic juliaElastic self-assigned this Jan 15, 2024
juliaElastic added a commit that referenced this issue Jan 15, 2024
@juliaElastic
[Fleet] enabling flaky tests with endpoint (#174679)
247b8d1 
## Summary

Closes #163203
Closes #167188
Closes #156941

Enable flaky tests, using endpoint-8.6.1 as a fixture bundled package.
See discussion:
#167188 (comment)

Closes #170690
The es error was reproducible with an API request to index a document. I
had a look at the data stream mappings, and experimented with providing
values for the other keyword `time_series_dimension` fields. It seems
the issue is fixed by providing value for one more field.
@kibanamachine kibanamachine reopened this Feb 21, 2024
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kpollich
Copy link
Member

No failures since February. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juliaElastic juliaElastic

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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Fleet] enabling flaky tests with endpoint juliaElastic/kibana
6 participants
@hop-dev @mistic @kpollich @elasticmachine @kibanamachine @juliaElastic