Add of detached keystone node to existing cluster failed with Call cib_apply_diff failed (-205): Update was older than existing configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel Plugins |
New
|
Undecided
|
Unassigned | ||
Fuel for OpenStack |
Fix Released
|
High
|
Dmitry Bilunov | ||
7.0.x |
Fix Released
|
High
|
Dmitry Ilyin | ||
8.0.x |
Fix Released
|
High
|
Dmitry Bilunov |
Bug Description
Steps:
1. Install detach-database and detach-keystone plugins on master node
2. Create next cluster - Ubuntu, HA, Neutron Vlan, enabled separate-database and separate-keystone, 3 controllers, 1 compute, 1 cinder, 3 database+keystone
3. Deploy cluster
4. After deployment add 1 keystone node
5. Start deployment
Actual result - it failed on new keystone node (node-8):
2015-09-10 09:57:48 ERR (/Stage[
Issue might affect keystone plugin only.
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Dmitry Ilyin (idv1985) |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: on-verification |
tags: | added: area-library |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | added: team-bugfix |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: on-verification |
tags: | added: on-verification |
tags: | added: on-verification |
The old implementation of cs_property id lacking retries. Perhaps in this case crm did not update the cib before some property have been changed somewhere and there was no retry to fix this situation.
Why do you even try to manage no-quorum-policy property? puppet/ osnailyfacter/ modular/ astute/ enable_ quorum. rb to set thei property
We are using this script after the deployment ./deployment/