RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1972277 - HA cluster PMDA to export pacemaker location constraints as labels
Summary: HA cluster PMDA to export pacemaker location constraints as labels
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcp
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 8.6
Assignee: Paul Evans
QA Contact: Jan Kurik
Apurva Bhide
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-15 14:52 UTC by Paul Evans
Modified: 2022-05-10 13:49 UTC (History)
4 users (show)

Fixed In Version: pcp-5.3.3-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 13:30:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:1765 0 None None None 2022-05-10 13:30:51 UTC

Description Paul Evans 2021-06-15 14:52:06 UTC
Description of Problem:
HA Cluster PMDA PM_TYPE_STRING metrics are unable to export their values through the pmproxy OpenMetrics API due to String type metrics being unsupported. 

The Pacemaker Location Constraint details are required to be able to pinpoint primary node. These location constraints need to be added as Labels in order to be exposed during export.

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

How reproducible:
Always

Steps to Reproduce:
1.) Install pcp-pmda-hacluster
# yum  install -y pcp pcp-pmda-hacluster

2.) Start pmcd service, install PMDA and start pmproxy Service
# systemctl start pmcd
# ./usr/libexec/pcp/pmdas/hacluster/Install
# systemctl start pmproxy

3.) Check for location constraints data in pmproxy output
# curl http://localhost:44323/metrics?names=ha_cluster.pacemaker | grep location_constraints

Actual Results:
Output of "curl" is as follows:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 25835    0 25835    0     0  43714      0 --:--:-- --:--:-- --:--:-- 43714
...

Expected Results:
The output should provide the location constraint information for pacemaker

Additional info:
Plan on adding the required location constraints data as labels to a new metric which
will be of a supported OpenMetrics data type in pmproxy.

Comment 1 Nathan Scott 2021-06-16 00:32:54 UTC
Tentatively setting this for 8.6 just to put it on a release radar, but earlier is still possible at this stage - let's get code upstream first.

Comment 2 Chris Feist 2021-06-22 16:33:56 UTC
One more note here, we also need the ability to report if promotable/ms resource on a node is in the promoted/master state or not.  Let me know if we need an additional bz for this or if we can include the fix in this bz.

Comment 3 Nathan Scott 2021-06-22 23:03:34 UTC
(In reply to Chris Feist from comment #2)
> One more note here, we also need the ability to report if promotable/ms
> resource on a node is in the promoted/master state or not.  Let me know if
> we need an additional bz for this or if we can include the fix in this bz.

Same BZ is fine.

Comment 5 Paul Evans 2021-06-25 11:28:05 UTC
Hi,

(In reply to Chris Feist from comment #2)
> One more note here, we also need the ability to report if promotable/ms
> resource on a node is in the promoted/master state or not.  Let me know if
> we need an additional bz for this or if we can include the fix in this bz.

The patch above also addresses these issues.

Paul

Comment 12 errata-xmlrpc 2022-05-10 13:30:36 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 (pcp bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:1765


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