Bug 808212

Summary:	vport_create fails with operation not supported
Product:	[Fedora] Fedora	Reporter:	neochi808
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-14 14:51:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description neochi808 2012-03-29 20:12:24 UTC

Description of problem:
Cannot assign/create any NPIV virtual ports on 2nd HBA port.
Performing the identical operation on 1st HBA port 100% successful.


Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. cd /sys/class/fc_host/host5
2. echo '1122334455667788:1122334455667788' > vport_create

  
Actual results:
bash: echo: write error: Operation not supported

Dmesg output: FC Virtual Port LLDD Create failed


Expected results:
A new vport / scsi host adapter should be created.


Additional info:
QLogic QME2572 PCI-Express Dual Channel 8GB HBA


Please note: This also fails on RHEL62 on same hardware

Comment 1 Dave Jones 2012-10-23 15:29:56 UTC

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 2 Justin M. Forbes 2012-11-14 14:51:38 UTC

With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.