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:
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.

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.

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/

    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.

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