Downtime of one memcache instance leads to failures after recovery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
New
|
High
|
Fuel Library (Deprecated) | ||
5.0.x |
New
|
Undecided
|
Fuel Library (Deprecated) | ||
5.1.x |
New
|
High
|
Fuel Library (Deprecated) | ||
6.0.x |
New
|
Undecided
|
Fuel Library (Deprecated) | ||
6.1.x |
New
|
High
|
Fuel Library (Deprecated) |
Bug Description
Way to reproduce:
1) restart an instance of memcache
2) spawn dozen of VMs
3) investifgate failed instances and find out that keystone failed to auth few tokens of few services
like this:
<188>Dec 30 14:57:23 node-1 keystone-all 2014-12-30 14:57:23.402 3910 WARNING keystone.
ERROR cinder.
summary: |
- Downtime of on memcache instance leads to failures after recovery + Downtime of one memcache instance leads to failures after recovery |
More easier way to reproduce:
1) on 1st screen on one of controllers run: d/keystone stop ; /etc/init. d/memcached stop ; sleep 1m ; /etc/init. d/memcached start ; /etc/init. d/keystone start
/etc/init.
2) on 2nd screen on one of the controllers in parallel run:
while true ; do date ; for f in `seq 1 20` ; do ( out=$(glance --debug image-list 2>&1) || echo $out ) & done ; wait ; done
3) enjoy random failures almost infinitely