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:
As seen while trying to work around https://bugzilla.redhat.com/show_bug.cgi?id=1380682 , systemd reset capabilities to 0 rather than merging them.

Version-Release number of selected component (if applicable):
$ rpm -q systemd
systemd-219-19.el7_2.13.x86_64

How reproducible:
each time

Steps to Reproduce:
1. install tor
2. add a file fix_rh_1375369.conf to /etc/systemd/system/tor.service.d/ with the following content:
[Service]
CapabilityBoundingSet=CAP_DAC_READ_SEARCH

3. systemctl daemon-reload
4.  systemctl show tor.service |grep -i cap


Actual results:

CapabilityBoundingSet=0

Expected results:
CapabilityBoundingSet=1220
(or at least, something which is not '0')

Additional info:

https://github.com/systemd/systemd/issues/1221 is quite similar, and both

b9d345b53ff0ee402c9dceee1bc14bf0d8907706 and 661b37b05be6720dc8678ba44ed6b321679aa260 might be the fixes

Definitely something we should check during 7.4 development.

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