Bug 1966417

Summary: Migration Resources tree on the Migration Details page in the web console is not updated
Product: Migration Toolkit for Containers Reporter: Xin jiang <xjiang>
Component: UIAssignee: Derek Whatley <dwhatley>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: low Docs Contact: Avital Pinnick <apinnick>
Priority: low    
Version: 1.5.0CC: ernelson, mnadeem, rjohnson, sregidor, whu
Target Milestone: ---   
Target Release: 1.5.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: 2021-07-28 04:08:07 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:
Attachments:
Description Flags
tree view none

Description Xin jiang 2021-06-01 06:25:21 UTC
Created attachment 1788421 [details]
tree view

Description of problem:
When the Stage operation Completed, there are some resource still stuck at Pending or Active status. For instance, DVM, DVMP. see the screenshot.


Version-Release number of selected component (if applicable):
MTC 1.5.0

How reproducible:
Always

Steps to Reproduce:
1. Deploy application on source cluster 
$  ansible-playbook deploy-app.yml -e use_role=ocp-django -e namespace=testns1
$  ansible-playbook deploy-app.yml -e use_role=ocp-django -e namespace=testns2

2. Create a migplan with default target namespaces
3. Execute Stage operation

Actual results:
The Stage operation completed, and some of resources are still in Pending or Active status. 

Expected results:
The resources should be showing proper status, for instance, "Completed" status.

Additional info:
$  oc -n openshift-migration get migmigration
NAME          READY   PLAN          STAGE   ROLLBACK   ITINERARY   PHASE       AGE
stage-60ab6           test2         true               Stage       Completed   47m
stage-77b40           test2         true               Stage       Completed   39m
stage-a4925           testmapping   true               Stage       Completed   81m



$ oc get dvmp -n openshift-migration
NAME                               CLUSTER          POD NAME          POD NAMESPACE   PROGRESS   TRANSFER RATE   AGE
274ac526d639e8f6d0d0be98a7eb806f   source-cluster   dvm-rsync-krxrd   testns2         100%                       11m
a2337aec16d5ac709c266453bcfb4d1c   source-cluster   dvm-rsync-krxrd   testns2         100%                       3m35s
b045c0feac2972e8d944ec0d17ef4b64   source-cluster   dvm-rsync-z5lfr   testns1         100%                       3m35s
f38ec645dcb3f0f91bce0c629665a722   source-cluster   dvm-rsync-z5lfr   testns1         100%                       11m

Comment 1 Derek Whatley 2021-06-09 20:01:54 UTC
Hi Xin,

I ran a stage migration on robot-shop from mig-demo-apps using deploy.sh and saw that the tree view had correct content after my posted UI update. Please let me know if this resolves the problem on your end.

Comment 6 Sergio 2021-06-29 15:19:14 UTC
Verified using MTC 1.5.0

   openshift-migration-rhel7-operator@sha256:00e77706ca22bcb557d13c16822180fc877e6ea1639a72fda8eb9f5488b039a2
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 7f657df15e9514df4ef42da3431f558a19b8d3233a2ef1222cd8e27793c93816
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: bda1959e1f44170905499b304ce28f9f95ee1841b0dc29f9a9e2790d0dd0bd71

No resource are pending after the stage operation ends.


Moved to VERIFIED.

Comment 12 errata-xmlrpc 2021-07-28 04:08:07 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) image release advisory 1.5.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.

https://access.redhat.com/errata/RHEA-2021:2929