| Summary: | ifconfig down and up on vlan interface makes the link fcoe ctlr link remain down | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Nithin Nayak Sujir <nsujir> | ||||
| Component: | fcoe-utils | Assignee: | Petr Šabata <psabata> | ||||
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1 | CC: | ademcho, bprakash, cward, ebenes, echo, mchan, mvadkert, nsujir, rvokal, ttluong | ||||
| Target Milestone: | rc | Keywords: | EasyFix, OtherQA, Patch | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| URL: | http://www.open-fcoe.org/patchwork/patch/1687/ | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | fcoe-utils-1.0.17-6.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
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.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-19 14:20:28 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
This seems reasonable. Requesting devel ack. Created attachment 481401 [details]
Automatically enable FCoE interface after interface restart
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 Adding Broadcom DVT to CC to help verify this. Fixed in CVS tag fcoe-utils-1.0.17-6.el6. ~~ 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! 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 @OtherQA feedback contact person, please update us with the latest available test results confirming the resolution of this request. Thank you. Fix verified by looping ifconfig ethX.<VLAN>-fcoe up/down 100 times, link always becomes online
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/