Comment 4Denys Shchedrivyi
2022-02-04 19:49:56 UTC
Verified on CNV v4.9.3-16
In virt-controller logs I see the message about hitting the migration limits:
{"component":"virt-controller","kind":"","level":"info","msg":"Waiting to schedule target pod for vmi [default/vm-5] migration because total running parallel outbound migrat
ions on target node [2] has hit outbound migrations per node limit.","name":"job-5","namespace":"default","pos":"migration.go:714","timestamp":"2022-02-04T19:37:19.968194Z",
"uid":"d9d535b9-8062-4428-b664-9c6badda2a8a"}
And VMIM objects look much more informative:
$ oc get vmim -o wide
NAME PHASE VMI
job-1 Succeeded vm-1
job-2 Succeeded vm-2
job-3 Running vm-3
job-4 Scheduling vm-4
job-5 Pending vm-5
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 (OpenShift Virtualization 4.9.3 Images), 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:0641
Verified on CNV v4.9.3-16 In virt-controller logs I see the message about hitting the migration limits: {"component":"virt-controller","kind":"","level":"info","msg":"Waiting to schedule target pod for vmi [default/vm-5] migration because total running parallel outbound migrat ions on target node [2] has hit outbound migrations per node limit.","name":"job-5","namespace":"default","pos":"migration.go:714","timestamp":"2022-02-04T19:37:19.968194Z", "uid":"d9d535b9-8062-4428-b664-9c6badda2a8a"} And VMIM objects look much more informative: $ oc get vmim -o wide NAME PHASE VMI job-1 Succeeded vm-1 job-2 Succeeded vm-2 job-3 Running vm-3 job-4 Scheduling vm-4 job-5 Pending vm-5