-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
After migrating VMs from VMware vSphere to OpenShift Virtualization (OCP-Virt) using MTV 2.9.4, the OpenShift Console fails to display the IPv4 addresses for the migrated VMs' network interfaces. While the VMs remain reachable via IPv4, this display issue hinders management. The problem is resolved by performing a live migration of the VM to another OCP-Virt node.
Version-Release number of selected component (if applicable):
OCP Cluster version is 4.18.21 Migration Toolkit for Virtualization (MTV): 2.9.4
How reproducible:
Consistently. The issue occurs across all affected VMs migrated in this manner.
Steps to Reproduce:
1. Configure and execute a migration plan using MTV 2.9.4 to migrate RHEL 8 and 9 VMs from VMware vSphere to an OpenShift Virtualization cluster. 2. Ensure the source VMs have at least two network interfaces, each with both IPv4 and IPv6 addresses. 3. After the migration is complete, log in to the OpenShift Console and navigate to the migrated VM's network interface details.
Actual results:
The OpenShift Console displays only the IPv6 address for one of the two network interfaces. The functional IPv4 address for that interface is not visible in the console.
Expected results:
The OpenShift Console should display both the IPv4 and IPv6 addresses for all network interfaces on the migrated VM.
Additional info:
1. A temporary workaround is to perform a live migration of the problematic VM from its current node to another OCP-Virt node. This action forces the console to correctly display all IP addresses. 2. Must-Gather and MTV NS inspect has been collected. Customer will provide sos-report from affected node while the VM is in this condition and sos-report after remedied