-
Sub-task
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
None
-
Description of problem:
Customer makes a network change to a VM and in the web ui it states that changes will take affect after a live migration of the VM. The customer live migrates the VM, but the changes do not take affect. They only take affect if the VM is shut down and restarted.
Version-Release number of selected component (if applicable):
OCP 4.17.16 CNV 4.17.5
How reproducible:
Originally the VM has: ~~~ - multus: networkName: default/br1-vlan192-default name: default ~~~ Modify the VM to switch the network to default/br1-vlan128-default Post migration the VM config has: ~~~ - multus: networkName: default/br1-vlan128-default name: default ~~~ However the VM is still on the original multus network: ~~~ k8s.v1.cni.cncf.io/network-status: |- [{ "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "192.168.15.106" ], "mac": "0a:58:c0:a8:0f:6a", "default": true, "dns": {} },{ "name": "default/br1-vlan192-default", <--- original network, not vlan128-default "interface": "pod37a8eec1ce1", "mac": "02:e1:ad:00:00:2c", "dns": {} }] ~~~
Expected results:
The VM is on the new network post migration.