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
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Invalid values entered to fence agent Consequences: Agent ends with exception Fix: Cover exceptions and add user understandable strings Results: Fencing agent ends with human readable error
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/RHSA-2009-1341.html