Bug 1629444 - unable to create fcoe instance on the second NIC(bnx2x)
Summary: unable to create fcoe instance on the second NIC(bnx2x)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fcoe-utils
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Leech
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-16 11:43 UTC by lnie
Modified: 2019-11-27 19:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:27:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal (146.76 KB, text/plain)
2018-09-16 11:43 UTC, lnie
no flags Details

Description lnie 2018-09-16 11:43:33 UTC
Created attachment 1483686 [details]
journal

Description of problem:
[root@storageqe-16 ~]# ifconfig ens2f1 up
[root@storageqe-16 ~]# /bin/cp -f /etc/fcoe/cfg-ethx /etc/fcoe/cfg-ens2f1
[root@storageqe-16 ~]# vi /etc/fcoe/cfg-ens2f1 
[root@storageqe-16 ~]# vi /etc/fcoe/cfg-ens2f1 
[root@storageqe-16 ~]# vi /etc/fcoe/cfg-ens2f1 
[root@storageqe-16 ~]# vi /etc/sysconfig/network-scripts/ifcfg-ens2f1
[root@storageqe-16 ~]# service lldpad restart
Redirecting to /bin/systemctl restart lldpad.service
[root@storageqe-16 ~]# service fcoe restart
Redirecting to /bin/systemctl restart fcoe.service
[root@storageqe-16 ~]# chkconfig lldpad on
Note: Forwarding request to 'systemctl enable lldpad.service'.
Created symlink /etc/systemd/system/multi-user.target.wants/lldpad.service → /usr/lib/systemd/system/lldpad.service.
Created symlink /etc/systemd/system/sockets.target.wants/lldpad.socket → /usr/lib/systemd/system/lldpad.socket.
[root@storageqe-16 ~]# chkconfig fcoe on
Note: Forwarding request to 'systemctl enable fcoe.service'.
Created symlink /etc/systemd/system/multi-user.target.wants/fcoe.service → /usr/lib/systemd/system/fcoe.service.
[root@storageqe-16 ~]# 
[root@storageqe-16 ~]# fcoeadm -i
    Description:      NetXtreme II BCM57810 10 Gigabit Ethernet
    Revision:         10
    Manufacturer:     Broadcom Inc. and subsidiaries
    Serial Number:    001018AD40C0

    Driver:           bnx2x 1.712.30-0
    Number of Ports:  1

        Symbolic Name:     bnx2fc (QLogic BCM57810) v2.11.8 over ens2f1.802-fcoe
        OS Device Name:    host1
        Node Name:         0x2000001018ad40c3
        Port Name:         0x2001001018ad40c3
        Fabric Name:        0x2322000573b27f01
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048 bytes
        FC-ID (Port ID):   0x7500a1
        State:             Online
[root@storageqe-16 ~]# ifconfig ens2f0 up
[root@storageqe-16 ~]# /bin/cp -f /etc/fcoe/cfg-ethx /etc/fcoe/cfg-ens2f0
[root@storageqe-16 ~]# vi /etc/fcoe/cfg-ens2f0
[root@storageqe-16 ~]# service lldpad restart
Redirecting to /bin/systemctl restart lldpad.service
[root@storageqe-16 ~]# service fcoe restart
Redirecting to /bin/systemctl restart fcoe.service
[root@storageqe-16 ~]# chkconfig lldpad on
Note: Forwarding request to 'systemctl enable lldpad.service'.
[root@storageqe-16 ~]# chkconfig fcoe on
Note: Forwarding request to 'systemctl enable fcoe.service'.
[root@storageqe-16 ~]# fcoeadm -i
    Description:      NetXtreme II BCM57810 10 Gigabit Ethernet
    Revision:         10
    Manufacturer:     Broadcom Inc. and subsidiaries
    Serial Number:    001018AD40C0

    Driver:           bnx2x 1.712.30-0
    Number of Ports:  1

        Symbolic Name:     bnx2fc (QLogic BCM57810) v2.11.8 over ens2f1.802-fcoe
        OS Device Name:    host1
        Node Name:         0x2000001018ad40c3
        Port Name:         0x2001001018ad40c3
        Fabric Name:        0x2322000573b27f01
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048 bytes
        FC-ID (Port ID):   0x7500a1
        State:             Online



If you create fcoe instance on ens2f0 first,you won't be able to create fcoe instance on ens2f1 then.

Version-Release number of selected component (if applicable):
kernel-4.18.5-300.fc29.x86_64
fcoe-utils-1.0.32-6.fc29.x86_64


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ben Cotton 2019-10-31 20:42:12 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-11-27 19:27:46 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.