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:
With the upgrade from RHEL 7.5 to RHEL 7.6, we rebased pcp on 4.1.0.
pcp 4.0.2 changed the pmdanfsclient from Perl to Python [1] and so did the script name:
/var/lib/pcp/pmdas/nfsclient/pmdanfsclient.pl
vs.
/var/lib/pcp/pmdas/nfsclient/pmdanfsclient.python
This results in messages like the following
Feb 4 11:10:26 xxx pcp-pmie[6361]: Restart unresponsive PMDAs pmdanfsclient[4]@xxx
And 'unresponsive' pmdanfsclient.
Version-Release number of selected component (if applicable): 4.1
How reproducible: Always
Steps to Reproduce:
1. Install RHEL 7.5 with pcp 3.x with pmdanfsclient; aka. pcp-pmda-nfsclient [rpm]
2. Use pmdanfsclient. Eg.
# grep pmdanfs /etc/pcp/pmcd/pmcd.conf
nfsclient 62 pipe binary perl /var/lib/pcp/pmdas/nfsclient/pmdanfsclient.pl
2. Upgrade to RHEL 7.6
Actual results:
Upgrade breaks pcp installation.
[1] https://fossies.org/linux/pcp/CHANGELOG
Expected results:
Upgrade of RHEL shouldn't break pcp installation.
Additional info:
Customer case will be attached in a hurry.
I'd suggest to get this at least documented in the release notes.
As a short-term workaround, customers can do the following to resolve this:
# touch /var/lib/pcp/pmdas/nfsclient/.NeedInstall
# systemctl restart pmcd
We'll look into a transparent solution for this for the next PCP release though. It affects more than just the nfsclient PMDA and some PMDAs have more complex upgrade requirements.
Thanks Oliver.
This is fixed in upstream PCP by the following commit ... planned for inclusion in RHEL7.7 now.
commit ce928bc8562a3702b7b577cf6d65b7b55ae4398c
Author: Nathan Scott <nathans>
Date: Wed Feb 6 12:19:46 2019 +1100
rc_pmcd: optional PMDA ./Upgrade to resolve upgrade issues
This change adds support for an (optional) PMDA ./Upgrade
script alongside the ./Install and ./Remove scripts. The
pmcd start script is also updated to support invocation of
these scripts directly, which allows platform independent
scripts to fix upgrade issues (typically pmcd.conf is at
the centre of these issues, but not always - could be the
PMDA configuration file(s) need fixing too, for example).
This shifts a handful of adhoc rpm/deb platform-specific
packaging scripts into a more formal process. It adds in
several additional fixups for upgrade problems seen in the
wild now - in particular relating to the transition from
one language implementation to another for some PMDAs, an
upgrade issue we had not previously come across.
QA can now been written to test these PMDA shell upgrade
snippets, independently to full-package upgrade tests. A
number of tests that do just that, for PMDAs affected by
re-implementation in recent times, are added here.
Resolves Red Hat BZ #1672291.
Description of problem: With the upgrade from RHEL 7.5 to RHEL 7.6, we rebased pcp on 4.1.0. pcp 4.0.2 changed the pmdanfsclient from Perl to Python [1] and so did the script name: /var/lib/pcp/pmdas/nfsclient/pmdanfsclient.pl vs. /var/lib/pcp/pmdas/nfsclient/pmdanfsclient.python This results in messages like the following Feb 4 11:10:26 xxx pcp-pmie[6361]: Restart unresponsive PMDAs pmdanfsclient[4]@xxx And 'unresponsive' pmdanfsclient. Version-Release number of selected component (if applicable): 4.1 How reproducible: Always Steps to Reproduce: 1. Install RHEL 7.5 with pcp 3.x with pmdanfsclient; aka. pcp-pmda-nfsclient [rpm] 2. Use pmdanfsclient. Eg. # grep pmdanfs /etc/pcp/pmcd/pmcd.conf nfsclient 62 pipe binary perl /var/lib/pcp/pmdas/nfsclient/pmdanfsclient.pl 2. Upgrade to RHEL 7.6 Actual results: Upgrade breaks pcp installation. [1] https://fossies.org/linux/pcp/CHANGELOG Expected results: Upgrade of RHEL shouldn't break pcp installation. Additional info: Customer case will be attached in a hurry. I'd suggest to get this at least documented in the release notes.