Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fleet] Kibana ignores new values of xpack.fleet.agent.* keys in the config #105400

Closed
david-kow opened this issue Jul 13, 2021 · 9 comments · Fixed by #135669
Closed

[Fleet] Kibana ignores new values of xpack.fleet.agent.* keys in the config #105400

david-kow opened this issue Jul 13, 2021 · 9 comments · Fixed by #135669
Assignees
Labels
bug Fixes for quality problems that affect the customer experience QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@david-kow
Copy link

Kibana version: 7.14.0-SNAPSHOT

Elasticsearch version: 7.14.0-SNAPSHOT

Original install method (e.g. download page, yum, from source, etc.): ECK

Describe the bug:

The settings specified with the below keys are not updated when Kibana restarts.

xpack.fleet.agents.elasticsearch.host: https://elasticsearch.default.svc:9200
xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server.default.svc:8220"]

Steps to reproduce:

  1. Start Kibana with invalid values of xpack.fleet.agents.elasticsearch.host and xpack.fleet.agents.fleet_server.hosts, e.g.:
xpack.fleet.agents.elasticsearch.host: https://bad.svc:9200
xpack.fleet.agents.fleet_server.hosts: ["https://bad.svc:8220"]
  1. Fix values of above settings and restart Kibana, e.g.:
xpack.fleet.agents.elasticsearch.host: https://elasticsearch-test-es-http.default.svc:9200
xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-test-agent-http.default.svc:8220"]
  1. Elastic Agents will still try to use old (invalid) setting values. This is visible both in Elastic Agent logs and in the Kibana UI (Fleet > Settings flyout).

Expected behavior:

Kibana should apply the updated values from the config file.

@david-kow david-kow added the bug Fixes for quality problems that affect the customer experience label Jul 13, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 13, 2021
@mostlyjason mostlyjason added Team:Fleet Team label for Observability Data Collection Fleet team and removed needs-team Issues missing a team label labels Jul 20, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@jen-huang
Copy link
Contributor

I think this is by design right now as we save the kibana.yml value into Fleet settings, which can then be updated from the UI. So how do we know when to reapply new kibana.yml values?

cc @nchaulet thoughts on this?

@jen-huang jen-huang changed the title Kibana ignores new values of xpack.fleet.agent.* keys in the config [Fleet] Kibana ignores new values of xpack.fleet.agent.* keys in the config Jul 20, 2021
@joshdover
Copy link
Contributor

@nchaulet have we fixed these issues in preconfiguration by now?

@nchaulet
Copy link
Member

nchaulet commented Jun 9, 2022

@joshdover we fixed the preconfigured policies and output but not the default value for xpack.fleet.agents.fleet_server.hosts it should probably be the same as policies if a value is defined in the config it could not be removed from the UI and we should add new values

@joshdover
Copy link
Contributor

@jen-huang Can we have this prioritized as a papercut item for 8.4? It's likely to be higher prio than some of the others.

@ghost
Copy link

ghost commented Jul 6, 2022

Hi Team
We have tested this issue on the self-managed 8.3.1 release build and observed that the issue is reproducible. Please find below the testing details :

Screenshot:
dddddd

Build Details:
VERSION: 8.3.1
BUILD: 53549
COMMIT: a4f8dc6

We will be revalidating this issue once the issue is fixed.

Thanks!

@ghost
Copy link

ghost commented Jul 18, 2022

Hi @nchaulet @jen-huang @joshdover,

We have re-validated this issue on the latest 8.4.0-SNAPSHOT self-managed build and observed that the issue is fixed.

Build details:

Version: 8.4.0 SNAPSHOT
Build: 54571
Commit: f53c703c4e8851adc51da800a0965eaaae4136fe

Overview Steps:

  1. Start Kibana with invalid values of xpack.fleet.agents.elasticsearch.host and xpack.fleet.agents.fleet_server.hosts, e.g.:
xpack.fleet.agents.elasticsearch.host: https://bad.svc:9200/
xpack.fleet.agents.fleet_server.hosts: [["https://bad.svc:8220"](https://bad.svc:8220/)]

  1. Check the values in the Kibana UI (Fleet > Settings flyout).
  2. Create a Policy > Add Fleet Server > Install Elastic Agent
  3. Agent doesn't get installed
  4. Now, Re-start Kibana with valid values of xpack.fleet.agents.elasticsearch.host and xpack.fleet.agents.fleet_server.hosts, e.g.:
xpack.fleet.agents.elasticsearch.host: [https://10.10.10.10:9200](https://172.31.12.144:9200/)
xpack.fleet.agents.fleet_server.hosts: [["https://10.10.10.10:8220"](https://172.31.12.144:8220/)]
  1. Observe the values in the Kibana UI are now updated(Fleet > Settings flyout).
  2. Create a Policy > Add Fleet Server > Install Elastic Agent
  3. Elastic Agent is installed

Below are the observations

  • Updated values are visible in the Kibana UI (Fleet > Settings flyout).

image

  • Updated values are visible in the Elastic Agent logs.

Elastic Agent logs: Windows

elastic-agent-diagnostics-2022-07-18T09-20-41Z-00.zip

Hence, we are marking this issue as QA Validated.

Thanks!

@ghost ghost added QA:Validated Issue has been validated by QA and removed QA:Needs Validation Issue needs to be validated by QA labels Jul 18, 2022
@maggieghamry
Copy link
Contributor

@joshdover @nchaulet is there a workaround for folks < 8.4.0 since the PR was not backported?

@nchaulet
Copy link
Member

nchaulet commented Dec 15, 2022

@maggieghamry for folks using a lower version than 8.4.0 they would to have to edit these settings in the UI and remove them from the kibana.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants