-
Bug
-
Resolution: Done-Errata
-
Major
-
2.6.2
-
False
-
None
-
True
-
-
-
Moderate
The plan is failing with error below after creating a migration plan from UI with source as another OpenShift Virtualization cluster:
The plan is not ready - VMNetworksNotMapped VM has unmapped networks.. To troubleshoot, check the Forklift controller pod logs.
The selected VM have bridge network attached to it:
networks:
- name: default
pod: {}
- multus:
networkName: bridgenet
name: nic-financial-pelican
Forklift controller logs:
{"level":"error","ts":"2024-06-14 15:10:51.981","logger":"validator|ocp","msg":"Multus network not found.","plan":"openshift-mtv/rhel8-general-flamingo"
It looks like the networkmap for bridge is not correctly populated and only have ID:
spec:
map:
- destination:
type: pod
source:
type: pod
- destination:
name: br2-nad
namespace: default
type: multus
source:
id: 5340fbc7-490c-423b-8956-74bf239168f2 <===
After manually adding name and type to the networkmap as below, the plan moves into "Ready" :
source: id: 5340fbc7-490c-423b-8956-74bf239168f2 name: clusters-external/bridgenet type: multus
Version-Release number of selected component (if applicable):
Migration Toolkit for Virtualization Operator 2.6.2
OpenShift Virtualization 4.14.6
How reproducible:
100 %
Steps to Reproduce:
1. Create a plan from UI, select another OpenShift Virtualization as source provider and select a VM that have a bridge network. 2. Plan will be in error state with message "The plan is not ready - VMNetworksNotMapped"
Actual results:
VMNetworksNotMapped error after creating plan with OpenShift Virtualization source provider
Expected results:
Additional info:
- is duplicated by
-
-
- Closed
-
- links to
-
RHBA-2024:139514
MTV 2.7.2 Images 4.14-4.16
