Bug 1850425

Summary:	[v2v][VM import RHV to CNV] Add validation for network target type in network mapping
Product:	Container Native Virtualization (CNV)	Reporter:	Ilanit Stein <istein>
Component:	V2V	Assignee:	Jakub Dzon <jdzon>
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.4.0	CC:	cnv-qe-bugs, pkliczew, pvauter, ysegev
Target Milestone:	---
Target Release:	2.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v2.4.0-17	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-28 19:10:39 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 Ilanit Stein 2020-06-24 10:01:31 UTC

Description of problem:
In the VM import resource mapping, there is no validation to the target network type.
The types should be restricted to the supported ones:
multus and pod.

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

Comment 1 Ilanit Stein 2020-07-08 19:33:35 UTC

Verified on CNV-2.4 from July 07 2020.

VM import resource yaml with target network type incorrect indentation, and invalid value (not pod/multus) is resulted with VM import to target network pod

Comment 4 errata-xmlrpc 2020-07-28 19:10:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:3194