Keystone fails over slowly
Bug #1461655 reported by
Dmitry Mescheryakov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Committed
|
High
|
Boris Bobrov |
Bug Description
Steps to reproduce
1. Install HA env with 3 controllers and 1 compute node
2. Shut down one of the controllers
3. Get a new token with 'keystone token-get'
4. Do 'keystone tenant-list' using token from step #4
5. Repeat steps 3-4 several times
With some probability, step 4 (keystone tenant-list) will fail with message 'Invalid OpenStack Identity credentials'. You might need to get up and shut down controller several times before you get a repro. But once you get it, many new tokens generated in step #4 will fail on step #4. The behaviour persists until the controller is up.
description: | updated |
description: | updated |
description: | updated |
Changed in mos: | |
milestone: | none → 6.1 |
Changed in mos: | |
importance: | Undecided → High |
tags: | added: keystone |
description: | updated |
Changed in mos: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Changed the description a bit.
The bug should be fixed by https:/ /review. fuel-infra. org/#/c/ 7407/. With the fix, one should wait TCP_KEEPALIVE seconds after node failure. The value (TCP_KEEPALIVE) is out of keystone's control, someone who deals with network configuration should have a look here.