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

elastic-agent: running with snapshots of dependencies #17761

Closed
mtojek opened this issue Apr 16, 2020 · 2 comments · Fixed by #17764
Closed

elastic-agent: running with snapshots of dependencies #17761

mtojek opened this issue Apr 16, 2020 · 2 comments · Fixed by #17764
Assignees
Labels

Comments

@mtojek
Copy link
Contributor

mtojek commented Apr 16, 2020

I booted up snapshot version of Kibana and Elasticseach. The agent failed with following error:

./elastic-agent enroll http://localhost:5601 NzNjbmczRUJVR2x5NHZyUFFDMko6R2RBV21DTEtUa2FhUy1ybXZxM2dudw==
The Elastic Agent is currently in Alpha and should not be used in production
This will replace your current settings. Do you want to continue? [Y/n]:Y
2020-04-16T15:23:47+02:00 DEBUG	client.go:170	Request method: POST, path: /api/ingest_manager/fleet/agents/enroll
fail to enroll: fail to execute request to Kibana: Status code: 400, Kibana returned an error: Bad Request, message: Browser client is out of date, please refresh the page ("kbn-version" header was "8.0.0" but should be "8.0.0-SNAPSHOT")

/cc @ruflin

@elasticmachine
Copy link
Collaborator

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

@ph ph added the bug label Apr 16, 2020
@ph
Copy link
Contributor

ph commented Apr 16, 2020

Oh crap we are indeed too strict here.

@ph ph assigned ph and unassigned michalpristas Apr 16, 2020
ph added a commit to ph/beats that referenced this issue Apr 16, 2020
This remove the check that Kibana was doing to enforce that the remove
version match the current version of Kibana. Instead the Fleet API
should take the agent header version and ensure we can support it.

This allow the Kibana side to control the communication and the upgrade
more gracefully.

Fixes: elastic#17761
@ph ph closed this as completed in #17764 Apr 17, 2020
ph added a commit that referenced this issue Apr 17, 2020
…17764)

* Remove the hard version between Fleet and the Elastic Agent.

This remove the check that Kibana was doing to enforce that the remove
version match the current version of Kibana. Instead the Fleet API
should take the agent header version and ensure we can support it.

This allow the Kibana side to control the communication and the upgrade
more gracefully.

Fixes: #17761
ph added a commit to ph/beats that referenced this issue Apr 17, 2020
…lastic#17764)

* Remove the hard version between Fleet and the Elastic Agent.

This remove the check that Kibana was doing to enforce that the remove
version match the current version of Kibana. Instead the Fleet API
should take the agent header version and ensure we can support it.

This allow the Kibana side to control the communication and the upgrade
more gracefully.

Fixes: elastic#17761
(cherry picked from commit c40a841)
@andresrc andresrc reopened this Apr 19, 2020
ph added a commit that referenced this issue Apr 20, 2020
…eet and the Elastic Agent. (#17806)

* [Agent] Remove the hard version between Fleet and the Elastic Agent. (#17764)

* Remove the hard version between Fleet and the Elastic Agent.

This remove the check that Kibana was doing to enforce that the remove
version match the current version of Kibana. Instead the Fleet API
should take the agent header version and ensure we can support it.

This allow the Kibana side to control the communication and the upgrade
more gracefully.

Fixes: #17761
(cherry picked from commit c40a841)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants