Bug 864036
| Summary: | iSCSI session are not restored after reboot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Bruno Goncalves <bgoncalv> |
| Component: | iscsi-initiator-utils | Assignee: | Chris Leech <cleech> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Bruno Goncalves <bgoncalv> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | btaneja, jkortus, mcsontos, mnovacek, prajnoha, sudha, tmaria, wattersm, xiaoli |
| Target Milestone: | rc | Keywords: | TestBlocker, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | iscsi-initiator-utils-6.2.0.873-7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 10:52:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 883874, 1080147 | ||
|
Description
Bruno Goncalves
2012-10-08 12:16:16 UTC
Problem is still reproducible with: rpm -q iscsi-initiator-utils iscsi-initiator-utils-6.2.0.873-2.el7.x86_64 uname -r 3.7.0-0.36.el7.x86_64 There is a problem with systemd dependencies at boot: iscsi is started before network. So I tried restarting iscsid later after boot but session is still not restored. `iscsiadm -m node -l` works for me. Adding the line to rc.local. There's also a note in the /etc/init.d/iscsi init script: # Note we should have $network in Required-Start/Stop but we don't because if # we would require network chkconfig will put us directly after NetworkManager # when using NM, which will make our see if the network is up test succeed # while NM is actually still configuring the network. By not requiring network # chkconfig will use the chkconfig header to determine our start prio, starting # us after the old network service, but before NM (netfs does this the same). (adding Required-Start: $network iff using network.service instead of NetworkManager.service should solve the issue) *** Bug 958864 has been marked as a duplicate of this bug. *** Is there any plan on how to solve this permanently with for example systemctl.service with proper dependencies? This should be fixed with iscsi-initiator-utils-6.2.0.873-7, which is in sync with f19 and has proper systemd unit files. The problem continues on RHEL7. rpm -q iscsi-initiator-utils iscsi-initiator-utils-6.2.0.873-7.el7.x86_64 uname -r 3.10.0-0.rc4.59.el7.x86_64 iscsiadm -m discovery na3170b.lab.bos.redhat.com:3260 via sendtargets iscsiadm -m session iscsiadm: No active sessions. From /var/log/messages: Jun 21 11:28:17 ibm-x3500m4-01 kernel: [ 16.429909] Loading iSCSI transport class v2.0-870. Jun 21 11:28:17 ibm-x3500m4-01 dbus[654]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jun 21 11:28:17 ibm-x3500m4-01 systemd[1]: Started Open-iSCSI. Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: iscsiadm: Could not login to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260]. Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: iscsiadm: Could not login to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260]. Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: iscsiadm: Could not log into all portals Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: Logging in to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260] (multiple) Jun 21 11:28:17 ibm-x3500m4-01 iscsiadm[1118]: Logging in to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260] (multiple) Jun 21 11:28:17 ibm-x3500m4-01 systemd[1]: iscsi.service: main process exited, code=exited, status=12/n/a Jun 21 11:28:17 ibm-x3500m4-01 systemd[1]: Failed to start Login and scanning of iSCSI devices. Jun 21 11:28:17 ibm-x3500m4-01 systemd[1]: Unit iscsi.service entered failed state. Okay seems the culprit now is selinux. Making it permissive the sessions start after reboot. Jun 21 11:28:18 ibm-x3500m4-01 avahi-daemon[638]: Registering new address record for fe80::e61f:13ff:fee0:1bf8 on em1.*. Jun 21 11:28:18 ibm-x3500m4-01 avahi-daemon[638]: Registering new address record for fe80::e61f:13ff:fee0:1bf9 on em2.*. Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from getattr access on the directory /etc/modprobe.d. For complete SELinux messages. run sealert -l 968e2e66-9b85-4e6f-bf17-1d4eb6b0cba7 Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:18 ibm-x3500m4-01 avahi-daemon[638]: Registering new address record for fe80::e61f:13ff:fee0:1bfa on em3.*. Jun 21 11:28:18 ibm-x3500m4-01 iscsid: iSCSI daemon with pid=1144 started! Jun 21 11:28:18 ibm-x3500m4-01 iscsid: Could not insert module tcp. Kmod error -38 Jun 21 11:28:18 ibm-x3500m4-01 iscsid: Could not insert module tcp. Kmod error -38 Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from getattr access on the directory /etc/modprobe.d. For complete SELinux messages. run sealert -l 968e2e66-9b85-4e6f-bf17-1d4eb6b0cba7 Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:18 ibm-x3500m4-01 setroubleshoot: SELinux is preventing /usr/sbin/iscsid from search access on the directory modules. For complete SELinux messages. run sealert -l ff4fcc47-5106-4ef0-82e6-a2041654710c Jun 21 11:28:19 ibm-x3500m4-01 avahi-daemon[638]: Registering new address record for fec0:0:a10:4000:e61f:13ff:fee0:1bf8 on em1.*. (In reply to Bruno Goncalves from comment #12) > Okay seems the culprit now is selinux. What is the version of selinux-policy installed? That should be fixed as of 3.12.1-51. Thank you, I was using selinux-policy-3.12.1-48.el7 With selinux-policy-3.12.1-52.el7 it seems to work. It has been fixed on iscsi-initiator-utils-6.2.0.873-7.el7.x86_64 selinux-policy-3.12.1-59.el7.noarch This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. I'm still seeing this issue on RHEL (CentOS) 7.5. The system has selinux-policy-3.13.1-192.el7_5.4.noarch and iscsi-initiator-utils-6.2.0.874-7.el7.x86_64 installed. After reboot only one iscsi target is logged in to despite node.startup being set to automatic for all nodes. [root@ovirt-node-production1 iscsi]# grep -r node.startup * nodes/iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db/192.168.111.5,3260,1/default:node.startup = automatic nodes/iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db/192.168.112.5,3260,1/default:node.startup = automatic nodes/iqn.1984-05.com.dell:powervault.md3800i.600a098000601b4700000000549b893a/192.168.111.4,3260,1/default:node.startup = automatic nodes/iqn.1984-05.com.dell:powervault.md3800i.600a098000601b4700000000549b893a/192.168.112.4,3260,1/default:node.startup = automatic nodes/iqn.1994-12.com.promise.f5.3.65.55.1.0.0.20/10.201.64.101,3260,1/default:node.startup = automatic nodes/iqn.1994-12.com.promise.f5.3.65.55.1.0.0.20/10.201.64.102,3260,1/default:node.startup = automatic Before rebooting all targets are logged in. [root@ovirt-node-production1 iscsi]# iscsiadm -m session tcp: [1] 192.168.111.5:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db (non-flash) tcp: [2] 192.168.111.4:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a098000601b4700000000549b893a (non-flash) tcp: [3] 192.168.112.4:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a098000601b4700000000549b893a (non-flash) tcp: [4] 10.201.64.101:3260,1 iqn.1994-12.com.promise.f5.3.65.55.1.0.0.20 (non-flash) tcp: [5] 10.201.64.102:3260,1 iqn.1994-12.com.promise.f5.3.65.55.1.0.0.20 (non-flash) tcp: [6] 192.168.112.5:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db (non-flash) After reboot only one target is active. username@workstation:~$ ssh root@ovirt-node-production1 Last login: Tue Aug 7 13:37:07 2018 from 10.209.44.227 [root@ovirt-node-production1 ~]# iscsiadm -m session tcp: [1] 192.168.111.5:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db (non-flash) tcp: [2] 192.168.112.5:3260,1 iqn.1984-05.com.dell:powervault.md3800i.600a09800060188f0000000054af52db (non-flash) I can provide logs as needed. I am seeing this problem on Red Hat Enterprise Linux Server release 7.6 (Maipo) Kernel Version: 3.10.0-957.12.2.el7.x86_64 running on VMWare Was logged into target before a reboot. After reboot, see the following messages: Feb 06 17:51:25 MD161-3033-04 iscsiadm[23980]: iscsiadm: No matching sessions found Feb 06 17:51:25 MD161-3033-04 iscsid[21592]: iscsid shutting down. The very first time after a reboot does not work. As a workaround, Once i do "iscsiadm --mode node --targetname iqn.1992-08.com.netapp:sn.26fa40d9362a11ea8c28005056b3aea6:vs.5 --login" it starts working thereafter. I am seeing this problem on Red Hat Enterprise Linux Server release 7.8 kernel version : 3.10.0-1127.18.2.el7.x86_64 I need to issue the iscsiadm --mode node -targetname --login every time i reboot the system I believe I came across this issue on this node: Booted kernel: 3.10.0-1062.el7.x86_64 $ grep selinux-policy sos_commands/yum/yum_list_installed selinux-policy.noarch 3.13.1-252.el7.1 @os-7.7.0 selinux-policy-devel.noarch 3.13.1-252.el7.1 @os-7.7.0 selinux-policy-targeted.noarch 3.13.1-252.el7.1 @os-7.7.0 $ grep iscsi-initiator-utils sos_commands/yum/yum_list_installed iscsi-initiator-utils.x86_64 6.2.0.874-11.el7 @os-7.7.0 iscsi-initiator-utils-iscsiuio.x86_64 6.2.0.874-11.el7 @os-7.7.0 --------- Its cluster node is not showing this issue, and its running on different version of selinux-policy: Booted kernel: 3.10.0-1062.el7.x86_64 $ grep selinux-policy sos_commands/yum/yum_list_installed selinux-policy.noarch 3.13.1-266.el7 @os-7.7.3 selinux-policy-devel.noarch 3.13.1-266.el7 @os-7.7.3 selinux-policy-targeted.noarch 3.13.1-266.el7 @os-7.7.3 $ grep iscsi-initiator-utils sos_commands/yum/yum_list_installed iscsi-initiator-utils.x86_64 6.2.0.874-17.el7 @os-7.7.3 iscsi-initiator-utils-iscsiuio.x86_64 6.2.0.874-17.el7 @os-7.7.3 --------- Have not tried to update "selinux-policy" yet and reboot the server. Will share the results as the case progresses. |