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.
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-2017:1861
Description of problem: * the systemd-initctl service is not confined, should it be confined? Version-Release number of selected component (if applicable): selinux-policy-3.13.1-93.el7.noarch selinux-policy-devel-3.13.1-93.el7.noarch selinux-policy-doc-3.13.1-93.el7.noarch selinux-policy-minimum-3.13.1-93.el7.noarch selinux-policy-mls-3.13.1-93.el7.noarch selinux-policy-sandbox-3.13.1-93.el7.noarch selinux-policy-targeted-3.13.1-93.el7.noarch systemd-219-25.el7.x86_64 systemd-devel-219-25.el7.x86_64 systemd-journal-gateway-219-25.el7.x86_64 systemd-libs-219-25.el7.x86_64 systemd-networkd-219-25.el7.x86_64 systemd-python-219-25.el7.x86_64 systemd-resolved-219-25.el7.x86_64 systemd-sysv-219-25.el7.x86_64 How reproducible: * always Steps to Reproduce: # service systemd-initctl status Redirecting to /bin/systemctl status systemd-initctl.service ● systemd-initctl.service - /dev/initctl Compatibility Daemon Loaded: loaded (/usr/lib/systemd/system/systemd-initctl.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-initctl.service(8) # service systemd-initctl start Redirecting to /bin/systemctl start systemd-initctl.service # service systemd-initctl status Redirecting to /bin/systemctl status systemd-initctl.service ● systemd-initctl.service - /dev/initctl Compatibility Daemon Loaded: loaded (/usr/lib/systemd/system/systemd-initctl.service; static; vendor preset: disabled) Active: active (running) since Wed 2016-08-10 16:47:02 CEST; 1s ago Docs: man:systemd-initctl.service(8) Main PID: 11091 (systemd-initctl) Status: "Processing requests..." CGroup: /system.slice/systemd-initctl.service └─11091 /usr/lib/systemd/systemd-initctl Aug 10 16:47:02 rhel71.localdomain systemd[1]: Started /dev/initctl Compatib.... Aug 10 16:47:02 rhel71.localdomain systemd[1]: Starting /dev/initctl Compati.... Hint: Some lines were ellipsized, use -l to show in full. # ps -efZ | grep initctl system_u:system_r:init_t:s0 root 11091 1 0 16:47 ? 00:00:00 /usr/lib/systemd/systemd-initctl unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 11125 11150 0 16:47 pts/0 00:00:00 grep --color=auto initctl #