Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
/etc/init.d/tgtd does not support command-line arguments to tgtd
Version-Release number of selected component (if applicable):
scsi-target-utils-1.0.24-2.el6.x86_64
How reproducible:
Need to include "--iscsi portal=x.x.x.x:3260" args to restrict socket binding on multi-homed system.
Steps to Reproduce:
1. have a multi-homed system
2. require iscsi to only bind to one NIC
3. fail :-)
Actual results:
tgtd binds to 0.0.0.0:3260 by default.
Expected results:
tgtd binds only to a specific IP.
Additional info:
Adding support is trivial:
***BEGIN PATCH***
--- tgtd 2012-03-20 14:22:28.000000000 -0500
+++ tgtd.local 2013-03-15 16:24:57.298215576 -0500
@@ -31,7 +31,7 @@
[ -x /usr/sbin/$exec ] || exit 5
echo -n $"Starting $prog: "
# Note /dev/null redirection to silence rdma not found messages
- daemon $exec >/dev/null 2>&1
+ daemon $exec ${TGTD_OPTIONS} >/dev/null 2>&1
retval=$?
if [ $retval -ne 0 ] ; then
failure
***END PATCH***
and since /etc/sysconfig/tgtd does not contain a TGTD_OPTIONS line, default behaviour remains unchanged.
The workaround is obvious, but this needs to get into an errata pkg so I'm not customizing initscripts to support a fully-documented feature (see http://stgt.sourceforge.net/manpages/tgtd.8.html).
Should be possible to include in errata since default behaviour does not change.
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.
http://rhn.redhat.com/errata/RHBA-2013-1684.html
Description of problem: /etc/init.d/tgtd does not support command-line arguments to tgtd Version-Release number of selected component (if applicable): scsi-target-utils-1.0.24-2.el6.x86_64 How reproducible: Need to include "--iscsi portal=x.x.x.x:3260" args to restrict socket binding on multi-homed system. Steps to Reproduce: 1. have a multi-homed system 2. require iscsi to only bind to one NIC 3. fail :-) Actual results: tgtd binds to 0.0.0.0:3260 by default. Expected results: tgtd binds only to a specific IP. Additional info: Adding support is trivial: ***BEGIN PATCH*** --- tgtd 2012-03-20 14:22:28.000000000 -0500 +++ tgtd.local 2013-03-15 16:24:57.298215576 -0500 @@ -31,7 +31,7 @@ [ -x /usr/sbin/$exec ] || exit 5 echo -n $"Starting $prog: " # Note /dev/null redirection to silence rdma not found messages - daemon $exec >/dev/null 2>&1 + daemon $exec ${TGTD_OPTIONS} >/dev/null 2>&1 retval=$? if [ $retval -ne 0 ] ; then failure ***END PATCH*** and since /etc/sysconfig/tgtd does not contain a TGTD_OPTIONS line, default behaviour remains unchanged. The workaround is obvious, but this needs to get into an errata pkg so I'm not customizing initscripts to support a fully-documented feature (see http://stgt.sourceforge.net/manpages/tgtd.8.html). Should be possible to include in errata since default behaviour does not change.