Description of problem:
The NetworkMap does not get updated in the following cases:
- When creating a NetworkAttachmentDefinition (NAD) for a second network after the NetworkMap already exists --> NetworkMap stays on "NotReady" state, message: "Destination network not found"
- When the NetworkMap is ready and you delete the NAD which is in use --> NetworkMap stays in "Ready" state
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Via API, create a NetworkMap CR that includes mapping to a second network (multus) --> NetworkMap is on "NotReady" state due to "Destination network not found"
2. Create a NetworkAttachmentDefinition CR for the second network
NetworkMap stays on "NotReady" state
NetworkMap moves to "Ready" state
Would you please document that the NetworkAttachmentDefinition CR creation for the second network, is a required step,
BEFORE creating the network mapping, for the Migration, due to this bug?
Moving this bug back to a software bug, and cloning a doc bug instead.
Regarding to this documentation page: https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.0/html-single/installing_and_using_the_migration_toolkit_for_virtualization/index?lb_target=stage
The "MTV custom resources" list contains also NetworkMapping and StorageMapping
But indeed in this section: "3.3. Migrating virtual machines from the command line interface" - there are no examples on how to create those CRs, and the example for Plan is an old solution where the mappings were internal
I will file a new Documentation BZs to update this section with NetworkMapping, StorageMapping and Plan CRs creation examples
(In reply to Maayan Hadasi from comment #5)
> Hi @firstname.lastname@example.org,
> I will file new Documentation BZs to update this section with
> NetworkMapping, StorageMapping and Plan CRs creation examples
Bug 1971324 - [DOC][MTV][API] Add custom resource creation example for NetworkMap and StorageMap
Bug 1971326 - [DOC][MTV][API] Update custom resource creation example for Plan CR
@email@example.com, do we need to add a watch for the NetworkAttachDefinition CRs?
1. Delete the network mapping
2. Create the NAD
3. Recreate the network mapping
Fixed March 29, 2021: https://github.com/konveyor/forklift-controller/commit/46f0fb4c035e8f9fa6e6ecdc2cf8b6910f9e5736
Found/Fixed the items listed on DestinationNetworkNotFound conditions. No need to file a bug.
The issue is reproducible using mtv-operator-bundle-container-2.1.0-21
Please verify with build 2.1.0-29 / IIB:90663.
Verified as fixed.
MTV 2.1.0-44 iib 96817
CNV 4.8.1-17 iib 97584
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Migration Toolkit for Virtualization 2.1.0), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.