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

Bug 1297454

Summary:	[SR-IOV] - REST API - No validation for 'passthrough' profile in DCs less than 3.6
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Alona Kaplan <alkaplan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.2	CC:	bugs, danken, jmcdonal, sbonazzo, ylavi
Target Milestone:	ovirt-3.6.5	Flags:	rule-engine: ovirt-3.6.z+ rule-engine: exception+ ylavi: planning_ack+ danken: devel_ack+ rule-engine: testing_ack+
Target Release:	3.6.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-21 14:42:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Burman 2016-01-11 14:50:26 UTC

Description of problem:
[SR-IOV] - REST API - No validation for 'passthorugh' profile and vNIC type in clusters less then 3.6.

Currently there is no validation in clusters less then 3.6 for 'passthrough' profiles and 'pci-passthrough' vNIC types as should be. 

It is possible to end up with 'passthoruhg' profile in cluster 3.5 in the new 3.6.2 engine. 
The same for vNIC type of 'pci-passthoruhg'.  

Version-Release number of selected component (if applicable):
3.6.2-0.1.el6

How reproducible:
100

Steps to Reproduce:
1. Create vNIC profile with 'passthrough'' enabled in cluster 3.5 in engine 3.6.2 via REST
2. Create vNIC with 'pci-passthoruhg' type in cluster 3.5 in engine 3.6.2 via REST


Actual results:
Possible.

Expected results:
Should be blocked. Should be validation in clusters less then 3.6

Additional info:
See also BZ 1282441

Comment 1 Alona Kaplan 2016-02-11 15:04:10 UTC

It is necessary to fix just the vnic profile add/edit, to block creating 'passthrough' vnics in unsupported DCs.

There is no need to do the same blocking to the add/edit vnic. Since in case the vnics dc doesn't support sriov, it won't contain passthough profile. Therefore, after adding the blocking to the profiles, the user won't be able to create passthough vnic in this dc anyway.

Comment 2 Michael Burman 2016-04-03 11:19:49 UTC

Verified on - 3.6.5-0.1.el6


<fault>
<reason>Operation Failed</reason>
<detail>
[Cannot add VM network interface profile. Passthrough profile is not supported on the selected data center version.]
</detail>
</fault>

<fault>
<reason>Operation Failed</reason>
<detail>
[Cannot edit VM network interface profile. Passthrough profile is not supported on the selected data center version.]
</detail>
</fault>