Bug 489670

Summary:	Exceptions in fencing agents
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Marek Grac <mgrac>
Component:	fence	Assignee:	Marek Grac <mgrac>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4	CC:	cfeist, cluster-maint, cmarthal, edamato
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	487501	Environment:
Last Closed:	2009-05-18 21:16:19 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:
Bug Depends On:	487501
Bug Blocks:

Description Marek Grac 2009-03-11 10:38:18 UTC

+++ This bug was initially created as a clone of Bug #487501 +++

Several of new fencing agent does not work when bad options are entered (bad password, non-existent outlet number, ...). This is not a problem. Unfortunately python exceptions are thrown and we don't care about catching them. Such output is very usefull for debugging (as people tends to send it) but it will be better if the user will see that the error is in the input data

Comment 3 errata-xmlrpc 2009-05-18 21:16:19 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-2009-1050.html