Bug 128635
Summary: | fence_node: fences the node it's run on | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Derek Anderson <danderso> |
Component: | gfs | Assignee: | Christine Caulfield <ccaulfie> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | teigland |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-04 19:25:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Derek Anderson
2004-07-27 14:43:10 UTC
I will try to figure out what's happening here but I think you misunderstand the relation between fenced and fence_node -- the two have nothing to do with each other. fenced deals with the fence domain and executes a fencing agent against a node when a node is removed from the domain, based on input from cman. fence_node is not used by our software but is a simple and potentially useful utility. fence_node looks up fencing parameters from ccs and then calls the specified agent on the victim. In effect, fenced calls fence_node when it needs to fence a node that's left the domain. I'm using fence_manual and see no problems when using fence_node as you've shown. Verified against: fenced DEVEL.1096898839 (built Oct 4 2004 09:08:31) Copyright (C) Red Hat, Inc. 2004 All rights reserved. Updating version to the right level in the defects. Sorry for the storm. |