Hi Alexey, My few comments on your point: - HAProxy usually works in TCP mode, when TLS termination is done on the Apache virtual host on the backend servers (servers hosting an OpenStack control plane service). Therefore, HAProxy doesn't even know that the traffic passing through is HTTP/HTTPS. And even if it knew, it should not, by any means, respond to the client on behalf of the backend service. - This problem falls into the 'no response received' category of the errors that the client should detect and handle properly. In particular, the client should not assume the operation failed, which is the current behaviour. For all 'query type' requests (ie, HTTP GET), it is completely safe to retry the prior request, but for all requests attempting to modify the state of the OpenStack/database (PUT, POST, etc), without having the response, we should not retry. Rather, report an error to the user immediately. Best regards, Marcin
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012047 Title: Client should not blindly resend/retry POST/PUT (create/update) requests To manage notifications about this bug go to: https://bugs.launchpad.net/keystoneauth/+bug/2012047/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
