Liam Young e02c6257ae Fix adding of stonith controlled resources. ... There appears to be a window between a pacemaker remote resource being added and the location properties for that resource being added. In this window the resource is down and pacemaker may fence the node. The window is present because the charm charm currently does: 1) Set stonith-enabled=true cluster property 2) Add maas stonith device that controls pacemaker remote node that has not yet been added. 3) Add pacemaker remote node 4) Add pacemaker location rules. I think the following two fixes are needed: 1) For initial deploys update the charm so it does not enable stonith until stonith resources and pacemaker remotes have been added. 2) For scale-out do not add the new pacemaker remote stonith resource until the corresponding pacemaker resource has been added along with its location rules. Depends-On: Ib8a667d0d82ef3dcd4da27e62460b4f0ce32ee43 Change-Id: I7e2f568d829f6d0bfc7859a7d0ea239203bbc490 Closes-Bug: #1884284		2020-09-09 09:35:30 +00:00
..
__init__.py	Convert charm to Python 3	2019-03-14 12:40:07 +00:00
test_hacluster_hooks.py	Fix adding of stonith controlled resources.	2020-09-09 09:35:30 +00:00
test_hacluster_utils.py	Fix adding of stonith controlled resources.	2020-09-09 09:35:30 +00:00
test_pcmk.py	Spread pacemaker remote resources across cluster.	2020-09-08 11:35:25 +00:00
test_utils.py	Convert charm to Python 3	2019-03-14 12:40:07 +00:00