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.
Bug 668114 - fcoe fails to login with Cisco Eaglehawk switch firmware on VFC shut/no shut
Summary: fcoe fails to login with Cisco Eaglehawk switch firmware on VFC shut/no shut
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 6.1
Assignee: Mike Christie
QA Contact: Storage QE
URL:
Whiteboard:
Depends On: 663561 674707
Blocks: 677180 683814
TreeView+ depends on / blocked
 
Reported: 2011-01-07 22:40 UTC by Vasu Dev
Modified: 2011-05-19 12:21 UTC (History)
18 users (show)

Fixed In Version: kernel-2.6.32-120.el6
Doc Type: Bug Fix
Doc Text:
Operating in the FIP (FCoE Initialization Protocol) mode and performing operations that bring up ports could cause the fcoe.ko and fnic.ko modules to not be able to re-login when a port was brought back up. This was due to a bug in the FCoE (Fiber Channel over Ethernet) layer causing improper handling of FCoE LOGO frames while in the FIP mode. With this update, FCoE LOGO frames are properly handled when in the FIP mode and the fcoe.ko and fnic.ko modules no longer fail to re-login.
Clone Of:
Environment:
Last Closed: 2011-05-19 12:21:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0542 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update 2011-05-19 11:58:07 UTC

Description Vasu Dev 2011-01-07 22:40:41 UTC 
Fix is implemented by not allowing FCoE LOGO in FIP mode, EMC will also use
test case to ensure FCoE LOGO does't log out fcoe port. 

Fix is out at https://lists.open-fcoe.org/pipermail/devel/2011-January/010909.html and this depends on patches from Bug #663561 .

This fix also needs to picked by RHEL 6.0
Comment 2 RHEL Program Management 2011-01-08 04:30:47 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 3 Barry Donahue 2011-01-19 16:35:35 UTC 
Is Intel going to be able to verify this fix in 6.1?
Comment 4 Jack Morgan 2011-01-19 18:12:47 UTC 
Yes, In fact we already verified this fix prior to pushing the patches and will verify the RPM once available.
Comment 5 Robert Love 2011-02-03 00:12:11 UTC 
Patch mailed to linux-scsi on 01/28/11.
Comment 6 Mike Christie 2011-02-14 20:12:17 UTC 
Just to sync everyone up. I was going to sent the fix in the initial comment from Vasu and the other ones I sent you last week in this bz.


Rob/Intel us know when you are done testing and we will send internally. Thanks.
Comment 7 Russell Doty 2011-02-21 16:27:29 UTC 
Comment 19 indicates that Intel will verify the patch once a test RPM is available. Has this test RPM been provided?
Comment 8 Robert Love 2011-02-23 00:55:43 UTC 
I only see 7 comments, so comment 19 must be private. We're testing a kernel RPM that Mike has provided to us that should contain this patch.
Comment 9 Russell Doty 2011-02-23 16:13:42 UTC 
Since we are trying to address a critical subset of FCoE bugs in a 5.6.z Z-stream release, we need to get these bugs moved to modified or on_qa as soon as possible.

This bug looks like it is in good shape as part of a larger set of 6.1 work. Can we get this bug promoted to modified (and then on_qa) so that we can start the z-stream request process?
Comment 10 Jack Morgan 2011-02-25 21:13:08 UTC 
Verified by Intel. Thanks
Comment 11 Robert Love 2011-03-04 19:07:09 UTC 
I was asked to indicate which patch is needed for this BZ. The patch that fixes this issue is linked to in the first comment, the "description". Here it is again: https://lists.open-fcoe.org/pipermail/devel/2011-January/010909.html
Comment 14 Aristeu Rozanski 2011-03-08 21:59:20 UTC 
Patch(es) available on kernel-2.6.32-120.el6
Comment 19 Chris Ward 2011-04-06 11:16:15 UTC 
~~ Partners and Customers ~~

This bug was included in RHEL 6.1 Beta. Please confirm the status of this request as soon as possible.

If you're having problems accessing 6.1 bits, are delayed in your test execution or find in testing that the request was not addressed adequately, please let us know.

Thanks!
Comment 20 Martin Prpič 2011-04-12 12:46:21 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:
Operating in the FIP (FCoE Initialization Protocol) mode and performing operations that bring up ports could cause the fcoe.ko and fnic.ko modules to not be able to re-login when a port was brought back up. This was due to a bug in the FCoE (Fiber Channel over Ethernet) layer causing improper handling of FCoE LOGO frames while in the FIP mode. With this update, FCoE LOGO frames are properly handled when in the FIP mode and the fcoe.ko and fnic.ko modules no longer fail to re-login.
Comment 21 Jack Morgan 2011-04-13 19:40:47 UTC 
Updating Verified field
Comment 22 errata-xmlrpc 2011-05-19 12:21:32 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/RHSA-2011-0542.html
Note You need to log in before you can comment on or make changes to this bug.