Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The current version doesn't monitor replication and metrics are coded in the script, in order to have more flexibility and be able to offer metrics about aspects such as replication status and others i have made some changes which can be found in the following PR:
https://github.com/performancecopilot/pcp/pull/1310
With these changes the user can define extra metrics via the configuration file.
Version-Release number of selected component (if applicable):
RHEL8
Additional info:
PR provided:
https://github.com/performancecopilot/pcp/pull/1310
Marking as FailedQA for the following reasons:
1) Registration of ds389 pmda does not work due to syntax errors in pmdads389.pl
- Lines 265 and 267 of the pmdads389.pl contain misspelled keywords 'elif' instead of 'elsif'.
2) In previous versions of ds389 pmda it was possible to register the pmda even when the server was not up/running. Now, the registration is possible only with running server. I am considering this as a regression.
Thanks Jan, good pickups - Raul and/or Marko, are you guys able to look into these issues?
Longer term could be a candidate PMDA for python conversion if that's your native language.
cheers.
Thanks Jan - we'll look into part #2 soon. Your initial fix is upstream ...
commit ef4468872a5bf9ce944f10d557064f4f7110d45f
Author: Jan Kurik <jkurik>
Date: Tue Sep 28 08:06:34 2021 +0200
Fix of a syntax error in pmdads389.pl
Part #2 now fixed upstream...
commit fabe05a9fc4d1779882edb60a7450cc492c0daaa
Author: Nathan Scott <nathans>
Date: Wed Oct 6 11:56:32 2021 +1100
pmdads389: allow installation when ds389 server is down
Recent extensions to the ds389 PMDA have resulted in an
accidental failure to install when the server is not up
(picked up by QA). This fixes that, and also reduces a
bit of log noise in this (expected sometimes) scenario.
Related to Red Hat BZ #1966122
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