Description of problem:
When running isns discovery with iscsiadm/iscsid we get the selinux error in the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 295460 [details]
Here is the selinux output.
Created attachment 295461 [details]
patch to allow isns discovery
Here is a patch made over 2.4.6-121.
I know it is late. As I said in the other bz, I have been running without
selinux on all my machines when I thought it was always on, so I have been
redoing all my testing and Barry/QE has been catching the ones I have not
started on. Sorry about all this.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
The AVC messages that you attached is incorrect. Did you hand edit this or was
it created by the kernel directly?
The avc specifies the port as being iscsi_t rather then port_t.
Created attachment 295541 [details]
selinux port outpout
I found the problem. Originally I got the attached selinux error, and for the
PORT_TYPE I typed in iscsid_t instead of iscsi_port_t. When I use the correct
type I do not need the change in the other comment.
Is there any way I can make it so open-iscsi can always use port 3205 at least?
It is the default port for isns traffic in the isns spec, or do we always have
to do the semanage port command?
Fixed in selinux-policy-2.4.6-122.el5
Mike, could you please try the latest selinux policy (128 or >121) and reply
here whether it solves the problem? Thanks.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.