Bug 1287301
| Summary: | fence_compute does not advertise itself correctly | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Andrew Beekhof <abeekhof> |
| Component: | fence-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED ERRATA | QA Contact: | Asaf Hirshberg <ahirshbe> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | abeekhof, cluster-maint, oblaut |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | fence-agents-4.0.11-38.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 04:48:41 UTC | Type: | Bug |
| 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: | 1185030, 1287303 | ||
|
Description
Andrew Beekhof
2015-12-01 22:39:33 UTC
Andrew, I got the following the expected result from fence-agents4.0.11-27 </resource-agent> [root@overcloud-controller-2 ~]# fence_compute -o metadata|grep -A3 action <parameter name="action" unique="0" required="1"> <getopt mixed="-o, --action=[action]" /> <content type="string" default="off" /> <shortdesc lang="en">Fencing Action</shortdesc> </parameter> -- <actions> <action name="on" on_target="1" automatic="1"/> <action name="off" /> <action name="status" /> <action name="list" /> <action name="list-status" /> <action name="monitor" /> <action name="metadata" /> </actions> </resource-agent> Did I missed something? as it fixed in fence-agents-4.0.11-38.el7 They must have forgotten to close the bug Correct. It was already fixed, so I set Resolves for this bz for fence-agents-4.0.11-38.el7, as that was missing from the changelog. 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. https://rhn.redhat.com/errata/RHBA-2016-2373.html |