Bug 1102444
Summary: | 'pcs stonith list' -> Error: no metadata for /usr/sbin/fence_check (and others) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Madison Kelly <mkelly> |
Component: | pcs | Assignee: | Chris Feist <cfeist> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.5 | CC: | cluster-maint, djansa, rbalakri, rsteiger, tojeline, tommi.tervo |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pcs-0.9.121-1.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-14 07:22:02 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: |
Description
Madison Kelly
2014-05-29 01:12:18 UTC
Fence agents do not contain these files, so moving to other package Thanks Marek. I should have verified the packages before filing the bug. Chris, 'fence_check', 'fence_node' and 'fence_tool' are from 'cman'. I'm not sure if this should still be handled by pcs though, as it does seem reasonable that any 'fence_$foo' should have at least a cursory XML. The counter argument though being that they'll never be configured in cluster.conf or pcs, so... I'll leave that for you and the others to decide. :) Digimer, Yes, those definitely should not be showing up. They've been blacklisted and should no longer be showing up. Upstream patch here: https://github.com/feist/pcs/commit/d58336f5af61b8056456a538b7b508d2ebae9715 Fixed in pcs-0.9.121-1.el6 [root@bid-05 ~]# rpm -q pcs pcs-0.9.121-1.el6.x86_64 [root@bid-05 ~]# pcs stonith list | grep Error [root@bid-05 ~]# 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-2014-1526.html |