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

Bug 1579137

Summary: OSP13 sriov VF not created
Product: Red Hat OpenStack Reporter: jianzzha
Component: puppet-neutronAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: amuller, atelang, atheurer, cfontain, jianzzha, jjoyce, jschluet, rnoriega, skramaja, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-11 14:27:22 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:
Attachments:
Description Flags
sriov env
none
deploy shell script none

Description jianzzha 2018-05-17 04:19:31 UTC
Description of problem:
Sriov VF not created when using templates with sriov lines:
  NeutronMechanismDrivers: "openvswitch,sriovnicswitch"
  NovaPCIPassthrough:
    - devname: "p1p1"
      physical_network: "dpdk0"
    - devname: "p1p2"
      physical_network: "dpdk1"

  NeutronSupportedPCIVendorDevs: ['15b3:1018', '8086:154c']
  NeutronPhysicalDevMappings: "dpdk0:p1p1,dpdk1:p1p2"
  NeutronSriovNumVFs: "p1p1:8,p1p2:8"


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


How reproducible:
always

Steps to Reproduce:
1. deploy with the template file which has the sriov config line
2. after deployment, lspci to search for virtual function; or cat /sys/class/net/p1p1/device/sriov_numvfs
3.

Actual results:
cat /sys/class/net/p1p1/device/sriov_numvfs shows 0
lspci didn't show any virtual function

Expected results:
/sys/class/net/p1p1/device/sriov_numvfs should have 8 and lspci should list virtual functions

Comment 1 jianzzha 2018-05-17 04:22:32 UTC
Created attachment 1437738 [details]
sriov env

Comment 2 jianzzha 2018-05-17 04:23:50 UTC
Created attachment 1437739 [details]
deploy shell script

Comment 3 Saravanan KR 2018-05-31 13:06:53 UTC
I believe the patch https://review.openstack.org/#/c/571121/ will fix this issue. Could you confirm?

Comment 4 jianzzha 2018-05-31 13:20:52 UTC
yes it does solve the problem.

Comment 5 Ricardo Noriega 2018-05-31 15:04:30 UTC
Before marking this bz as duplicated with the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1583272

I'd like to know which environment was used to specify the SRIOV configuration. Didn't you use something like this? 

https://github.com/openstack/tripleo-heat-templates/blob/stable/queens/environments/services-docker/neutron-sriov.yaml

This env file specifies the required services in the resource registry.

resource_registry:
  OS::TripleO::Services::NeutronSriovAgent: ../../docker/services/neutron-sriov-agent.yaml
  OS::TripleO::Services::NeutronSriovHostConfig: ../../puppet/services/neutron-sriov-host-config.yaml

Which was the root cause of the issue.

Comment 6 jianzzha 2018-05-31 15:38:45 UTC
I inherited the templates from osp10 when the sriov deploy and I didn't recall to use this neutron-sriov-host-config.yaml on osp10 and it worked. will osp10 also need this templates to deploy sriov now?

Comment 7 jianzzha 2018-06-26 16:40:26 UTC
we can close out this as dulicate. thanks

Comment 8 Christophe Fontaine 2019-02-11 14:27:22 UTC

*** This bug has been marked as a duplicate of bug 1583272 ***