It looks like a leaked file descriptor.

Is this a redirection?

Minfei, can you have a look and answer questions in comment #5?

For now, I found that the denied message will appear, if kdump generates the initramfs during the kernel boot. In the other word, if someone flips the option force_rebuild, the denied message will always appear, otherwise it is fine.

Also, the denied message never appear, if I am disable the kdump service by systemctl.

(In reply to Milos Malik from comment #2)
> It looks like a leaked file descriptor.

As commented above, the error message will appear, if kdump generates the initramfs when systemctl trys to start the kdump.service. But it is fine to start the kdump service manually using "kdumpctl start".

So I think this issue may concern with systemd which may do not start kdump service correctly in selinux policy.

Thanks
Minfei

(In reply to Miroslav Grepl from comment #5)
> Is this a redirection?

Hi, Grepl.

As you commented it may concern with redirection issue, I tried to remove the pipe and redirection where kdump uses iscsiadm to get iscsi info. And the error message still appear from the selinux. Following it the code which kdump calls.

1) 
473     # Check once before getting explicit values, so we can output a decent
474     # error message.
475
476     if ! /sbin/iscsiadm -m session -r ${path} >/dev/null ; then
477         derror "Unable to find iscsi record for $path"
478         return 1
479     fi

2)
432     result=$(/sbin/iscsiadm --show -m session -r ${1} | grep "^${2} = ")
433     result=${result##* = }
434     echo $result

Thanks
Minfei

commit f29ce6902d8eb72d5badd64c06af011e100383ce
Author: Lukas Vrabec <lvrabec>
Date:   Mon Jun 29 13:06:55 2015 +0200

    Allow iscsid write to fifo file kdumpctl_tmp_t. Appears when kdump generates the initramfs during the kernel boot. BZ(1181476)

Moving back to correct state

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://rhn.redhat.com/errata/RHBA-2015-2300.html