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
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.
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>