Bug 2045036 - [MTC UI] UI becomes blank when we change the namespace per page value
Summary: [MTC UI] UI becomes blank when we change the namespace per page value
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 1.7.0
Assignee: Jaydip Gabani
QA Contact: Xin jiang
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-25 13:36 UTC by Prasad Joshi
Modified: 2022-03-24 06:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-24 06:32:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-ui pull 1380 0 None open Bug 2045036: making sure plan doesn't get fetched in map everytime 2022-01-31 20:17:18 UTC
Red Hat Product Errata RHBA-2022:1043 0 None None None 2022-03-24 06:32:36 UTC

Comment 4 Prasad Joshi 2022-02-02 07:46:58 UTC
Verified with MTC 1.7.0

metadata_nvr: openshift-migration-operator-metadata-container-v1.7.0-26

$ oc get pods -n openshift-migration migration-controller-5dccf94877-75wtn -oyaml
registry.redhat.io/rhmtc/openshift-migration-controller-rhel8@sha256:db04235e98ace157246f09753cf16cdd7e495a78d1c740cea333ae5c0fa30779

After changing the namespace per page value UI is not going blank anymore. Also search box is working fine here.

Moving to verified status.

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


Note You need to log in before you can comment on or make changes to this bug.