Description of problem: The 'namespace' should be mandatory for a Network Attach Definition resource while creating NetworkMap CR Steps to Reproduce: 1. Create a NetworkAttachDefinition with a unique name among all namespaces 2. Create NetworkMap CR with the NAD as destination network, including only type:multus and name:<nad_name> For example: map: - destination: type: multus name: <networkattachmentdefinition_name> source: id: <source_network_mor> Expected results: NetworkMap should be invalid with reason: NotFound until the NAD's namespace will be added.
@fdupont @jortel Should this issue move to ON_QA since the fix is a part of Bug 1971259? https://github.com/konveyor/forklift-controller/pull/306
Yes, this should have been ON_QA. Could you please verify it with MTV 2.2.0-1?
Verified. Versions: MTV 2.2.0-20 / iib: 113682 CNV 4.8.3-11 / iib:117885 (PSI) Step to reproduce: As mentioned in bug description Actual result: NetworkMap is invalid with reason: "Ambiguous" and appropriate message: "Destination network (NAD) namespace required." Until editing NetworkMap with the NAD namespace $ oc describe networkmap.forklift.konveyor.io/rdu2-to-ocp ... Status: Conditions: Category: Critical Items: unique-nad-name Last Transition Time: 2021-10-05T08:19:41Z Message: Destination network (NAD) namespace required. Reason: Ambiguous Status: True Type: DestinationNetworkNotValid Observed Generation: 1 References: Id: network-14 Name: VM Network Id: network-13 Name: Mgmt Network Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning DestinationNetworkNotValid 15s networkMap Destination network (NAD) namespace required.
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 (MTV 2.2.0 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/RHEA-2021:5066