Pacemaker mysql resource shall have failcounts configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Bogdan Dobrelya | ||
Mitaka |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
W/o failcounts defined, the resource may fail to start and be left stopped.
How to reproduce:
* Deploy a cluster
* Make impossible for the pacemaker mysql clone resource to be started: add a exit 1 to the OCF RA action start.
* Issue crm resource cleanup p_mysql-clone && crm resource restart p_mysql-clone
* Check transitions summary with crm_simulate -Ls | grep -v "\-INF"
* Wait for a while, like 5 min or so, and recheck transitions.
Expected:
Operation start must be always in transitions plan, for example:
Transition Summary:
* Start p_mysql:0 (n1)
* Start p_mysql:1 (n2)
* Start p_mysql:2 (n3)
* Start p_mysql:3 (n4)
* Start p_mysql:4 (n5)
Actual:
It gives up starting the resource
Solution:
Configure failure modes for the pacemaker resource, for example like we do for the rabbit resource:
meta migration-
Changed in fuel: | |
importance: | Undecided → High |
tags: | added: galera pacemaker |
description: | updated |
description: | updated |
tags: | added: tech-debt |
tags: | added: area-library |
no longer affects: | fuel/newton |
how does it affect users ?