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:
The fcoeadm tool was not properly sending VN2VN create requests to fcoemon.
Consequence:
Requested VN2VN mode FCoE interfaces would actually be created as fabric mode.
Fix:
fcoeadm was fixed to pass the proper command to fcoemon
Result:
VN2VN interface creation with fcoeadm works as expected
retry with SELinux disabled. and still get the same issue. It seems like the option "-m vn2vn" does not work. it always use the Fabric mode to create the FCoE instance.
[root@hp-dl388g8-23 ~]# setenforce 0
[root@hp-dl388g8-23 ~]# fcoeadm -m vn2vn -c p2p1
[root@hp-dl388g8-23 ~]# fcoeadm -i
Description: 82599EB 10-Gigabit SFI/SFP+ Network Connection
Revision: 01
Manufacturer: Intel Corporation
Serial Number: 90E2BA5661D8
Driver: ixgbe 3.15.1-k
Number of Ports: 1
Symbolic Name: fcoe v0.1 over p2p1
OS Device Name: host3
Node Name: 0x100090E2BA5661DA
Port Name: 0x200090E2BA5661DA
FabricName: 0x0000000000000000
Speed: Unknown
Supported Speed: 1 Gbit, 10 Gbit
MaxFrameSize: 2112
FC-ID (Port ID): 0xFFFFFFFF
State: Linkdown
[root@hp-dl388g8-23 ~]# cat /sys/bus/fcoe/devices/ctlr_0/mode
Fabric
(In reply to Xiaowei Li from comment #7)
> set it to blocker since vn2vn is the rhel 7.0 fcoe feature. we should
> support it via the fcoeadm.
As there is a workaround, I don't believe this meets the blocker criteria.
(In reply to Petr Šabata from comment #9)
> (In reply to Xiaowei Li from comment #7)
> > set it to blocker since vn2vn is the rhel 7.0 fcoe feature. we should
> > support it via the fcoeadm.
>
> As there is a workaround, I don't believe this meets the blocker criteria.
okay for me to remove the blocker keyword. but let's keep the urgent priority so that we can fix it asap.
(In reply to Xiaowei Li from comment #10)
> (In reply to Petr Šabata from comment #9)
> > (In reply to Xiaowei Li from comment #7)
> > > set it to blocker since vn2vn is the rhel 7.0 fcoe feature. we should
> > > support it via the fcoeadm.
> >
> > As there is a workaround, I don't believe this meets the blocker criteria.
>
> okay for me to remove the blocker keyword. but let's keep the urgent
> priority so that we can fix it asap.
also if cannot fix it in 7.0 we should document this known issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2015-0560.html
Description of problem: Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. # fcoeadm -c p2p2 -m vn2vn fcoeadm: Internal error Try 'fcoeadm --help' for more information. # echo $? 6 this is another issue. don't care it. # fcoeadm -i Description: 82599EB 10-Gigabit SFI/SFP+ Network Connection Revision: 01 Manufacturer: Intel Corporation Serial Number: 90E2BA5663D8 Driver: ixgbe 3.15.1-k Number of Ports: 1 Symbolic Name: fcoe v0.1 over p2p2 OS Device Name: host5 Node Name: 0x100090E2BA5663DB Port Name: 0x200090E2BA5663DB FabricName: 0x0000000000000000 Speed: 10 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 2112 FC-ID (Port ID): 0xFFFFFFFF State: Offline 2. cat /sys/bus/fcoe/devices/ctlr_1/mode Fabric 3. Actual results: the port state is offline and the mode is Fabric. Expected results: the port state is online and the mode is vn2vn Additional info: workaround: echo vn2vn > /sys/bus/fcoe/devices/ctlr_1/mode #cd /sys/bus/fcoe/devices/ctlr_1/ # cat enabled 1 # cat mode Fabric # echo vn2vn > mode -bash: echo: write error: Device or resource busy # echo 0 > enabled # echo vn2vn > mode # echo 1 > enabled # fcoeadm -i Description: 82599EB 10-Gigabit SFI/SFP+ Network Connection Revision: 01 Manufacturer: Intel Corporation Serial Number: 90E2BA5663D8 Driver: ixgbe 3.15.1-k Number of Ports: 1 Symbolic Name: fcoe v0.1 over p2p2 OS Device Name: host5 Node Name: 0x100090E2BA5663DB Port Name: 0x200090E2BA5663DB FabricName: 0x0000000000000000 Speed: 10 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 2112 FC-ID (Port ID): 0x0063DB State: Online