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 default pcp.conf contains the following lines

    # directory for PCP specific nssdb
    # Standard path: /etc/pcp/nssdb
    PCP_NSSDB_DIR=/etc/pcp/nssdb

Actually PCP_NSSDB_DIR is not used anywhere. According to pmintro(1)

    PCP_SECURE_DB_PATH
        When set, this variable specifies an alternate certficate database path
        for client tools.  Similar to the action of the -C option for pmcd(1)
        and pmproxy(1).

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

    # cat /etc/redhat-release 
    Red Hat Enterprise Linux Server release 7.8 (Maipo)

    # rpm -qf /etc/pcp.conf 
    pcp-conf-4.3.2-6.el7.x86_64

How reproducible: Always

Steps to Reproduce: not appliccable

Actual results: pcp.conf by default contains incorrect information.

Expected results: the file should not contain incorrect information.

Additional info:

The misleading information led a customer to waste time attempting to set
secure communication between pmlogger and a remote pmdc.

Fixed in upstream with commit:

commit 5890d31f0e07b03bd8a3c602be31f339269b14a5 (HEAD -> master, upstream/master, origin/master, origin/HEAD)
Author: Andreas Gerstmayr <agerstmayr>
Date:   Tue Apr 28 18:30:21 2020 +0200

    rename PCP_NSSDB_DIR to PCP_SECURE_DB_PATH in pcp.conf
    
    There was no reference to PCP_NSSDB_DIR in the source code, only to
    PCP_SECURE_DB_PATH. pcpintro(1) also references PCP_SECURE_DB_PATH.
    
    Resolves Red Hat BZ #1826020

Will be resolved via rebase to pcp-5.1 in RHEL 8.3.

*** This bug has been marked as a duplicate of bug 1792971 ***

Verified on pcp-5.1.1-2.el8 build.