Red Hat Bugzilla – Bug 588990
iscsiadm can exit with status 19 (ENODEV) even when exec_iface_up() succeeds
Last modified: 2011-01-13 17:58:32 EST
Description of problem:
Line 1447 in open-iscsi-2.0-871-test4.bnx2i/usr/iscsiadm.c explicitly treats ENODEV as an non-anomalous situation, and allows passthrough to line 1450 (logging success) in this case.
However, the rc value which is tested is also used by return value, which is also used as the exit status. Consequently, this successful operation can be treated by calling scripts as a failure.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run the following command:
-m iface \
-I test-scsi-if-0 \
-n iface.net_ifacename \
echo "Exit status: $?"
...updated to use a different interface name if necessary
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. 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.
This is fixed in
It can be downloaded here:
Verified on RHEL5.6-Server-20101014.0
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, the open-iscsi administration utility (iscsiadm) interface update operation returned an error code, even though the operation was successful. This error has been fixed, the error detection code has been corrected, and the interface update now behaves as expected.
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 therefore 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.