Bug 718922 - fence_drac5 does not end ssh sessions
Summary: fence_drac5 does not end ssh sessions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fence-agents
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Marek Grac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 718924 730633 730634
TreeView+ depends on / blocked
 
Reported: 2011-07-05 07:21 UTC by Fabio Massimo Di Nitto
Modified: 2011-08-15 07:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 718924 (view as bug list)
Environment:
Last Closed: 2011-07-08 08:21:39 UTC
Type: ---


Attachments (Terms of Use)

Description Fabio Massimo Di Nitto 2011-07-05 07:21:56 UTC
Description of problem:

	
Attribute		Value
		
Name		DRAC 5
Product Information		Dell Remote Access Controller 5
Hardware Version		A07
Firmware Version		1.51
Firmware Updated		NA
RAC Time		Tue Jul 5 07:18:01 2011

device is configured to allow max 4 ssh connections

Version-Release number of selected component (if applicable):

3.1.4+git

How reproducible:

always

Steps to Reproduce:

[root@rhel6-node2 ~]# fence_drac5 -o status -a drac.int.fabbione.net -l root -p blabla -x
Status: ON
[root@rhel6-node2 ~]# fence_drac5 -o status -a drac.int.fabbione.net -l root -p blabla -x
Status: ON
[root@rhel6-node2 ~]# fence_drac5 -o status -a drac.int.fabbione.net -l root -p blabla -x
Status: ON
[root@rhel6-node2 ~]# fence_drac5 -o status -a drac.int.fabbione.net -l rootblabla -x
Status: ON
[root@rhel6-node2 ~]# fence_drac5 -o status -a drac.int.fabbione.net -l root -p blabla -x
Unable to connect/login to fencing device
[root@rhel6-node2 ~]# 

Actual results:

The ssh sessions are not being closed at the end of command execution, causing the device to think that the fence_agent is still connected.

Once the max conn limit is exceeded, further login to the device are not allowed

(see attached print from web management UI)

Comment 1 Fabio Massimo Di Nitto 2011-07-08 08:21:39 UTC
It turns out to be a Dell firwmare issue


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