Bug 1963938

Summary: Mark pcp-pmda-* packages configuration files or every file shpiped under /etc with %config flag.
Product: Red Hat Enterprise Linux 8 Reporter: mkenjale
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED DUPLICATE QA Contact: Jan Kurik <jkurik>
Severity: high Docs Contact: Apurva Bhide <abhide>
Priority: unspecified    
Version: 8.4CC: agerstmayr, jkurik, mgoodwin, nathans, patrickm, peter.vreman, pkhedeka
Target Milestone: beta   
Target Release: 8.5   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 00:16:38 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 mkenjale 2021-05-24 12:35:28 UTC 
Description of problem:
------------------------
PCP PMDA pcp-pmda-bcc /etc files not marked as config files

Version-Release number of selected component (if applicable):
------------------------
pcp-pmda-bcc-5.2.5-4.el8.x86_64

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
I modified the file /etc/pcp/bcc/bcc.conf to enable the needed bcc modules.
Now the RPM Verify fails because the file is missing the %config in the RPM:

--------
$ rpm -V pcp-pmda-bcc
S.5....T.    /etc/pcp/bcc/bcc.conf
$ rpm -qc pcp-pmda-bcc
$
--------

Actual results:
---------------
$ rpm -V pcp-pmda-bcc
S.5....T.    /etc/pcp/bcc/bcc.conf
$ rpm -qc pcp-pmda-bcc
$

Expected results:
------------------
rpm verification shall mark the configuration files with %config flag.

Additional info:
Comment 1 Nathan Scott 2021-05-25 00:16:38 UTC 
Thanks for the report - this has been fixed in more recent versions of PCP, e.g.

$ rpm -qc pcp-pmda-bcc
/etc/pcp/bcc/bcc-tracepoint.conf
/etc/pcp/bcc/bcc-uprobe.conf
/etc/pcp/bcc/bcc-usdt.conf
/etc/pcp/bcc/bcc.conf

$ rpm -qv pcp-pmda-bcc
pcp-pmda-bcc-5.3.1-1.x86_64

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