Bug 1271912

Summary: [SR-IOV] - Edit VMs vNIC - when choosing a 'passthrough' profile, the type should be automatically 'pci-passthrough' type
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Alona Kaplan <alkaplan>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: alkaplan, bugs, danken, myakove, ylavi
Target Milestone: ovirt-3.6.1Flags: rule-engine: ovirt-3.6.z+
ylavi: Triaged+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:22:45 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:
Bug Depends On: 1285696    
Bug Blocks:    

Description Michael Burman 2015-10-15 05:56:21 UTC
Description of problem:
[SR-IOV] - Edit VMs vNIC - when choosing a 'passthrough' profile, the type should be automatically 'pci-passthrough' type.

When editing and updating VMs vNIC profile with a 'passthrough' one, the type remain VirtIO(default), but should change automatically to a 'pci-passthrough' type.

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

How reproducible:
100

Steps to Reproduce:
1. Edit VMs vNIC profile and update to a 'passthrough' profile 
 
Actual results:
vNIC's type remain VirtIO and user need to change it manually to 'pci-passthrough'(if not, operation can't be approved)

Expected results:
vNIC's type should automatically changed to a 'pci-passthrough' type when choosing a 'passthrough' profile.

Comment 1 Yaniv Lavi 2015-10-29 12:44:17 UTC
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.

Comment 2 Michael Burman 2015-12-10 08:56:41 UTC
Verified on - 3.6.1.2-0.1.el6

Comment 3 Sandro Bonazzola 2015-12-16 12:22:45 UTC
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.