Bug 854183

Summary: fence_xvm does not respect delay parameter in cluster.conf
Product: Red Hat Enterprise Linux 5 Reporter: michal novacek <mnovacek>
Component: cmanAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 5.9CC: cluster-maint, edamato, mjuricek
Target Milestone: rc   
Target Release: 5.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cman-2.0.115-110.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-30 22:06:00 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:
Bug Depends On:    
Bug Blocks: 928849    
Attachments:
Description Flags
/etc/cluster/cluster.conf none

Description michal novacek 2012-09-04 09:23:15 UTC 
Created attachment 609605 [details]
/etc/cluster/cluster.conf

Description of problem:
When there is delay=15 added into <device> node in cluster.conf it is ignored
by /sbin/fence_node. fence_node command should first wait $delay seconds before
trying to send fence_command which it does not at the moment.

Version-Release number of selected component (if applicable):
RHEL-5.9, cman-2.0.115-106.el5

How reproducible: always.

Steps to Reproduce:
1. have cluster of three virtual machinech
2. on one of the nodes create/modify /etc/cluster/cluster.conf similar to the
one attached in which each <device> will have delay=15 attribute.
3. use "ccs_tool update /etc/cluster/cluster.conf" to distribute this config to
all nodes on the cluster.
4. on one of the nodes time fencing other node in the cluster
  
Actual results:
takes about two seconds.

Expected results:
should first wait $delay seconds and then try to fence the node which should
take more than 15 seconds.

Additional info:
partly related: https://bugzilla.redhat.com/show_bug.cgi?id=804170
Comment 5 errata-xmlrpc 2013-09-30 22:06:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1304.html