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:
TuneD exposes its API on the D-Bus. It has been working quite well so far, but recently new use cases have arose. E.g. for usage with the containers it's required to have API exposed on the Unix Domain Socket.

Version-Release number of selected component (if applicable):
tuned-2.18.0

How reproducible:
Always

Steps to Reproduce:
1. Check available TuneD APIs (control points)
2.
3.

Actual results:
No API exposed on the socket, no TuneD control socket

Expected results:
TuneD control socket with defined API

Additional info:
For the start just mirror the D-Bus API on the socket. With D-Bus ACLs are controlled by Polkit, with sockets just use file permissions for it. Also provide control mechanism to enable/disable the socket API, e.g. through the tuned-main.conf configuration file and maybe also throught the command line option. There should be also option allowing customization of the socket path/name.

Upstream PR:
https://github.com/redhat-performance/tuned/pull/470

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 (tuned bug fix and enhancement update), 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-2023:2585