Major Description : If VM uses NSX-T N-VDS , then the networks are not listed in Networkmap in MTV
- NSX-T is a VMWares SDN, similar to openvswitch
- Openshift-MTV will only provide the inventory of the hypervisors
- When creating a migration plan and mapping the networks, it will only display networks from the hypervisor.
- If the VM only has networks connected to NSX-T, when mapping the network it will not show any network available
Affected products : MTV 2.6
Expected results : NSX-T networks from the VMs should shown under the NetworkMapping of MTV
- causes
-
MTV-1667 (QE) Efforts related to NSX / MTV testing
-
- Closed
-
- is caused by
-
MTV-1695 Missing VM network-ID in the inventory.
-
- Closed
-
- links to
-
RHBA-2024:143338
MTV 2.7.5 Images
[MTV-1140] Networks managed by NSX-T (from VMWare VMs) are not listed in Network mapping of MTV
After a call with the customer, we were able to find that the issue was about the missing OpaqueNetwork support in the MTV Inventory.
We have opened a ticket about that issue in case there would be additional issues related to the NSXT support.
I have provided the customer with a custom upstream build so we could verify that the issue was solved quay.io/mnecas0/forklift-controller:MTV-1695.
The customer verified that the solution fixed the problem.
Hi,
me and omachace@redhat.com have tested the MTV with NSXT and we were able to get see the network managed by NSXT in the MTV network mappings, please take a look at the screenshots.
Please check with customers if they have applied the permissions correctly.
Mainly check if they added the permissions on proper objects ie networks, datastores, hosts that are related to the VMs.
Additionally, the customers user account needs to have permissions specified in https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/2.7/ht[…]ling_and_using_the_migration_toolkit_for_virtualization/index
We mainly focused on mapping and seeing the networks to which the VMs are attached to.
If some customer has a specific issue with the NSXT network please let us know.
Hello fdeutsch@redhat.com ,
> This is about displaying NSX-T networks as a source, in order to then map them to NetworkAttachmentDefinitions (NADs) on the OCP side. Is this correct?
The mentioned is correct, the NSX-T network is not listed in networks as a source, in order to map with NAD on OCP Side.
According to our informations this used to work with earlier MTV versions such as 2.6.z. Is somebody able to confirm this?
Also: This is about displaying NSX-T networks as a source, in order to then map them to NetworkAttachmentDefinitions (NADs) on the OCP side. Is this correct?
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (MTV 2.7.5 Images), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:10679