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.
Bug 1365501 - avc error on isnsd when initiator tries to connect to it
Summary: avc error on isnsd when initiator tries to connect to it
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1390208
TreeView+ depends on / blocked
 
Reported: 2016-08-09 11:54 UTC by Bruno Goncalves
Modified: 2017-03-21 09:47 UTC (History)
10 users (show)

Fixed In Version: selinux-policy-3.7.19-298.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1390208 (view as bug list)
Environment:
Last Closed: 2017-03-21 09:47:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0627 0 normal SHIPPED_LIVE selinux-policy bug fix update 2017-03-21 12:29:23 UTC

Description Bruno Goncalves 2016-08-09 11:54:38 UTC 
Description of problem:
Configure an iSNS server, when an initiator tries to discover targets from it, there is an avc error event.

Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-292.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1.Configure isnsd service and tgtd target
# yum install -y isns-utils scsi-target-utils

### iSCSI target configuration:

# cat /etc/tgt/targets.conf
default-driver iscsi
<target iqn.2009-10.com.redhat:storage-1>
    write-cache off
    allow-in-use yes
    <backing-store /var/lib/tgtd/loop-disk-1-1>
        scsi_sn 1989911
        scsi_id 1989911
        lun 1
        bs-type rdwr
        device-type disk
    </backing-store>
</target>
iSNSServerIP 127.0.0.1
iSNSServerPort 3205
iSNS On

2.Try to discover targets from it
# yum install -y iscsi-initiator-utils

# iscsiadm -m discovery -t isns -p 127.0.0.1 
iscsiadm: Could not scan /sys/class/iscsi_transport.
iscsiadm: Could not scan /sys/class/iscsi_transport.
[  OK  ] iscsid: [  OK  ]
127.0.0.1:3260,1 iqn.2009-10.com.redhat:storage-1

3.Check for SElinux message on /var/log/messsages
setroubleshoot: SELinux is preventing /usr/sbin/isnsd from accept access on the tcp_socket . For complete SELinux messages. run sealert -l bbdac7e4-1bec-4a2a-8bc9-248938339717
Comment 13 errata-xmlrpc 2017-03-21 09:47:23 UTC 
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-2017-0627.html
Note You need to log in before you can comment on or make changes to this bug.