Bug 1935357 - After some migration plans have run, Direct Image Migration process does not show progress
Summary: After some migration plans have run, Direct Image Migration process does not ...
Keywords:
Status: NEW
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.4.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-04 17:12 UTC by Guillermo Ojea Quitana
Modified: 2022-10-14 20:00 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Visual description of bug (28.60 KB, image/png)
2021-03-04 17:12 UTC, Guillermo Ojea Quitana
no flags Details

Description Guillermo Ojea Quitana 2021-03-04 17:12:35 UTC
Created attachment 1760732 [details]
Visual description of bug

Description of problem:
When there are some migration plans that already have run and a new one is created, when the process gets to the Direct Image Migration the "Details" web link does not appear.
(this issue is related to https://bugzilla.redhat.com/show_bug.cgi?id=1934666)

When this happens BZ 1934666 gets triggered and the migration controller pod starts crashing in a loop

Version-Release number of selected component (if applicable):
v1.4.1

How reproducible:
Often

Steps to Reproduce:
1. Create several migration plans (at least 4 or more) all with direct image migration and of different namespaces
2. Create an addition migration plan with another namespace and also using direct image migration
3. Run the migration plan and in the plan details when it gets to image migration the "Details" does not show, also BZ 1934666 gets triggered

Actual results:
Migration fails

Expected results:
Migration succeeds

Additional info:
WORKAROUND: A possible workaround that has solved the issue in some situations has been to delete all the migration plans created and only then create a new one.
Also it seems that it is also necessary to restart the migration-controller pod if it had many restarts.
I have to do more testing yet.


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