This bug is still present in Fedora 27, could you please add the configuration file for the /var/run directory?

+++ This bug was initially created as a clone of Bug #1492377 +++

On current Fedora 26, trying to start tgtd.service (the iscsi initiator, i.e. 'server', service) fails due to an SELinux denial:

Sep 16 12:12:06 support.domain.local systemd[1]: Starting tgtd iSCSI target daemon...
Sep 16 12:12:06 support.domain.local audit[1135]: AVC avc:  denied  { create } for  pid=1135 comm="tgtd" name="tgtd" scontext=system_u:system_r:tgtd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=0
Sep 16 12:12:06 support.domain.local tgtd[1135]: (null): ipc_init(781) failed to open lock file for management IPC
Sep 16 12:12:06 support.domain.local systemd[1]: tgtd.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 12:12:11 support.domain.local tgtadm[1137]: tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected
Sep 16 12:12:11 support.domain.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tgtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 16 12:12:11 support.domain.local systemd[1]: tgtd.service: Control process exited, code=exited status=107
Sep 16 12:12:11 support.domain.local systemd[1]: Failed to start tgtd iSCSI target daemon.
Sep 16 12:12:11 support.domain.local systemd[1]: tgtd.service: Unit entered failed state.
Sep 16 12:12:11 support.domain.local systemd[1]: tgtd.service: Failed with result 'exit-code'.

Looks like it's trying to create a file in /var/run and being denied. This is interfering with openQA tests, as we need to run an iSCSI server.

--- Additional comment from Joshua Roys on 2017-09-19 22:00:26 EDT ---

I have this issue also.

Quick fix:
$ cat /etc/tmpfiles.d/tgtd.conf 
D    /var/run/tgtd 0750 root root -

--- Additional comment from Fedora End Of Life on 2018-05-03 04:02:14 EDT ---

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

--- Additional comment from Fedora End Of Life on 2018-05-29 08:22:01 EDT ---

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.