Bug 688783 - iscsid will fail to set DCB priority if debug logging is turned off
Summary: iscsid will fail to set DCB priority if debug logging is turned off
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 6.1
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: ---
Assignee: Andy Grover
QA Contact: Barry Donahue
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 00:49 UTC by Mark Rustad
Modified: 2015-09-28 02:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If debug message logging was disabled, the iSCSI daemon failed to set the socket priority according to the Data Center Bridging application priority setting, which resulted in packets being sent with the default priority incorrectly. Socket priority is now set based on the Data Center Bridging application priority setting in this situation.
Clone Of:
Environment:
10g Ethernet with DCB
Last Closed: 2011-05-19 14:14:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0733 0 normal SHIPPED_LIVE iscsi-initiator-utils bug fix and enhancement update 2011-05-19 09:47:49 UTC

Description Mark Rustad 2011-03-18 00:49:20 UTC 
Description of problem:
iscsid will fail to set the socket priority according to the DCB application priority setting if debug message logging is turned off

Version-Release number of selected component (if applicable):
6.2.0.872-17.el6

How reproducible:
It will consistently fail when iscsid's debug logging is turned off.

Steps to Reproduce:
1. Set up a 10g Ethernet environment with DCB including a non-default priority for iSCSI (port 3260).
2. Run the iSCSI initiator with iscsid debug logging disabled against an iSCSI target accessible through a VLAN in the 10g network. The target need not have DCB support to see the problem.
  
Actual results:
The socket priority will not be set by iscsid, so the packets will be sent with the default priority.

Expected results:
The socket priority should have been set according to the DCB app priority for iSCSI (as configured in step 1).

Additional info:
This was found by code inspection. There is a one-line patch to iscsid being tested.
Comment 2 Mark Rustad 2011-03-18 00:58:49 UTC 
One additional note: the priority should be set correctly in the case that the initiator session is bound to the network device. The case that fails is when the session is not bound to a network device.
Comment 4 Mike Christie 2011-04-04 23:06:26 UTC 
Fixed in iscsi-initiator-utils-6.2.0.872-18.el6. You can download here:
http://people.redhat.com/mchristi/iscsi/rhel6.1/iscsi-initiator-utils/
Comment 8 Laura Bailey 2011-05-13 03:02:49 UTC 
    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.
    
    New Contents:
If debug message logging was disabled, the iSCSI daemon failed to set the socket priority according to the Data Center Bridging application priority setting, which resulted in packets being sent with the default priority incorrectly. Socket priority is now set based on the Data Center Bridging application priority setting in this situation.
Comment 9 errata-xmlrpc 2011-05-19 14:14:53 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2011-0733.html
Note You need to log in before you can comment on or make changes to this bug.