Bug 1385416 - SRIOV Nic Agent Not Installed In Overcloud Image
Summary: SRIOV Nic Agent Not Installed In Overcloud Image
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director-images
Version: 9.0 (Mitaka)
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 00:38 UTC by Benjamin Schmaus
Modified: 2019-12-16 07:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-21 12:52:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Benjamin Schmaus 2016-10-17 00:38:28 UTC 
Description of problem:

According to the upstream openstack documentation: http://docs.openstack.org/draft/networking-guide/config-sriov.html 

"You must include the SR-IOV agent on each compute node using SR-IOV ports."

In the current OSP Director Images (rhosp-director-images-9.0-20160818.1.el7ost.noarch) the openstack-neutron-sriov-nic-agent package is missing in the overcloud image.

Should this not be included given our support for SRIOV?

Current customers need to use virt-customize or install package after the deployment.


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

How reproducible:
100%

Steps to Reproduce:
1.Deploy Director Overcloud w/ SRIOV support
2.
3.

Actual results:
SRIOV Agent package missing

Expected results:
SRIOV Agent package should be in the image without needing to add it via virt-customize or after the fact with yum install.

Additional info:
Comment 2 Sven Anderson 2016-10-21 12:52:17 UTC 
SRIOV is not included in tripleo mitaka, and therefore not supported in OSP9 director.
Comment 3 awaugama 2017-08-30 17:56:37 UTC 
WONTFIX/NOTABUG therefore QE Won't automate
Note You need to log in before you can comment on or make changes to this bug.