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-tripleo | Assignee: | 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
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 (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 This will need to go through the exception process to go into 17.1. work in progress here: https://review.opendev.org/c/openstack/puppet-pacemaker/+/863036 https://review.opendev.org/c/openstack/puppet-tripleo/+/863041 According to our records, this should be resolved by puppet-pacemaker-1.5.1-1.20221226003830.7add073.el9ost. This build is available now. According to our records, this should be resolved by puppet-tripleo-14.2.3-1.20230517011019.el9ost. This build is available now. |