Bug 1468625

Summary:	[pci]/alias option is not present in the nova configuration on the computes
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED NOTABUG	QA Contact:	awaugama
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	berrange, dasmith, eglynn, jhakimra, jjoyce, jschluet, kchamart, owalsh, sbauza, sferdjao, sgordon, slinaber, srevivo, tvignaud, vromanso
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	scale_lab, aos-scalability-36
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-21 13:43:36 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 Sai Sindhur Malleni 2017-07-07 14:56:15 UTC

Description of problem:
[pci]/alias option is not being configured by the compute manifest. This option is needed in the nova configuration file on compute nodes starting with Ocata. It is instead being configured by the nova::api class when it should havebeen configured by nova::compute.


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

How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ollie Walsh 2017-07-07 15:04:41 UTC

Assigning to openstack-nova for now until we determine conclusively where the pci passthough conf should be done (compute config vs scheduler config vs both)

Comment 3 Sai Sindhur Malleni 2017-07-17 13:06:48 UTC

Seems like [pci]/alias option is needed on the controllers. On removing [pci]/alias from the controllers, restarting the nova services and trying to launch an instance with the alias in flavor I see PCI alias nvme is not defined (HTTP 400) . However, I have not confirmed if [pci]/alias is needed on the compute nodes.

Link to Error: https://gist.github.com/smalleni/e84c6955675445adf1f750dc7a8eb01a#file-gistfile1-txt-L1

Comment 4 Sahid Ferdjaoui 2017-07-17 13:30:21 UTC

The are two important options related to PCI; passthrought_whitelist and alias.

The passthrought_whitelist is related to the hardwares installed on the compute hosts. There is nothing in relation with the controllers. In the case you find a relation you should open a bug report.

The alias is related to the API, it provides an easy way for users to request hardwares. That option should only be relevant in the controllers.

Comment 5 Ollie Walsh 2017-07-21 13:43:36 UTC

Based on Sahid's comment, which was my expectation after briefly reviewing the code, I'll close this as not a bug. However we should correct the (upstream?) docs the mention setting pci alias on the computes.