documentation unclear after hacluster changes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Masakari Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
1. hacluster stonith_enabled parameter changed from default False to default true with a deprecation warning
stonith_enabled:
default: "False"
description: |
DEPRECATED: is now ignored and will be removed in a future release.
Resource fencing (aka STONITH) is now always enabled for every node in
the cluster. This requires MAAS credentials be provided and each node's
power parameters are properly configured in its inventory.
2. pacemaker-remote enable-stonith says (some typos there)
description: |
Whether to request a stoniith resoiurce is created for this nodee
It is not clear whether pacemaker-remote enable-stonith: false disables stonith as hacluster says it will enable it on all nodes.
What we observed in SQA test runs, our masakari validator started to reboot node where we killed nova-compute and pacemaker_remote, which was not happening before. We have (and had) enable_stonith set to true in pacemaker and stonith disabled in hacluster-masakari.
This is all in Ussuri on Focal.
