Description of problem:
The dummy openThe dummy openstack-core resource was meant to replace keystone so that restarting keystone would not restart the whole cloud. When this resource was introduced the paramter interleave=true was mistakenly left out.stack-core resource was meant to replace keystone so that restarting keystone would not restart the whole cloud. When this resource was introduced the paramter interleave=true was mistakenly left out.
As a side effect of that openstack-core resource is being restarted on all controllers nodes right after one of the controllers nodes comes back online after failover which effectively causing restart of most of the resources and cluster downtime.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Ungracefully reset or fence one of the controller of HA Openstack setup.
2. Wait for the reset node to come back online.
Many resource on all controllers nodes - even though alive controllers nodes which were not reset/fence are being restarted which causing donwtime of Openstack cluster
Resource already running and started on controller nodes should be left in that state and not to be restarted. Only resources on fenced node should be started.
Upstream patch has been merged
Meta Attrs: interleave=true
Resource: openstack-core (class=ocf provider=heartbeat type=Dummy)
Operations: start interval=0s timeout=20 (openstack-core-start-interval-0s)
stop interval=0s timeout=20 (openstack-core-stop-interval-0s)
monitor interval=10 timeout=20 (openstack-core-monitor-interval-10)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.