Bug 606316 - fence_apc fails for some port numbers
Summary: fence_apc fails for some port numbers
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: fence
Version: 4
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marek Grac
QA Contact: Cluster QE
URL:
Whiteboard: Regression
Depends On: 606297
Blocks: 606315
TreeView+ depends on / blocked
 
Reported: 2010-06-21 12:06 UTC by Marek Grac
Modified: 2010-07-16 09:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 606297
Environment:
Last Closed: 2010-07-16 09:16:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Marek Grac 2010-06-21 12:06:59 UTC
+++ This bug was initially created as a clone of Bug #606297 +++

Description of problem:

This command works
fence_apc  -l user -p user -a pdu -o reboot -n 1
but the same command fails for port 23:
fence_apc  -l user -p user -a pdu -o reboot -n 23

(first line on new page)

Version-Release number of selected component (if applicable):
fence-agents-3.0.12-3.el6.x86_64

How reproducible:
Log into BAR cluster and try to fence bar-01:-)

--- Additional comment from pm-rhel on 2010-06-21 07:43:21 EDT ---

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

--- Additional comment from mgrac on 2010-06-21 07:45:35 EDT ---

Line splitting is not working as expected when 'next line' is not issued and just carriage is returned on the first position. This affects only line after
'press enter to continue'

show_re = re.compile('^\s*(\d+)- (.*?)\s+(ON|OFF)\s*')

need to be changed to: (accept 0D as start of line)

show_re = re.compile('[^\x0D]\s*(\d+)- (.*?)\s+(ON|OFF)\s*')

Comment 1 Marek Grac 2010-07-16 09:16:23 UTC
Due to different implementation (and missing ^ in regex), problem is already fixed in released versions.


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