-
Bug
-
Resolution: Done
-
Major
-
2.9.0
Description of problem:
migration OVA plan for a VM that has two network cards (NICs). The issue is, both of these source NICs are incorrectly mapped to the same pod network, yet the plan still shows a "ready" status, even though this misconfiguration isn't reflected in the YAML.
Version-Release number of selected component (if applicable):
OCP: 4.19 CNV: 4.19 MTV: 2.9.0 - on-pr-76657e65fa4e6ff445965976200aed1ad7adbb7d
How reproducible:
Always
Steps to Reproduce:
1. Create OVA provider connected to NFS server 2. Create a Plan from OVA files with 2 NICs 3. Select both of the NICs to "Pod" target Network
Actual results:
1. YAML doesn't show anything as critical 2. Plan Is ready
Expected results:
1. YAML showing the critical warning 2. Plan is not ready and pointing to Network to fix
Additional info: