Agent remains in 'Healthy' status on updating the agent policy

[ghost]

Kibana version:
Kibana: 8.0.0-SNAPSHOT Kibana cloud environment

Elasticsearch version:
Elasticsearch: 8.0.0-SNAPSHOT cloud environment

Host OS and Browser version:
Windows x64, All

Original install method (e.g. download page, yum, from source, etc.):
8.0.0-SNAPSHOT Kibana cloud environment from https://staging.found.no

Description
Agent remains in 'Healthy' status on updating the agent policy

Preconditions

1. 8.0.0-SNAPSHOT Kibana cloud environment(with commit f2d961d) should be available.
2. Login into the above Kibana environment with 'elastic' superuser.
3. 8.0.0-SNAPSHOT version windows-x86_64.zip agent should be installed with Default policy(having System Integration) on above kibana :-
   Agent download location: https://snapshots.elastic.co/8.0.0-5823f363/downloads/beats/elastic-agent/elastic-agent-8.0.0-SNAPSHOT-windows-x86_64.zip
4. A new policy(say rahul_new_policy) should exist with System and Endpoint Integration.

Steps to Reproduce

1. Open the left hand menu and click 'Fleet' link under Management.
2. Navigate to Agents tab in Kibana and observe that agent is in Healthy status.
3. In second tab, navigate to Policies tab and click on Default policy.
4. Navigate to 'Settings' tab and update the policy description.
5. Navigate back to first tab and observe that 'Updating' status is not displayed for the prerequisite agent.

Test data
N/A

Impacted Test case id
https://elastic.testrail.io/index.php?/cases/view/35208

Actual Result
Agent remains in 'Healthy' status on updating the agent policy.

Expected Result
'Updating' status should be displayed on updating the agent policy (as per hbharding comment #81872 (comment))

What's working

• N/A

What's not working

• Issue is also occurring on changing the policy to 'rahul_new_policy' for the prerequisite agent.

Screenshot
Agent remains in 'Healthy' status on updating the agent policy

Logs
N/A

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[ghost]

@manishgupta-qasource Please review the bug

[manishgupta-qasource]

Reviewed & Assigned to @EricDavisX

[EricDavisX]

@nchaulet if you don't want to poke this issue you can un-assign / re-assign the issue - thanks for help. @hbharding also. Guys, do we think this part of the design was implemented?

[nchaulet]

@EricDavisX the scope of status changed a little with the introduction of Fleet Server and it's currently not possible to report updating status when we update the agent policy, it's going to change when we move to Fleet server and we should keep this in mind.

[EricDavisX]

Thanks. The QA team knows this status as 'closed, wont fix' - we can keep the test case for later and will re-test it as such when Fleet Server is ready for deeper QA.