Bug 2026385

Summary: [RFE] Add ability to configure sbd on cluster nodes but not remote nodes via TripleO template
Product: Red Hat OpenStack Reporter: Luigi Tamagnone <ltamagno>
Component: puppet-tripleoAssignee: Luca Miccini <lmiccini>
Status: CLOSED CURRENTRELEASE QA Contact: David Rosenfeld <drosenfe>
Severity: low Docs Contact:
Priority: medium    
Version: 17.1 (Wallaby)CC: jelynch, jjoyce, joflynn, jschluet, lmiccini, mburns, rbruzzon, slinaber, spower, tvignaud
Target Milestone: ---Keywords: FutureFeature, TestOnly, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-pacemaker-1.5.1-1.20221226003830.7add073.el9ost puppet-tripleo-14.2.3-1.20230106160840.c6d3f8c.el9ost Doc Type: Enhancement
Doc Text:
With this update, you can configure `fence_watchdog` that uses `sbd`, like other fencing devices via tripleo, by defining the respective fencing resource: + ---- parameter_defaults: EnableFencing: true FencingConfig: devices: - agent: fence_watchdog host_mac: 52:54:00:74:f7:51 ---- + As an operator, you must enable `sbd` and set the watchdog timeout: + ---- parameter_defaults: ExtraConfig: pacemaker::corosync::enable_sbd: true tripleo::fencing::watchdog_timeout: 20 ----
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 13:40:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luigi Tamagnone 2021-11-24 14:25:33 UTC
Description of problem:
From RHEL8.4 it's possible to use sbd on cluster nodes but not remote nodes, Bug 1443666 as reference.
This RFE is to request the ability to configure it via TripleO template. Now it's required to create a post-deploy script

Version-Release number of selected component (if applicable):
Red Hat OpenStack 16.2 (RHOSP16.2)


Steps to Reproduce:
The script for post-deploy should be similar to this:
~~~
pcs property set stonith-watchdog-timeout=10
pcs resource create watchdog stonith:fence_watchdog

pcs stonith level add 2 controller-0 watchdog
pcs stonith level add 2 controller-1 watchdog
pcs stonith level add 2 controller-2 watchdog

pcs resource update watchdog instance pcmk_host_list="controller-0,controller-1,controller-2"
~~~
Enable sbd in template extra config during the deploy/update:
~~~
parameter_defaults:
   ExtraConfig:
     pacemaker::corosync::enable_sbd: true
~~~


Actual results:
After the configuration the pcs output should be similar to this:
~~~
[root@controller-1 ~]# pcs stonith level
Target: compute-0
  Level 1 - stonith-fence_ipmilan-compute-0
Target: controller-0
  Level 1 - stonith-fence_ipmilan-controller-0
  Level 2 - watchdog
Target: controller-1
  Level 1 - stonith-fence_ipmilan-controller-1
  Level 2 - watchdog
Target: controller-2
  Level 1 - stonith-fence_ipmilan-controller-2
  Level 2 - watchdog
~~~

Comment 2 Riccardo Bruzzone 2022-03-17 16:07:12 UTC
Hello,
Customer is asking for a backport of this new feature in red Hat OpenStack 16.2.
Could you evaluate also the impact of this request ?

BR
Riccardo

Comment 3 Luca Miccini 2022-03-18 08:51:26 UTC
(In reply to Riccardo Bruzzone from comment #2)
> Hello,
> Customer is asking for a backport of this new feature in red Hat OpenStack
> 16.2.
> Could you evaluate also the impact of this request ?
> 
> BR
> Riccardo

Hi Riccardo,
this feature unfortunately hasn't been prioritized so I haven't been able to implement it yet.
Once that is done we can vet the feasibility of the backport.

Regards
Luca

Comment 6 spower 2022-10-28 10:55:33 UTC
This will need to go through the exception process to go into 17.1.

Comment 15 Lon Hohberger 2023-08-16 10:34:13 UTC
According to our records, this should be resolved by puppet-pacemaker-1.5.1-1.20221226003830.7add073.el9ost.  This build is available now.

Comment 16 Lon Hohberger 2023-08-16 10:34:16 UTC
According to our records, this should be resolved by puppet-tripleo-14.2.3-1.20230517011019.el9ost.  This build is available now.