-
Bug
-
Resolution: Done-Errata
-
Undefined
-
2.5.2
-
None
Description of problem:
A plan is created with the transfer network:
# oc get plan -n openshift-mtv -o yaml |grep -i -A 1 transferNetwork transferNetwork: name: macvlan-net
The virt-v2v pod is not using this network and is using the default pod network:
oc get pod myplan-vm-43263-htxnx -o json |jq '.metadata.annotations' { "k8s.ovn.org/pod-networks": "{\"default\":{\"ip_addresses\":[\"10.131.1.30/23\"],\"mac_address\":\"0a:58:0a:83:01:1e\",\"gateway_ips\":[\"10.131.0.1\"],\"routes\":[{\"dest\":\"10.128.0.0/14\",\"nextHop\":\"10.131.0.1\"},{\"dest\":\"172.30.0.0/16\",\"nextHop\":\"10.131.0.1\"},{\"dest\":\"100.64.0.0/16\",\"nextHop\":\"10.131.0.1\"}],\"ip_address\":\"10.131.1.30/23\",\"gateway_ip\":\"10.131.0.1\"}}", "k8s.v1.cni.cncf.io/network-status": "[{\n \"name\": \"ovn-kubernetes\",\n \"interface\": \"eth0\",\n \"ips\": [\n \"10.131.1.30\"\n ],\n \"mac\": \"0a:58:0a:83:01:1e\",\n \"default\": true,\n \"dns\": {}\n}]", "openshift.io/scc": "forklift-controller-scc", "seccomp.security.alpha.kubernetes.io/pod": "runtime/default" }
So the transfer happens over the pod network and not through the transfer network.
Version-Release number of selected component (if applicable):
Migration Toolkit for Virtualization Operator 2.5.2
How reproducible:
100%
Steps to Reproduce:
1. While creating the plan, select another network for migration.
2. Check the conversion pod definition. The transfer network is not being used by the conversion pod.
- clones
-
MTV-835 Transfer network is not used by the conversion pod
- Closed
- links to
-
RHBA-2023:125016 MTV 2.5.4 Images
- mentioned on