due to incorrect logic in python-memcache, keystone tries to write data into a dead memcache backend, skipping alive backends.
That happens because backend traverse logic is randomized and can potentially miss alive servers in the pool.
When most servers of the pool are dead, the probability of failure is relatively high.
Practically that issue shows up during deployment, when keystone is used in the environment, where some controllers have not been deployed yet.
The issue is a heizenbug and it depends on the randomly generated data.
due to incorrect logic in python-memcache, keystone tries to write data into a dead memcache backend, skipping alive backends.
That happens because backend traverse logic is randomized and can potentially miss alive servers in the pool.
When most servers of the pool are dead, the probability of failure is relatively high.
Practically that issue shows up during deployment, when keystone is used in the environment, where some controllers have not been deployed yet.
The issue is a heizenbug and it depends on the randomly generated data.