Bug 1380409 - openscap-daemon rpm does not create/claim ownership of /etc/oscapd/config.ini
Summary: openscap-daemon rpm does not create/claim ownership of /etc/oscapd/config.ini
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openscap-daemon
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Preisler
QA Contact: Matus Marhefka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-29 14:15 UTC by Marek Haicman
Modified: 2018-04-11 00:07 UTC (History)
3 users (show)

Fixed In Version: openscap_daemon-0.1.10-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-11 00:06:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1093 0 None None None 2018-04-11 00:07:14 UTC

Description Marek Haicman 2016-09-29 14:15:07 UTC 
Description of problem:
From the user perspective, it is definitely better to know, which package owns particular config file. Also it's nicer, if the config file is created during installation.

/etc/oscapd/config.ini is neither owned nor created, even though it is used by openscap-daemon.

Version-Release number of selected component (if applicable):
openscap-daemon-0.1.6-1.el7.noarch

How reproducible:
reliably

Steps to Reproduce:
1. yum install -y openscap-daemon
2. cat /etc/oscapd/config.ini
2. rpm -Vv openscap-daemon | grep config.ini


Actual results:
2. No such file or directory
3. No line is printed

Expected results:
2. Default config or empty file with comment is present
3. .........  c /etc/oscapd/config.ini

Additional info:
Comment 10 errata-xmlrpc 2018-04-11 00:06:49 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://access.redhat.com/errata/RHBA-2018:1093
Note You need to log in before you can comment on or make changes to this bug.