Bug 847744 - 3.1 beta2 fenceNode verb ignores its "options" argument
3.1 beta2 fenceNode verb ignores its "options" argument
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm (Show other bugs)
Unspecified Unspecified
unspecified Severity urgent
: rc
: ---
Assigned To: Roy Golan
Tareq Alayan
: Regression
Depends On:
  Show dependency treegraph
Reported: 2012-08-13 08:21 EDT by Roy Golan
Modified: 2012-12-04 14:05 EST (History)
10 users (show)

See Also:
Fixed In Version: vdsm-4.9.6-29.0
Doc Type: Bug Fix
Doc Text:
Previously, the fenceNode API was missing the "options" argument. Consequently, options for the fenceNode verb were not passed to the underlying vdsm implementation. The options argument has been added to the fenceNode API, as a result the fenceNode verb works as expected.
Story Points: ---
Clone Of:
Last Closed: 2012-12-04 14:05:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 18:48:05 EST

  None (edit)
Description Roy Golan 2012-08-13 08:21:26 EDT
Description of problem:
passing options to the fenceNode verb is not passed to the underlying implementation 

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

How reproducible:

Steps to Reproduce:
1. vdsClient 0 fenceNode apc user pass status true port=1
2. trace the logs, no options are passed
Actual results:
root@honda vdsm]# vdsClient 0 fenceNode 22 apc user pass status true port=1
Thread-133333::DEBUG::2012-08-13 15:20:22,139::API::1021::vds::(fenceNode) fenceNode(addr=,port=22,agent=apc,user=user,passwd=XXXX,action=status,secure=true,options=)

Expected results:
options are passed

Additional info:
Comment 7 errata-xmlrpc 2012-12-04 14:05:35 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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