Bug 674483

Summary: cman: fence_brocade has not been done at the wrong password
Product: Red Hat Enterprise Linux 5 Reporter: Hajime Taira <htaira>
Component: cmanAssignee: Marek Grac <mgrac>
Status: CLOSED CANTFIX QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.6CC: cluster-maint, edamato
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 841556 (view as bug list) Environment:
Last Closed: 2012-07-19 11:51:44 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:    
Bug Blocks: 807971, 841556    
Attachments:
Description Flags
error handling codes and connection closing codes for fence_brocade.pl none

Description Hajime Taira 2011-02-02 05:47:05 UTC
Description of problem:

fence_brocade has not been done at the wrong password.

When I set wrong password to fence_brocade.pl.
fence agent will stop during $t->waitfor('/\>/');
Fablic OS will return "Login incorrect".

I created patch for error handling codes and connection closing code.
But I have not Brocade Silkworm switch. This source code is not tested at real SAN switch.
I read Brocade Fabric OS Command Reference Manual.

Comment 1 Hajime Taira 2011-02-02 05:54:01 UTC
Created attachment 476518 [details]
error handling codes and connection closing codes for fence_brocade.pl

Comment 7 RHEL Program Management 2012-04-02 10:52:08 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 8 Marek Grac 2012-07-19 11:50:52 UTC
We will attempt to fix this bug in RHEL version 6