[Fleet][Agentless] Agentless host stuck in pending state with okta integration when new fleet server is set to default and agentless policy has old default values

[harshitgupta-qasource]

Kibana Build details:

VERSION: 9.1.0 SNAPSHOT
BUILD: 86565
COMMIT: b6c788655a044c70d9bce8545823669d3471361b

Preconditions:

1. 9.1.0 or above Kibana should be available.
2. Agent Policy should be created.
3. Default fleet server and elasticsearch are installed only

Steps to reproduce:

1. Navigate to the Integrations tab.
2. Search for Okta integration and open it.
3. Set the deployment option to Agentless.
4. Provide the Okta System Log API URL and API Key.
5. Click on Save policy observe host is installed.
6. Now, add a new Fleet Server and mark it as default.
7. Again, try adding Agentless with Okta integration.
8. Observe that a new policy for serverless is created.
9. However, the Agentless host is not installed and gets stuck in the pending state.
10. Also, the serverless policy continues to reflect the old default Fleet Server and Elasticsearch values.

Expected Results

• Agentless host should not stuck in pending state with okta integration with actual default values.

Screen-shot

Agent Policy for Okta 3

elastic-agent.zip

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[harshitgupta-qasource]

@amolnater-qasource Kindly review

[amolnater-qasource]

Secondary review is Done for this ticket!