-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
2.6.3
-
None
-
False
-
None
-
False
-
-
When creating a Migration Plan for OCPv->OCPv using the form, the network map generated is missing the source namespace causing VMNetworkNotMapped error on the plan. Editing the YAML and adding the namespace to the source fixes this issue:
Generated YAML:
spec:
map:
- destination:
name: vlan-4020
namespace: ctc-windows
type: multus
source:
id: adf78721-65b6-4d8e-a3ca-3adcdc527702
name: vlan-4020
type: openshift
- destination:
name: pod
namespace: ''
type: pod
source:
type: pod
Manually updated:
spec:
map:
- destination:
name: vlan-4020
namespace: ctc-windows
type: multus
source:
id: adf78721-65b6-4d8e-a3ca-3adcdc527702
name: vlan-4020
namespace: default
type: openshift
- destination:
name: pod
namespace: ''
type: pod
source:
type: pod
Expection:
The YAML generated for the NetworkMap using the Plan Creation Form contains the namespace for Source objects when the source provider is an Openshift Provider Type.
