It definitely could be reproducible in MOS 5.0 because I seen this behavior each and every time when session expires. Possible reasons could be: keystone with memcached or settings of HAproxy.
It definitely could be reproducible in MOS 5.0 because I seen this behavior each and every time when session expires.
Possible reasons could be: keystone with memcached or settings of HAproxy.