-
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
[Fleet] Integrations API endpoint /api/fleet/epm/packages returns different data randomly #166921
Comments
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as |
Pinging @elastic/fleet (Feature:EPM) |
One thing that comes to mind is that in 8.6.0 we introduced a change in the way we get the information from registry or archive (PR), so it would be interesting to know if it still happens in newer versions. @amolnater-qasource could you try reproducing this bug on latest version? We are not sure if it's still occurring. |
Hi @criamico We have revalidated this issue on latest 8.11.0 and 8.12.0 SNAPSHOT kibana cloud environment and found it not reproducible there. Observations:
Screen Recording: r.kb.europe-west1.gcp.cloud.es.io_9243_api_fleet_epm_packages_excludeInstallStatus.false.-.Google.Chrome.2023-11-10.15-19-37.mp48.12.0: s.kb.us-west2.gcp.elastic-cloud.com_9243_api_fleet_epm_packages_excludeInstallStatus.false.-.Google.Chrome.2023-11-10.15-39-45.mp4Build details: Please let us know if anything else is required from our end. |
Thanks @amolnater-qasource and @criamico for chiming in. Closing this as not reproducible then. |
The Fleet API endpoint for integrations randomly returns different data regarding available integrations.
No apparent cause of even pattern is obvious.
URI example: /api/fleet/epm/packages?excludeInstallStatus=false
Response examples isolated to the 1password integration simply for sanity.
1password is installed on this deployment.
This request confirms it, 1.6.0 is available and we have it installed.
But a subsequent request to the same endpoint with the parameters returns this, where it claims that 1password is NOT installed even though it is.
This also results in the Kibana webUI randomly listing integrations as available for upgrade, then not listing them on next page refresh/navigation event.
We are on version 8.3.2, this issue has existed in all 8.x versions that we have used, I am only just now working out what the actual cause is at this API level.
The text was updated successfully, but these errors were encountered: