Description of problem:
There is a significant change in ownership/existence of PMDA files of pcp-5.2.X-Y.el8 release, comparing to previous (< pcp-5.1.X-Y.el8) releases.

I am unsure whether this is intentional or not, but it is causing issues with a lot files left on a filesystem without a relation to an RPM package.


Version-Release number of selected component (if applicable):
* pcp-5.2.3-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Install pcp-5.2.3-1.el8 RPM package on a RHEL-8 system
# yum install -y pcp

2. List the directory containing PMDA's files
# ls /var/lib/pcp/pmdas/

3. Check which package owns files located in /var/lib/pcp/pmdas/<PMDA> directory
# rpm -qf /var/lib/pcp/pmdas/mssql

Actual results:
The following command 

# ls /var/lib/pcp/pmdas/

lists PMDAs directories and files (symlinks) for all PMDAs available in system, even these are not installed. As such, query for a file ownership of a directory of a non-installed PMDA (i.e. pcp-pmda-mssql) shows missing ownership.

# rpm -qf /var/lib/pcp/pmdas/mssql
file /var/lib/pcp/pmdas/mssql is not owned by any package


When the pcp package is uninstalled

# yum remove -y pcp

all the PMDAs directories and files which were not owned by a package are left on filesystem.


This is a change in behavior of the pcp package and its files comparing to older PCP releases, where the pcp RPM package does not deliver files/directories for non-installed PMDAs.

Expected results:
All the files and directories delivered by pcp RPM should be owned by this RPM.


Additional info:
I am unsure if this is a bug or just a change of the way how PCP delivers its PMDAs. So, if this behavior is intentional, feel free to WONTFIX.
There is currently no impact on functionality or security of the system, I can think of, caused by this issue. The only unwanted effect are leftovers of files and directories after un-installation of pcp RPM package.