Bug 718195

Summary: Dell Drac CMC is not working correctly as fence device
Product: Red Hat Enterprise Linux 5 Reporter: Marek Grac <mgrac>
Component: fence-agentsAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7CC: cluster-maint, djansa, edamato, fdinitto, mjuricek, sgordon
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: fence-agents-3.0.17-12.el5 Doc Type: Bug Fix
Doc Text:
The list operation for Dell DRAC CMC fence devices previously did not function correctly. When the list operation was invoked it failed and a traceback error presented. The fence-agents have been updated and the list operation now works correctly for Dell DRAC CMC fence devices.
Story Points: ---
Clone Of: 718194 Environment:
Last Closed: 2012-02-21 04:51:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 718194    
Bug Blocks:    

Description Marek Grac 2011-07-01 10:55:42 UTC
+++ This bug was initially created as a clone of Bug #718194 +++

Description of problem:

List operation for fence_drac5 is not working correctly and fence agents ends with python traceback

Comment 5 Stephen Gordon 2012-02-09 19:35:02 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The list operation for Dell DRAC CMC fence devices previously did not function correctly. When the list operation was invoked it failed and a traceback error presented.

The fence-agents have been updated and the list operation now works correctly for Dell DRAC CMC fence devices.

Comment 6 errata-xmlrpc 2012-02-21 04:51:51 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-2012-0318.html