Bug 800650
Summary: | Add symlinks for common fence types that utilize standards based agents | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Perry Myers <pmyers> | ||||
Component: | fence-agents | Assignee: | Marek Grac <mgrac> | ||||
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.3 | CC: | cluster-maint, djansa, mjuricek, sbradley, slevine, syeghiay | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | fence-agents-3.1.5-20.el6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 917747 917838 (view as bug list) | Environment: | |||||
Last Closed: | 2013-02-21 07:41:15 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 917747, 917838, 969136, 1031888 | ||||||
Attachments: |
|
Description
Perry Myers
2012-03-06 21:12:01 UTC
Created attachment 591829 [details]
Proposed patch
This patch adds support for creating symlink fence agents for fencing library (example with ilo2) and ipmilan (example with ilo3). We will have to decide which symlinks should be added.
Patches are in upstream: http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=87266bcbf3f1b71664e65d82fb6de9f8814cb19e http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=cd73f094f7c163aca57a1dc9d5138fb468846835 Unit test for (fence_ilo2, fence_ilo3, fence_imm, fence_idrac) fence_? -o metadata Functionality of agents needs to be checked only for fence_ilo3 (different default values) fence_ilo3 -o status -l LOGIN -p PASS -a IP 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-2013-0286.html |