You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a HAProxy 2.4.27 with Data Plane API 2.6.5 on Linux and when I try to get the admin_state for the runtime servers, it always returns maint admin_state, doesn't matter if server is on READY, DRAIN or MAINT state:
Checking the Data Plane API code (GetServerState() and GetServersState() in handlers/runtime_server.go) and its dependencies, I found GetServerAdminState() in https://github.com/haproxytech/client-native/blob/master/misc/bits.go and I solved the problem by making the changes below:
From:
if mask.Any(B0, B1, B5) {
return "maint", nil
}
if mask.Any(B3, B4) {
return "drain", nil
}
To:
if mask.Any(B0) {
return "maint", nil
}
if mask.Any(B1) {
return "drain", nil
}
I don't know if it's a feature that isn't normally used, as I haven't found anyone else reporting this problem. I don't have any information on whether this problem continues in the most recent versions of HAProxy and Data Plane API, but it was the solution adopted to resolve the problem in these versions.
The text was updated successfully, but these errors were encountered:
I'm using a HAProxy 2.4.27 with Data Plane API 2.6.5 on Linux and when I try to get the admin_state for the runtime servers, it always returns maint admin_state, doesn't matter if server is on READY, DRAIN or MAINT state:
Checking the Data Plane API code (GetServerState() and GetServersState() in handlers/runtime_server.go) and its dependencies, I found GetServerAdminState() in https://github.com/haproxytech/client-native/blob/master/misc/bits.go and I solved the problem by making the changes below:
From:
To:
I don't know if it's a feature that isn't normally used, as I haven't found anyone else reporting this problem. I don't have any information on whether this problem continues in the most recent versions of HAProxy and Data Plane API, but it was the solution adopted to resolve the problem in these versions.
The text was updated successfully, but these errors were encountered: