-
Notifications
You must be signed in to change notification settings - Fork 74
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
Reloading haproxy causes endpoints to incorrectly respond with a version requirement error. #289
Comments
Hi @fatchan and thanks for the report. I could not reproduce this behavior on my machine. Could you please provide:
For me it works when using |
Thanks Olivier, as requested: haproxy section of dataplaneapi.hcl
systemd unit file
Update: I just build dataplaneapi myself with a forked client-native with the version check removed. Works fine for now. |
Hi @fatchan there seems to be an error when fetching the version from the HAProxy's stats socket. Can you paste the output of |
Thanks @mjuraga Here is the output of `show info` output
In this case, it was after a reload from adding an ssl certificate through dataplaneapi. Later, when sending a DELETE to
And again, just in case you need: haproxy -vv
dataplaneapi -v
|
Hello! It appears Docker images are affected by this issue. Specifically, I am using I have Datplane configured by adding
To reproduce the issue, create a new backend called "test" using Dateplane API by POSTing to Just in case it's relevant: haproxy -vv
dataplaneapi -v
|
Hello, do you have any updates on whether a potential fix is underway? We are completely stuck on transitioning our HAProxy to containers. If needed, I am interested in contributing. |
Hi,
After reloading haproxy e.g.
sudo systemctl reload haproxy
, a POST tov2/services/haproxy/runtime/servers?backend=whatever
endpoint will return{"code":500,"message":"this operation requires HAProxy 2.6 or later"}
.However, I am on haproxy 2.7. This api call works correctly before reloading, or after restarting rather than reloading haproxy.
This is an issue for me because after I add a certificate with dataplaneapi and haproxy reloads, some future API calls get broken with the "requires haproxy 2.6 or later" error.
For now, I have worked around the issue by
setting the dataplaneapi.hclrunning my own build of dataplaneapi with the version check from client-native removed, which is not ideal.reload_cmd
to actually restart haproxy insteadAny ideas?
Kind regards.
haproxy -vv
dataplaneapi -v
Update: did some grep'ing and realised that error is actually from inside client-native here: https://github.com/haproxytech/client-native/blob/master/runtime/runtime_client.go#L229 but nevertheless it shouldn't be returning the error because i am on haproxy 2.7. Should I open an issue there instead?
The text was updated successfully, but these errors were encountered: