-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Repository package build problem v7.x: url.PathEscape failing & causing 405 Method Not Allowed #41686
Comments
Okay so it appears this is a build issue.
Network traces obtained from tshark:
Repository version:
|
Does not affect v8 since it does not use aliases: https://www.elastic.co/guide/en/beats/libbeat/8.16/breaking-changes-8.0.html |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
@casesolved-co-uk what ES version are you using? |
Fails with both 7.17.23 and 7.17.25. filebeat and elasticsearch are the same version on the same server |
I've tried to reproduce it with the @casesolved-co-uk can you reproduce it if use the files (Linux/tar.gz) downloaded from our downloads page https://www.elastic.co/downloads/past-releases/filebeat-7-17-25? |
Like I said, a fresh build works fine. I didn't use the tarball but I checked out the tag using git then built it. Are you using ubuntu 20.04, and configured apt to use the repo above? |
What is your output from tshark upon creating an alias?
I don't know if this is a hint but I noticed the one that fails uses HTTP/1.0 but successful with HTTP/1.1 |
Maybe linked against an old go library? |
It appears standard filebeat create alias functionality is causing:
{"error":"Incorrect HTTP method for uri [/<filebeat-7.17.23-{now/d}-000001>] and method [PUT], allowed: [POST]","status":405}
It appears the url.PathEscape in the following code is failing somehow:
beats/libbeat/idxmgmt/ilm/client_handler.go
Lines 178 to 194 in bd0ffc1
I've raised a forum issue here but had no luck so far:
https://discuss.elastic.co/t/incorrect-http-method-for-uri-405-method-not-allowed/370661
Same error on 7.17.25
The text was updated successfully, but these errors were encountered: