After further investigation, what I observe is that if I don't use SSL and point coordination backend_url (as given in cinder.conf) to the IP of the node in /etc/hosts, there's no etcd3gw exception. But if I use the virtual internal IP of the OpenStack created by the keepalive, I see that error. So, I point the backend_url to the IP of the node to get rid off of the exception. Once done, I apply SSL and now I see https error in the cinder log. This goes away, once I point the backen_url back to the virtual IP of the OpenStack given by the keepalive! However, this brings the etcd3gw exception back! Those URLs you gave are of no use, I guess. *Thanks and Regards,* Debasis Mondal On Tue, Jun 4, 2024 at 7:30 AM Przemysław Kuczyński <