[Fleet]: Saved object conflict error is displayed while adding integration in default space when My first agent policy is created under Space2.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.16.0 SNAPSHOT
BUILD: 78702
COMMIT: 2a12f68d66ed1cbc422f8a92f751d1d6e4c02bdc

Preconditions:

1. 8.16.0-SNAPSHOT Kibana cloud environment should be available.
2. Multiple spaces should be created.
3. No agent should be installed.

Steps to reproduce:

1. Login to the fresh 8.16.0 SNAPSHOT.
2. Navigate to Space2 and go to Integrations>Nginx>Add integration.
3. Observe My first agent policy is generated in Space2.
4. Navigate to Default space and go to Integrations>Nginx>Add integration.
5. Observe error: Saved object [fleet-agent-policies/fleet-first-agent-policy] conflict.

Expected Result:
Saved object conflict error should be handled while adding integration in default space when My first agent policy is created under Space2.

• User should be able to add integration to agent policy from Default space when My first agent policy is created under Space2.

Screen Recording:

Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2024-10-03.11-25-39.mp4

Feature:
https://github.com/elastic/ingest-dev/issues/1664

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@muskangulati-qasource Please review.

[muskangulati-qasource]

Secondary review is Done for this ticket!

[jen-huang]

This will be fixed with #194350. Closing as a dupe of #182736. Please revalidate when that PR has merged and available in a build. Thanks!

[amolnater-qasource]

Hi Team,

We have revalidated this issue on latest 8.16.0 SNAPSHOT and found it fixed now.

Observations:

• User is able to add integration to agent policy from Default space when My first agent policy is created under Space2.

Build details:
VERSION: 8.16.0 SNAPSHOT
BUILD: 78885
COMMIT: 4e4107b

Screen Recording

Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2024-10-07.12-38-36.mp4

Hence, we are marking this issue as QA:Validated.

Thanks!!