Bug 1422129

Summary:	Cannot start instances with neutrons multi-provider network
Product:	Red Hat OpenStack	Reporter:	Vladik Romanovsky <vromanso>
Component:	openstack-nova	Assignee:	Vladik Romanovsky <vromanso>
Status:	CLOSED ERRATA	QA Contact:	awaugama
Severity:	high	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	akarlsso, berrange, dasmith, eglynn, fdinitto, jhakimra, jjung, jschluet, kchamart, lyarwood, nyechiel, rnoriega, sbauza, sferdjao, sgordon, srevivo, tvvcox, vromanso
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-14.0.7-9.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1469225 (view as bug list)		Environment:	N/A
Last Closed:	2017-09-06 17:04:57 UTC	Type:	Bug
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:	1469225
Bug Blocks:	1335596, 1396161, 1414428, 1533135, 1533136

Description Vladik Romanovsky 2017-02-14 14:22:23 UTC

Description of problem:
Instances utilizing SR-IOV won't be able to start with a network port that has been created from a multi-provider (multi-segment) network. [1]

Such ports will have a special "segments" field that will hold a list of networks and will fail when we will attempt to retrieve a single network, such as here [2]

[1] https://bugs.launchpad.net/openstack-api-site/+bug/1242019
[2] https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L1417

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nir Yechiel 2017-03-30 09:00:19 UTC

Hi Vladik,

IRRC, there is an upstream patch already proposed. Can you please update this BZ?

Thanks,
Nir

Comment 2 Nir Yechiel 2017-06-08 14:10:39 UTC

Upstream patch is merged.

Comment 13 errata-xmlrpc 2017-09-06 17:04:57 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-2017:2652