Inconsistent Fleet Behavior when Removing Configurations from kibana.yml for Managed Agent Policies #193407
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Fleet
Team label for Observability Data Collection Fleet team
Kibana version: latest (8.15)
Elasticsearch version: latest (8.15)
Describe the bug:
We observed inconsistency in Fleet’s behavior when removing configurations from
kibana.yml
, specifically for managed Agent policies.First we configured a Fleet Host, Fleet output, and a managed Agent Policy (using the host and output) through the
kibana.yml
. After starting Kibana we removed these configurations fromkibana.yml
.After removing the Fleet Host and Fleet output configurations, the Agent policy remains, but the Fleet Host and Fleet output are deleted. This leads to the Fleet UI failing since the Agent policy references non-existing Fleet Host and output.
Steps to Reproduce:
kibana.yml
with a managed Agent policy, Fleet Host, and Fleet output.kibana.yml
.kibana.yml
kibana.yml example
Expected Behavior:
kibana.yml
which result with their deletion in Kibana, should result with removal of references to this host and output from managed agent policies, just like it works for non-managed agent policies. They should be replaced with the default fleet host and output.Screenshots (if relevant):
Provide logs and/or server output (if relevant):
Details
Any additional context:
This bug was discovered as part of an expected migration of agentless on serverless from using preconfigured (
kibana.yml
) agent policy to using the agentless API.cc @kpollich @nchaulet
The text was updated successfully, but these errors were encountered: