Bug 230134 - can't fence port 1:1 with fence_apc
can't fence port 1:1 with fence_apc
Status: CLOSED CURRENTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: fence (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
: Regression, TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-26 15:04 EST by Nate Straz
Modified: 2009-04-16 16:12 EDT (History)
1 user (show)

See Also:
Fixed In Version: 4.5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-05-30 15:42:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
output from fence_apc -v (2.25 KB, text/plain)
2007-02-26 15:05 EST, Nate Straz
no flags Details

  None (edit)
Description Nate Straz 2007-02-26 15:04:02 EST
Description of problem:

When trying to fence a node connected to switch 1, port 1 of a linked
MasterSwitch Plus, I get the following error.

[root@morph-02 ~]# fence_apc -a morph-apc -l apc -p apc -o reboot -n 1:1 -v
Problem identifying outlet
Looking for 1 in string -------


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

How reproducible:
100%

Steps to Reproduce:
1. fence_apc -o reboot -n 1:1 -v
  
Actual results:

I will attach /tmp/apclog

Expected results:


Additional info:
Comment 1 Nate Straz 2007-02-26 15:05:34 EST
Created attachment 148824 [details]
output from fence_apc -v
Comment 2 Stanko Kupcevic 2007-02-27 10:57:48 EST
Fixed in HEAD
Comment 3 Stanko Kupcevic 2007-02-27 11:15:32 EST
Commited to RHEL4 as well
Comment 4 RHEL Product and Program Management 2007-02-27 11:23:50 EST
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.
Comment 6 Nate Straz 2008-05-30 15:42:50 EDT
Closing this out since it missed the errata process.

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