-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Ingest Manager] Enroll of agent call fails with 400 - at this route: /api/ingest_manager/fleet/agents/enroll #70726
Comments
I don't have ability to run source code currently to verify if its already fixed in master / 8.0 line, just fyi. BUT, I did have an older Kibana from 2 days back and I used the latest 8.0 snapshot agent and it worked - so I think the bug is Kibana side (or at least not in the Agent). |
I expect this with this PR being merged 3 hours ago as of now, that the coming nightly snapshot will have to work as it would be hard to test unenroll without first enrolling - so maybe we're all good. can't be sure tho. #70031 |
Steps to reproduce in Docker:
Expected behavior: kibana is able to enroll the agent
|
John was kind enough to post that the API has been updated, see this: #70339
|
we believe this is fixed and will be picked up in next successful snapshot build completed from here: |
darwin / macOS error is here, linux was found by Manu and our Agent / Ingest Manager e2e test we're writing:
2020-07-03T11:05:01.724-0400 DEBUG map[file.line:178 file.name:kibana/client.go] Request method: POST, path: /api/ingest_manager/fleet/agents/enroll {"ecs.version": "1.5.0"}
fail to enroll: fail to execute request to Kibana: Status code: 400, Kibana returned an error: Bad Request, message: Agent version is not compatible with kibana version
Kibana version:
latest 8.0 SNAPSHOT deploy to cloud-staging as of 11AM.
Browser version:
chrome on macOS
Describe the bug:
enroll call on the host as instructed by Ingest Manager UI fails with 400 response.
Steps to reproduce:
Expected behavior:
it should work. then you can run agent. as it is now, it gets a 400 and Agent does not show up in the Kibana Ingest Manager UI
Screenshots (if relevant):
The text was updated successfully, but these errors were encountered: