"Saved Object conflict" adding System or Windows Integrations

Elastic Stack Elastic Agent
,
1

Created a new cluster on Elastic Cloud running 8.14.3 (no agents deployed yet), but when creating new policy and leaving the "system" checkbox enabled, the policy gets created without the system integration. When trying to manually add the System integration, I get the following error:

Saved Object conflict encountered when installing system-1.60.2. There may be conflicting Saved Object saved to another Space. Original error: Saved object [tag/fleet-manage-default] conflict.

Similar error when installing Windows integration:

Saved Object conflict encountered when installing windows-1.47.0. There may be conflicting Saved Object saved to another Space. Original error: Saved object [tag/fleet-windows-default] conflict.

Other integratsions (Defend, OSQuery, Custom Windows Event Logs, etc.) seem to install without error.

I found that if I delete my "Client Space", which only provides to all indexes (*) and Kibana dashboards (also imported the custom dashboards), everything works fine. So, I tried giving access to all features in the Client Space, but still the same errors.

Why do these two integrations have issues, but the others don't? As I said this is a completely new cluster - no logs coming in yet, just initial configuration. Is this a bug?

2

Hi,
We had a few fixes related to Saved object conflicts, I'm not seeing any open bug in 8.14.
Can you try to manually delete those tags that appear in the error message? Probably the tags are in the non-default space.

3

The tags don't actually appear to have been created when the failure occurs. The only solution that worked was to delete the additional "Client" space. Then installing the integrations works, and I re-created the space.