Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1642313

Summary: Fix NeutronSriovHostConfig path for ODL deployment with SRIOV
Product: Red Hat OpenStack Reporter: Yariv <yrachman>
Component: openstack-tripleo-heat-templatesAssignee: Christophe Fontaine <cfontain>
Status: CLOSED ERRATA QA Contact: Yariv <yrachman>
Severity: high Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: atelang, cfontain, jchhatba, mburns, mkolesni, sclewis, skramaja, vkhitrin
Target Milestone: betaKeywords: Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060879.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:54:09 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 Yariv 2018-10-24 07:39:41 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yariv 2018-10-24 07:42:24 UTC
overcloud deploy is failing for ODL and SRIOV with following ERROR
Could not fetch contents for file:///tmp/tripleoclient-hxfjYU/tripleo-heat-templates/environments/puppet/services/neutron-sriov-host-config.yaml
Removing the current plan files
Uploading new plan files
Plan updated.
Processing templates in the directory /tmp/tripleoclient-hxfjYU/tripleo-heat-templates
pet/services/neutron-sriov-host-config.yaml

Patch is proposed

Comment 6 errata-xmlrpc 2019-01-11 11:54:09 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-2019:0045