Bug 1468290 - Pike sriov passing wrong argument for the passthrough whitelist
Summary: Pike sriov passing wrong argument for the passthrough whitelist
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-nova
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: RHOS Maint
QA Contact: awaugama
Depends On:
TreeView+ depends on / blocked
Reported: 2017-07-06 15:13 UTC by Maxim Babushkin
Modified: 2018-02-05 19:10 UTC (History)
15 users (show)

Fixed In Version: puppet-nova-11.2.0-0.20170714191600.ff92413.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:39:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 481003 0 None MERGED Fix pci config params name as mentioned in nova conf 2020-02-06 17:16:32 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Maxim Babushkin 2017-07-06 15:13:29 UTC
Description of problem:
During the deployment of sriov on Pike, passthrough_whitelist does not passing correctly to nova.conf

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

How reproducible:
Provide the following parameters within the sriov heat templates

    - devname: "p5p1"
      physical_network: "sriov1"
    - devname: "p5p2"
      physical_network: "sriov2"

Actual results:
pci_passthrough_whitelist=[{"devname": "p5p1", "physical_network": "sriov1"}, {"devname": "p5p2", "physical_network": "sriov2"}]

Expected results:
passthrough_whitelist=[{"devname": "p5p1", "physical_network": "sriov1"}, {"devname": "p5p2", "physical_network": "sriov2"}]

Comment 5 errata-xmlrpc 2017-12-13 21:39: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.


Note You need to log in before you can comment on or make changes to this bug.