Description of problem: If the migration is stuck, the virt-launcher logs the message as below in nanoseconds: ~~~ 2022-04-26T21:13:55.787653425Z {"component":"virt-launcher","kind":"","level":"error","msg":"Live migration abort detected with reason: Live migration stuck for 151375341154 sec and has been aborted","name":"a61b96652007"} ~~~ This should be logged in seconds instead of nanoseconds. Version-Release number of selected component (if applicable): OpenShift Virtualization 4.10.0 How reproducible: 100% Steps to Reproduce: 1. The VM has to hit the progresstimeout to show that error message. For testing, this can be achieved by reducing the progressTimeout and bandwidthPerMigration. Actual results: virt-launcher logs live migration in nanoseconds if the migration is stuck Expected results: Log migration stuck message in seconds. Additional info:
Fixed upstream with https://github.com/kubevirt/kubevirt/pull/7654.
Verified on CNV v4.11.0-334, time is in seconds: > {"component":"virt-launcher","kind":"","level":"error","msg":"Live migration abort detected with reason: Live migration stuck for 2 seconds and has been aborted" ...
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 (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), 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/RHSA-2022:6526