Cannot start instances with multi-provider network

Bug #1676513 reported by Denis Kostryukov on 2017-03-27
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Medium
Sergey Nikitin
9.x
Medium
Sergey Nikitin

Bug Description

Please backport the fix from the bug https://bugs.launchpad.net/nova/+bug/1659467 for MOS 9.x:

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.
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.

MOS 9.2

Denis Kostryukov (dkostryukov) wrote :

sla2 for 9.2-updates

Changed in mos:
importance: Undecided → Medium
tags: added: area-nova
Changed in mos:
assignee: nobody → Sergey Nikitin (snikitin)
status: New → Confirmed
milestone: 9.x-updates → 9.2-mu-2

Fix proposed to branch: 9.0/mitaka
Change author: Vladik Romanovsky <email address hidden>
Review: https://review.fuel-infra.org/32610

Fix proposed to branch: 10.0/newton
Change author: Vladik Romanovsky <email address hidden>
Review: https://review.fuel-infra.org/32614

Reviewed: https://review.fuel-infra.org/32610
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: 4ebe2fcd663e46c1cc584afd9bb015bf51f0fc37
Author: Vladik Romanovsky <email address hidden>
Date: Tue Apr 4 07:53:10 2017

neutron: retrieve physical network name from a multi-provider network

Multi-provider networks are a combination of vxlan and vlan networks.
such a network has a special "segments" field that holds a list
of networks. Each element of this list has the same structure as the 'provider
network attributes'.
These attributes are:
- provider:network_type
- provider:physical_network
- provider:segmentation_id

This patch will retrieve the relevant physical network name from a
multi-provider network

Change-Id: Icb9a546e6fcbf399fcef3e9ea686b35ec3817cd5
Closes-Bug: #1676513
(cherry picked from commit 5ae4f943d3d6b873210acbf2827d20d40b934164)

Dmitry (dtsapikov) wrote :

Verified on 9.2+MU2

tags: added: on-verification
tags: removed: on-verification

Fix proposed to branch: mcp/1.0/mitaka
Change author: Vladik Romanovsky <email address hidden>
Review: https://review.fuel-infra.org/36361

Change abandoned by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36361

Change restored by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36361

Reviewed: https://review.fuel-infra.org/36361
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/1.0/mitaka

Commit: 24110bd689bbdc4a28d9450a317051a9962bdd2a
Author: Vladik Romanovsky <email address hidden>
Date: Thu Aug 31 17:38:34 2017

neutron: retrieve physical network name from a multi-provider network

Multi-provider networks are a combination of vxlan and vlan networks.
such a network has a special "segments" field that holds a list
of networks. Each element of this list has the same structure as the 'provider
network attributes'.
These attributes are:
- provider:network_type
- provider:physical_network
- provider:segmentation_id

This patch will retrieve the relevant physical network name from a
multi-provider network

PROD ticket: https://mirantis.jira.com/browse/PROD-14344

Change-Id: Icb9a546e6fcbf399fcef3e9ea686b35ec3817cd5
Closes-Bug: #1676513
(cherry picked from commit 5ae4f943d3d6b873210acbf2827d20d40b934164)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers