[library] 'keystone' delays lead to unstable MOS operations
Bug #1340657 reported by
Dennis Dmitriev
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Aleksandr Didenko | ||
5.0.x |
Won't Fix
|
High
|
Sergii Golovatiuk | ||
5.1.x |
Fix Released
|
Critical
|
Aleksandr Didenko | ||
6.0.x |
Fix Released
|
Critical
|
Aleksandr Didenko |
Bug Description
Upstream bug: https:/
Confirmed for OpenStack HA environment.
When several OS controller nodes are used with 'memcached' installed on each of them, each 'keystone' instance is configured to use all of the 'memcached' instances.
Thus, if one of the controller nodes became inaccessible, then whole cluster may cease to be workable because of a lot of delays in the memcached backend.
There is no acceptable workaround at the moment which would allow the use all of available 'memcached' instances without such kind of issue.
Changed in mos: | |
assignee: | nobody → MOS Keystone (mos-keystone) |
Changed in mos: | |
milestone: | none → 5.0.1 |
Changed in fuel: | |
assignee: | nobody → Fuel for Openstack (fuel) |
Changed in mos: | |
assignee: | MOS Keystone (mos-keystone) → Yuriy Taraday (yorik-sar) |
Changed in mos: | |
status: | New → Invalid |
tags: | added: release-notes |
Changed in mos: | |
milestone: | 5.0.1 → 5.1 |
tags: | added: keystone |
no longer affects: | fuel/5.1.x |
summary: |
- 'keystone' delays lead to unstable MOS operations + [library] 'keystone' delays lead to unstable MOS operations |
no longer affects: | mos |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Sergii Golovatiuk (sgolovatiuk) |
Changed in fuel: | |
assignee: | Vladimir Kuklin (vkuklin) → Aleksandr Didenko (adidenko) |
Changed in fuel: | |
assignee: | Aleksandr Didenko (adidenko) → Sergii Golovatiuk (sgolovatiuk) |
no longer affects: | fuel/6.1.x |
no longer affects: | fuel/5.1.x |
tags: | added: on-verification |
To post a comment you must log in.
May be similar to bug: https:/ /bugs.launchpad .net/fuel/ +bug/1337923
Steps to reproduce:
Steps to Reproduce:
1. Create HA cluster with CentOS, neutron vlan
2. Add 3 nodes with controller role
3. Add 2 nodes with compute role
4. Deploy the cluster
5. Run network verification
6. Run OSTF
7. turn of primarry controller
8. wait for about 5 minutes
9. Run OSTF
Expected results:
Only "Check that required services are running" failed,
All "Functional tests" and "HA tests" passed.
Actual results:
"Functional tests" that launch an instance are failed with "Timed out waiting to become ACTIVE..." errors.
To make sure that this OSTF behaviour is affected by 'keystone':
1. On the rest operational controllers remove IP of the primary controller (it is 192.168.10.3 in the following example) from the IPs lists in the 'keystone' config file /etc/keystone/ keystone. conf: argument= url:192. 168.10. 3,192.168. 10.4,192. 168.10. 5 192.168. 10.3:11221, 192.168. 10.4:11221, 192.168. 10.5:11221
...
[cache]
backend_
...
[memcache]
servers=
..
2. restart openstack-keystone service on all controllers
3. run OSTF