Bug 1735676

Summary:	[Neutron] - VF link-state needs to be set to Auto
Product:	Red Hat OpenStack	Reporter:	Rodolfo Alonso <ralonsoh>
Component:	openstack-neutron	Assignee:	Rodolfo Alonso <ralonsoh>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	high	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	amuller, ccamposr, chrisw, coldford, cory.bannister, cylopez, djuran, ekuris, igallagh, jlibosva, jniu, jzaher, kfryklun, majopela, mmethot, njohnston, pliu, ralonsoh, scohen, srevivo, tfreger, vcojot, weiyongjun
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-neutron-9.4.1-48.el7ost	Doc Type:	Release Note
Doc Text:	The Neutron SR-IOV agent sets two link states for the virtual functions (VFs): - "auto": The physical function (PF) link state ("up" or "down") is replicated when the VF is enabled. - "disable": The VF is disabled and does not transmit. The default VF link state is now "auto". Therefore when the PF is "down" the VF will not transmit or receive, even with other VFs in the same embedded switch (NIC). Note: This is not standard behavior. The standard behavior depends on the NIC vendor implementation. Therefore you must check the driver manual for the behavior of a VF in "auto" state when the PF is "down".	Story Points:	---
Clone Of:	1656978
Clones:	1905791 (view as bug list)		Environment:
Last Closed:	2019-10-16 09:41:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1476160, 1656978
Bug Blocks:	1476900, 1500557, 1734490, 1905791

Comment 15 errata-xmlrpc 2019-10-16 09:41:17 UTC

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://access.redhat.com/errata/RHBA-2019:3115