Fleet server permanently goes offline on assigning to the new policy not having Fleet Server integration.

[harshitgupta-qasource]

Kibana Build details:

VERSION: 8.8 BC5 Kibana cloud environment
BUILD: 63092
COMMIT: ba9b182a3422f5e162c1ca74baafb91833eca059

Host OS and Browser version: All, All
Preconditions:

1. 8.8 BC5 Kibana cloud environment should be available.
2. Fleet server should be installed manually using Fleet Server policy having Fleet server integration.

Steps to reproduce:

1. Navigate to the Fleet tab.

2. Select the installed fleet server agent and assign it to a new policy not having fleet server integration.

3. Assign the fleet server back to the policy with Fleet server integration.

4. Observe the fleet server remains offline permanently.

Expected:
Fleet server should get back healthy on assigning back to the policy having Fleet Server integration.

Note:

• This issue is reproducible on all OSs.

Screencast:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2023-05-18.11-07-17.mp4

Screen-shot

• On assigning back to the policy having Fleet Server integration
  

• Relates Fleet server permanently goes offline on assigning to the new policy not having Fleet Server integration. #2603

[harshitgupta-qasource]

@amolnater-qasource Kindly review

[amolnater-qasource]

Secondary review for this ticket is Done.

[jlind23]

@michel-laterman I guess this is the expected behaviour right?

[juliaElastic]

I think we said on the QA sync last week that it is expected that the agent comes back online after reassigning it to the right policy, we should investigate why it stays offline. Though it is not likely that users intentionally reassign a Fleet Server to a regular policy.

[michel-laterman]

@jlind23 yes, if that was the only fleet-server running then it's expected behaviour.

If we have a single fleet-server running, and assign it to a policy that stops fleet-server no more policies will be dispatched and eventually all agents will appear offline

[jlind23]

thanks @michel-laterman @harshitgupta-qasource I believe we can close this as won't fix then.

[harshitgupta-qasource]

Hi Team,

Thank you for confirming the expected behavior. Hence, we are closing this issue.

Thanks!!