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 1341114

Summary: [packaging] pcs should mark known (existing or not) %config files in the spec (/etc/sysconfig/pcsd, /var/lib/pcsd/tokens, ...)
Product: Red Hat Enterprise Linux 7 Reporter: Jan Pokorný [poki] <jpokorny>
Component: pcsAssignee: Ivan Devat <idevat>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.1CC: cfeist, cluster-maint, idevat, omular, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.152-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 20:58:55 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 Jan Pokorný [poki] 2016-05-31 09:56:17 UTC
# rpm -qf /var/lib/pcsd/tokens      
> file /var/lib/pcsd/tokens is not owned by any package

It's up to the consideration if this file should not be tracked as well.
If so, the current behavior on upgrades would be retained using
"%config %ghost" tagging (a requirement to reauthenticate upon each
pcs update is hardly desirable).

As a bonus, the mentioned file would be listed with 'rpm -qc pcs'.
Moreover, that query currently shows nothing(!), which I call solidly
broken when there are files likes /etc/sysconfig/pcsd that should
definitely be listed.

See also:
https://fedoraproject.org/wiki/PackagingDrafts/Logfiles

Comment 1 Jan Pokorný [poki] 2016-05-31 09:58:51 UTC
Also COPYING file should rather be tagged with %license so that it's
shown with "rpm -qL pcs".

Comment 3 Tomas Jelinek 2016-06-07 14:20:38 UTC
pcsd configs:
/var/lib/pcsd/cfgsync_ctl
/var/lib/pcsd/pcsd.cookiesecret
/var/lib/pcsd/pcsd.crt
/var/lib/pcsd/pcsd.key
/var/lib/pcsd/pcs_settings.conf
/var/lib/pcsd/pcs_users.conf
/var/lib/pcsd/tokens

Comment 4 Ivan Devat 2016-06-22 12:16:14 UTC
Before fix:
[vm-rhel72-1 /] $ rpm -q pcs
pcs-0.9.143-15.el7.x86_64
[vm-rhel72-1 /] $ rpm -qc pcs

After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-1.el7.x86_64
[vm-rhel72-1 ~] $ rpm -qc pcs
/etc/sysconfig/pcsd
/var/lib/pcsd/cfgsync_ctl
/var/lib/pcsd/pcs_settings.conf
/var/lib/pcsd/pcs_users.conf
/var/lib/pcsd/pcsd.cookiesecret
/var/lib/pcsd/pcsd.crt
/var/lib/pcsd/pcsd.key
/var/lib/pcsd/tokens

Comment 8 errata-xmlrpc 2016-11-03 20:58:55 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, 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://rhn.redhat.com/errata/RHSA-2016-2596.html