Bug 1468290

Summary: Pike sriov passing wrong argument for the passthrough whitelist
Product: Red Hat OpenStack Reporter: Maxim Babushkin <mbabushk>
Component: puppet-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: awaugama
Severity: high Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: aschultz, awaugama, edannon, fbaudin, jjoyce, jschluet, ksundara, mbooth, mburns, oblaut, rhel-osp-director-maint, sgordon, slinaber, tvignaud, yrachman
Target Milestone: Upstream M3Keywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-nova-11.2.0-0.20170714191600.ff92413.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:39:17 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:

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

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

https://access.redhat.com/errata/RHEA-2017:3462