Hide Forgot
The default transport in the initiator is TCP, when one wants to use other transport (e.g iser) the transport of the relevant interface has to be changed before attempting to do the actual (non discovery) login. When iscsiadm is being run by higher level software layer, e.g clustering / virtualization such as VDSM or alike daemon, if that entity crashes between the time it has set the transport to the non default transport to the time it attempted to issue the login and received the result of that login, that iscsi node entry remains in a state where its transport isn't TCP which could lead to errors when the system reboots and attempt to connect to targets/luns previously discovered. The VDSM team asked for iscsiadm to accept the transport in its command line. For example, the request is to consolidate these two calls into one: iscsiadm -m node --targetname tg1 --portal 192.168.20.20:3260 --op update -n iface.transport_name -v iser iscsiadm -m node --targetname tg1 --portal 192.168.20.20:3260 --login
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not appear to meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact your EPM to request a re-evaluation of the issue, citing a clear business justification.