Bug 705072

Summary: Support new fence_vmware_soap agent configuration
Product: Red Hat Enterprise Linux 6 Reporter: Ryan McCabe <rmccabe>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: bbrock, cluster-maint, jpokorny, rsteiger
Target Milestone: rc   
Target Release: 6.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: luci-0.23.0-18.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 705073 (view as bug list) Environment:
Last Closed: 2011-12-06 10:07:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
proposed fix none

Description Ryan McCabe 2011-05-16 14:58:23 UTC
Update luci to support the new, rewritten fence_vmware fence agent.

Comment 1 Brian Brock 2011-06-07 22:21:19 UTC
What are the expected parameters, their range, optional parameters, displayed v. non-displayed parameters, and any other constraints?

Comment 2 Ryan McCabe 2011-06-10 06:49:31 UTC
Currently, attributes that will be configurable are:

"ipaddr", "login", "passwd", "passwd_script", "ssl", "port", "uuid", "separator", "ipport", and "power_wait"

ipaddr, login, passwd|passwd_script, and port are required. The attributes here have the same meanings and allowable values as they do in all the other agents. The only new option unique to this script is uuid (a string) which is optional.

Comment 3 Ryan McCabe 2011-06-14 20:07:45 UTC
It's also worth mentioning that all atrributes except "port" and "uuid" are configured when adding the fence device itself. The "port" and "uuid" attributes are configured when associating the fence device with a node (configuring the fence instance).

Comment 4 Ryan McCabe 2011-07-01 20:54:09 UTC
Added in upstream git commit 99255656b4eef4a57bd4c5de6b3f240d815a436d

Comment 5 Ryan McCabe 2011-07-02 04:02:45 UTC
Created attachment 510963 [details]
proposed fix

Comment 12 errata-xmlrpc 2011-12-06 10:07:11 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1510.html