Fleet / Osquery Manager: Can not upgrade package - concurrent installation detected #153212
Comments
ceeeekay
added
the
bug
|
Hi there, just confirming this is still an issue in Kibana Osquery Kibana log errors are the same as those in |
jen-huang
added
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
|
I can confirm we still have this issue on Elastic-Stack 8.8.1. We have several Kibana Spaces but use the integration just in one space. However, under saved objects in each space its a complete mess. There are several objects, some old some new but all from the Windows or System integration. I'm currently trying to delete objects in all spaces but the integration is appearing everywhere again and its a pain to fix this. We have 2 kibana and 7 elasticsearch nodes. Not sure where this issue comes from i dont suspect manual intervention but more an issue while upgraing the nodes or the integration. some logs inform about Error: Non-unique import objects detected
other interesting log is:
|
|
Related to #161804 |
|
This is similar to #171986. |
|
As the error was This seems to be another instance of #171986 and should be fixed with #173190. @kpollich do you think we can close it? |
Kibana version: 8.6.2
Elasticsearch version: 8.6.2
Package registry Docker image: 8.6.2
Server OS version: Ubuntu 22.04.2
Browser version: na
Browser OS version: n/a
Original install method (e.g. download page, yum, from source, etc.): apt
Describe the bug: I have an air-gapped install using the Elastic Docker image for the Fleet package registry. The Docker container is running on the same node as Kibana. I'm able to browse and install integrations from the locally hosted registry.
However, In the settings page for the Osquery Manager integration it's stuck on 1.5.1 and is claiming there is a 1.6.0 upgrade available, but the upgrade button is just spinning its wheel endlessly (as in, it's been like this for weeks). Other integrations can be upgraded with no problem. As far as I can tell it's only the Osquery integration which has this issue.
Steps to reproduce:
I'm unsure exactly how to reproduce this as I have no idea how it got into this condition.
Expected behavior:
Osquery integration upgrade button should be clickable and no errors in the logs.
Screenshots (if relevant):
Oqsuery integration will not upgrade
Other integrations are fine
Errors in browser console (if relevant): n/a
Provide logs and/or server output (if relevant):
[2023-03-15T11:54:14.640+13:00][WARN ][plugins.fleet] large amount of default fields detected for index template logs-osquery_manager.result in package osquery_manager, applying the first 1024 fields[2023-03-15T11:54:17.503+13:00][WARN ][plugins.fleet] Failure to install package [osquery_manager]: [ConcurrentInstallOperationError: Concurrent installation or upgrade of osquery_manager-1.6.0 detected, aborting. Original error: Saved object [tag/fleet-managed-kelp-admin] conflict][2023-03-15T11:54:17.877+13:00][INFO ][plugins.osquery] Updating osquery_manager integration[2023-03-15T11:54:17.906+13:00][WARN ][plugins.fleet] Failure to install package [osquery_manager]: [ConcurrentInstallOperationError: Concurrent installation or upgrade of osquery_manager-1.6.0 detected, aborting.][2023-03-15T11:54:17.907+13:00][INFO ][plugins.osquery] osquery_manager integration updatedThe text was updated successfully, but these errors were encountered: