Comment 2 for bug 1892852

Hello,
I guess you are right. The memcached configuration is related to the authentication and thus to Keystone.
I didn't know that the socket management was handled by the keystone middleware. Maybe this interaction with the middleware can explain somehow the fact that the socket is somehow left open.

I do not how I should proceed. Should I copy the content of this ticket and create a new one on the keystone component, or there is a way to move it ?

Thanks a lot for your quick feedback
Sergio