Bug 2005998

Summary:	[MTC UI] Migplan should display correct target namespace
Product:	Migration Toolkit for Containers	Reporter:	Prasad Joshi <prajoshi>
Component:	UI	Assignee:	Jaydip Gabani <jgabani>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	1.6.0	CC:	ernelson, prajoshi, rjohnson, sregidor, ssingla, xjiang
Target Milestone:	---
Target Release:	1.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-24 06:32:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Prasad Joshi 2021-09-20 16:13:16 UTC

Description of problem: When we click on edit migplan it should show correct information related to the target namespace.


Version-Release number of selected component (if applicable):
SOURCE CLUSTER: AWS 4.6 (MTC 1.6.0)
TARGET CLUSTER: AWS 4.9 (MTC 1.6.0) (CONTROLLER + UI)

How reproducible:
Always


Steps to Reproduce:
1. Create a migplan from UI. Change the target namespace.
2. Click on edit migplan and go to the namespace page.

Actual results: Migplan is showing wrong target namespace


Expected results: Migplan should show correct target namespace


Additional info: 
In backend we can see the correct target namespace.

oc get migplan -n openshift-migration state-migration -o yaml
spec:
  destMigClusterRef:
    name: source-cluster
    namespace: openshift-migration
  migStorageRef:
    name: automatic
    namespace: openshift-migration
  namespaces:
  - cakephp:cakephp-new

Comment 6 errata-xmlrpc 2022-03-24 06:32:27 UTC

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 Containers (MTC) 1.7.0 release advisory), 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-2022:1043