Description of problem: When the migration controller pod is deleted, and it is recreated again, the data in the MigAnalytic resources is corrupted. Version-Release number of selected component (if applicable): MTC 1.3 How reproducible: Always Steps to Reproduce: 1. Create an application in a namespace oc new-project bztest oc new-app mysql-persistent 2. Create a migration plan with name "bztest" for this namespace 3. Check the analytic data for this migration plan $ oc get miganalytic bztest NAME READY PLAN PROGRESS RESOURCES IMAGES IMAGESIZE PVS PVCAPACITY bztest True bztest 100 53 0 0 1 1Gi 4. Delete the migration controller pod $ oc delete pods -l control-plane 5. Wait until the pod is created again $ oc get pods -l control-plane NAME READY STATUS RESTARTS AGE migration-controller-59f565d48d-s5rvk 2/2 Running 0 29s Actual results: The analytic data has been corrupted, and every time we reset the controller, new data is added to the existing anaylytic. $ oc get miganalytic bztest NAME READY PLAN PROGRESS RESOURCES IMAGES IMAGESIZE PVS PVCAPACITY bztest True bztest 100 112 0 0 2 2Gi Expected results: The analytic data should be the right one after the migrationcontroller is restarted Additional info:
https://github.com/konveyor/mig-controller/pull/668
verified with MTC 1.3.0.
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) Tool image release advisory 1.3.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/RHBA-2020:4148