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:
Atomic RPM package or SPEC file haven't move atomic.d/ into /etc directory, it also means we can't find openscap under the /etc/atomic.d/.

Version-Release number of selected component (if applicable):
$ rpm -q atomic docker kernel PyYAML
atomic-1.10.3-1.el7.x86_64
docker-1.10.3-26.el7.x86_64
kernel-3.10.0-327.el7.x86_64
PyYAML-3.10-11.el7eng.x86_64

$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.2 (Maipo)

How reproducible:
always

Steps to Reproduce:
1. atomic -h

Actual results:
$ atomic -h
/etc/atomic.d/ does not exist


Expected results:


Additional info:

You need to manually install PyYAML RPM package firstly avoid to encounter bug 1341916, and meanwhile, I tried to create atomic.d directory under the /etc, atomic cmdline works well, but it had better we can document something about /etc/atomic.d/openscap.

make install for atomic command should have created /etc/atomic.d directory.

Brent should we be doing a make install-openscap for RHEL systems?

We need to know the proposed openscap image name and then we can do something like that.  I'll add Martin here.

docker pull rhel7/openscap

rpm -qf /etc/atomic.d/openscap
atomic-1.10.3-2.el7.x86_64

But the directory /etc/atomic.d/ doesn't belong to any package, it's irrelevant with bug, I will file new one to track it.
# rpm -qf /etc/atomic.d/
file /etc/atomic.d is not owned by any package

the atomic -h works well, so move the bug to VERIFIED status.

*** Bug 1343595 has been marked as a duplicate of this bug. ***

*** Bug 1344623 has been marked as a duplicate of this bug. ***

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-2016:1273