Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
Project not found: home:bnavigator:numpy
openSUSE:Leap:15.6:Update
pacemaker.32860
bsc#1210074-0006-Fix-fencer-apply-requested-fen...
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File bsc#1210074-0006-Fix-fencer-apply-requested-fencing-delay-only-for-th.patch of Package pacemaker.32860
From dd563f99570865582810cfa17374f141849a95b8 Mon Sep 17 00:00:00 2001 From: "Gao,Yan" <ygao@suse.com> Date: Thu, 13 Apr 2023 14:29:56 +0200 Subject: [PATCH 06/11] Fix: fencer: apply requested fencing delay only for the first device ... per review. No need to delay for further devices. --- daemons/fenced/fenced_remote.c | 8 ++++++++ 1 file changed, 8 insertions(+) Index: pacemaker-2.1.5+20221208.a3f44794f/daemons/fenced/fenced_remote.c =================================================================== --- pacemaker-2.1.5+20221208.a3f44794f.orig/daemons/fenced/fenced_remote.c +++ pacemaker-2.1.5+20221208.a3f44794f/daemons/fenced/fenced_remote.c @@ -670,6 +670,14 @@ remote_op_timeout_one(gpointer userdata) pcmk__set_result(&op->result, CRM_EX_ERROR, PCMK_EXEC_TIMEOUT, "Peer did not return fence result within timeout"); + // The requested delay has been applied for the first device + if (op->delay > 0) { + op->delay = 0; + crm_trace("Try another device for '%s' action targeting %s " + "for client %s without delay " CRM_XS " id=%.8s", + op->action, op->target, op->client_name, op->id); + } + // Try another device, if appropriate request_peer_fencing(op, NULL); return FALSE;
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor