[Fleet]: Reset to policy button sets the logging level to info, when agent policy logging level is set to error.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.15.0 SNAPSHOT
BUILD: 75123
COMMIT: 6e3b14fa19be367e2c29c32b56399729be3260bf

Preconditions:

1. 8.15.0-SNAPSHOT Kibana cloud environment should be available.
2. An agent should be installed.

Steps to reproduce:

1. Navigate to Edit Agent policies tab.
2. Change logging level to error.
3. Navigate to Agent logs tab and set logging level to debug.
4. Wait for sometime till the changes gets updated.
5. Now click Reset to policy and observe logging level is now set to info.

Expected Result:
Reset to policy button should sets the logging level to error(as per the selection under Agent policy), when agent policy logging level is set to error.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-06-07.15-16-37.mp4

Feature:
#158861

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[jen-huang]

After reviewing the video, this is due to the bug elastic/elastic-agent#4747. Since Elastic Agent is reporting its log level incorrectly, we can't select the correct initial level for the dropdown. Closing as duplicate. @amolnater-qasource please validate this scenario when that bug is fixed. Thanks :)

[amolnater-qasource]

Hi Team,

We have revalidated this issue on latest 8.15.0 SNAPSHOT kibana cloud environment and found it fixed now:

Observations:

• Reset to policy button sets the logging level to policy level.

Screen Recording:

ip-172-31-80-23.-.Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-06-24.13-01-27.mp4

Build details:
VERSION: 8.15.0 SNAPSHOT
BUILD: 75634
COMMIT: 6c36d72

Hence we are marking this issue as QA:Validated.

Thanks!