Description of problem:
When the cutover value is set on the Migration CR, the precopies are not shown in UI
In the UI the warm migration plan starts immediately with "Transfer disk" step
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I'm not sure I understand what the problem is. What would you expect that doesn't happen?
I expect that a prcopy will be executed every X minutes
I changed the interval time between precopies to be 8 minutes. Now, if the cutover value is set on Plan CR (future value), I see by watching the DataVolume that every 8 minuets it gets into "ImportInProgress", meaning that a disk copy is taken. Between the copies the DataVolume phase is "paused". At the cutover time the DataVolume phase is again "ImportInProgress" and after it "succeeded".
If the cutover value is set on Migration CR (future value), first the DataVolume phase is "ImportInProgress", after one copy it gets into "paused" and stay paused till the cutover time. At the cutover time it becomes "ImportInProgress" and "succeeded". Without more precopies
I will add screenshots of UI for both cases, both display migration plan in state "paused" and before cutover time
Created attachment 1778954 [details]
Created attachment 1778955 [details]
The issue was tested again with mtv-operator 2.0.0-4 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1594105
the precopies actually are taken every X minutes, but they are not reflected in UI
@firstname.lastname@example.org, what is the UI looking at to reflect the precopy iterations? The Migration or the Plan CR?
@email@example.com, where is the precopy iterations status written? The Migration or the Plan CR?
I would expect it to be on the Migration CR, since it represents the execution of a plan, but I may miss something.
Can you please try to reproduce with build 2.0.0-8 / iib:72981. It might be fixed.
Verified as fixed. Thanks
I know it's verified, but for posterity I'll answer the above questions anyway:
> what is the UI looking at to reflect the precopy iterations? The Migration or the Plan CR?
The UI looks at the plan CR which has a whole `warm` object conveniently summarized in the status for me. I'm not looking at the Migration or the DataVolume.
> where is the precopy iterations status written? The Migration or the Plan CR? I would expect it to be on the Migration CR, since it represents the execution of a plan, but I may miss something.
All the status data for the migration is actually written to both the Migration CR and also denormalized in the status section of the Plan CR for convenience. Most of the UI just reads from the plan CR and treats the Migration CR as write-only (with the current exception of canceled VM ids).