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.
Cause
Bring the FCoE VLAN interface down and then up again.
Consequence
The FCoE interface is not re-enabled after the VLAN interface is brought
up again.
Fix
Enable the interface.
Result
The FCoE interface is enabled after the VLAN interface is brought up.
DescriptionNithin Nayak Sujir
2011-02-26 00:56:17 UTC
Description of problem:
When ifconfig down is performed on a vlan interface fcoe-utils calls
DISABLE on the fcoe port. However, when it comes back up, it does not
call ENABLE since it was an auto created port. It waits for vlan
discovery to complete. But since vlan discovery is disabled for vlan
interfaces, ENABLE never gets called and the link remains down.
How reproducible:
By bringing down and up the vlan interface with bnx2fc driver as fcoe lld
Note: The current fcoe driver registers a device notifier and calls
fcoe_ctlr_link_up on its own. This patch makes ENABLE/DISABLE symmetric
and avoids forcing the llds to register their own notifiers.
Steps to Reproduce:
1. ifconfig eth4.<vlan>-fcoe down
2. ifconfig eth4.<vlan>-fcoe up
3. fcoeadm -i
Actual results:
State will show LinkDown
Expected results:
State should be Online
Additional info:
can't be reproduced with fcoe driver because it does link up on its own.
Patch for the Fix pending review at open-fcoe.org:
http://www.open-fcoe.org/patchwork/patch/1687/
Hi Nithin, QE does not have a proper test environment to verify this bug and would like to ask for your commitment to help with testing this bug before scheduling the fix for a next minor update. Thanks
~~ 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 12Miroslav Vadkerti
2011-04-06 11:22:20 UTC
Doing SanityOnly testing:
* Latest release of RHEL6.1 contains fcoe-utils-1.0.17-7.el6
* All available RHTS tests PASS:
/CoreOS/fcoe-utils/Regression/bz503165-running-fcoeadm-before-loading-fcoe-stack-tracebacks
/CoreOS/fcoe-utils/Regression/bz619604-fcoe-utils-enabled-in-2345-by-default
/CoreOS/fcoe-utils/Sanity/init-scripts-LSB
/CoreOS/fcoe-utils/Sanity/long-form-options
* rebuilding src.rpm without issues on all archs with the latest RHEL6.1
packages:
kernel-2.6.32-128.el6.x86_64
lldpad-0.9.41-3.el6.x86_64
The patch is applied:
+ echo 'Patch #15 (fcoe-utils-1.0.17-auto-enable.patch):'
Patch #15 (fcoe-utils-1.0.17-auto-enable.patch):
+ /bin/cat /root/rpmbuild/SOURCES/fcoe-utils-1.0.17-auto-enable.patch
+ /usr/bin/patch -s -p1 -b --suffix .auto-enable --fuzz=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.
New Contents:
Cause
Bring the FCoE VLAN interface down and then up again.
Consequence
The FCoE interface is not re-enabled after the VLAN interface is brought
up again.
Fix
Enable the interface.
Result
The FCoE interface is enabled after the VLAN interface is brought up.
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-0743.html
Description of problem: When ifconfig down is performed on a vlan interface fcoe-utils calls DISABLE on the fcoe port. However, when it comes back up, it does not call ENABLE since it was an auto created port. It waits for vlan discovery to complete. But since vlan discovery is disabled for vlan interfaces, ENABLE never gets called and the link remains down. How reproducible: By bringing down and up the vlan interface with bnx2fc driver as fcoe lld Note: The current fcoe driver registers a device notifier and calls fcoe_ctlr_link_up on its own. This patch makes ENABLE/DISABLE symmetric and avoids forcing the llds to register their own notifiers. Steps to Reproduce: 1. ifconfig eth4.<vlan>-fcoe down 2. ifconfig eth4.<vlan>-fcoe up 3. fcoeadm -i Actual results: State will show LinkDown Expected results: State should be Online Additional info: can't be reproduced with fcoe driver because it does link up on its own. Patch for the Fix pending review at open-fcoe.org: http://www.open-fcoe.org/patchwork/patch/1687/