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.

Bug 1988403

Summary: pmcd configuration not updated for python3
Product: Red Hat Enterprise Linux 8 Reporter: Abhijeet Joshi <abjoshi>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Jan Kurik <jkurik>
Severity: high Docs Contact: Apurva Bhide <abhide>
Priority: high    
Version: 8.4CC: agerstmayr, cstratak, jkurik, nathans, peter.vreman
Target Milestone: betaKeywords: Bugfix, Triaged
Target Release: 8.6Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pcp-5.3.3-1.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 13:30:52 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 Abhijeet Joshi 2021-07-30 13:38:32 UTC 
Description of problem:
After Leapp upgrade the PMCD configuration is not getting updated for Python3.


Version-Release number of selected component (if applicable):
RHEL 8.4


How reproducible:
Every time after upgrading the system to RHEL 8.4 using Leapp.


Steps to Reproduce:

[1] After upgrading with leapp below errors for PCP are logged.
~~~
$ sudo grep pcp /var/log/messages | tail -n10
Jul 28 06:29:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 06:39:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 06:49:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 06:59:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:09:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:19:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:29:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:39:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:49:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
Jul 28 07:59:24 li-lc-1667 pcp-pmie[2096]: Restart unresponsive PMDAs pmdanfsclient[4]@li-lc-1667
~~~

[2] The problem occurs because of 'python' in the file '/etc/pcp/pmcd/pmcd.conf' instead of 'python3':
~~~
$ cat /etc/pcp/pmcd/pmcd.conf
#
# Name  Id      IPC     IPC Params      File/Cmd
# Performance Metrics Domain Specifications
# This file is automatically generated during the build
root    1       pipe    binary          /var/lib/pcp/pmdas/root/pmdaroot
pmcd    2       dso     pmcd_init       /var/lib/pcp/pmdas/pmcd/pmda_pmcd.so
proc    3       pipe    binary          /var/lib/pcp/pmdas/proc/pmdaproc -d 3
linux   60      pipe    binary          /var/lib/pcp/pmdas/linux/pmdalinux
nfsclient       62      pipe    binary  python /var/lib/pcp/pmdas/nfsclient/pmdanfsclient.python
dm      129     pipe    binary          /var/lib/pcp/pmdas/dm/pmdadm -d 129
~~~

Expected results:
-------------------
The Leapp migration tool should take care of fixing python2-> python3 issues without user intervention. 

Additional info:
Comment 2 Nathan Scott 2021-08-02 22:22:39 UTC 
Looking into this, I believe there's a relatively simple workaround until we have a proper fix:

# touch /var/lib/pcp/pmdas/nfsclient/.NeedInstall
# systemctl restart pmcd

cheers.
Comment 3 Peter Vreman 2021-08-04 14:42:42 UTC 
Confirming the following fix is was i am using in the post-leapp steps now and that it is working after the next reboot
~~~
sed -r 's/(\s)python(\s)/\1python3\2/' -i /etc/pcp/pmcd/pmcd.conf
~~~
Comment 9 errata-xmlrpc 2022-05-10 13:30:52 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