Bug 317261 - Check for dual power fencing fails when adding new fence instances
Summary: Check for dual power fencing fails when adding new fence instances
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga
Version: 5.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ryan McCabe
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-03 19:52 UTC by Ryan McCabe
Modified: 2009-04-16 22:43 UTC (History)
4 users (show)

Fixed In Version: RHBA-2008-0407
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-21 15:47:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0407 0 normal SHIPPED_LIVE conga bug fix and enhancement update 2008-05-21 15:46:31 UTC

Description Ryan McCabe 2007-10-03 19:52:30 UTC
When adding or editing cluster node fence configuration for a node using a power
fencing device, the code that detects whether dual power fencing is needed (and
forces n*2 fence options, where the first half are on and the second are off,
given n ports) fails.

This only happens for the most recent node fencing configuration entered, and
should be caught and fixed automatically if you modify something other than node
fencing configuration via conga.

Comment 1 Ryan McCabe 2007-10-03 19:58:30 UTC
Sorry, above should read, "first half are off and the second half are on"
instead of the reverse.

Comment 3 Brian Brock 2008-05-15 01:47:34 UTC
logic in the fencing configuration seems to reflect the new behavior, changing
state to verified.

Comment 5 errata-xmlrpc 2008-05-21 15:47:25 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0407.html


Note You need to log in before you can comment on or make changes to this bug.