Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-19025

[2095221] "migration finalized successfully" in target virt launcher pod before the VM migration completion

XMLWordPrintable

    • CNV Virtualization Sprint 231, CNV Virtualization Sprint 232, CNV Virtualization Sprint 233, CNV Virtualization Sprint 234, CNV Virtualization Sprint 239
    • Moderate
    • No

      Description of problem:

      In virt-launcher target pod below message is logged before the migration completion.

      ~~~

      {"component":"virt-launcher","kind":"","level":"info","msg":"migration finalized successfully","name":"rhel8-organisational-pony","namespace":"nijin-cnv","pos":"server.go:329","timestamp":"2022-03-15T07:16:12.784845Z","uid":"31323a86-8f9d-425b-aec9-5ac514e8279d"}

      ~~~

      This is from `FinalizeVirtualMachineMigration` which is called from here https://github.com/kubevirt/kubevirt/blob/5bf9394089f6790279aad9ac2001a7a230d34ec3/pkg/virt-handler/vm.go#L681.

      This is an early stage of VM migration where the libvirt domain gets detected on the target pod. The actual "libvirt" migration starts after this (movement of memory) and even if this fails, we still see the above message. With the above message, users get an impression that the migration is completed although it's not.

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

      4.10

      How reproducible:

      100%

      Steps to Reproduce:
      1. Live migrate a virtual machine and watch the target virt-launcher pod for the above messages. We can see that this message is logged in the early stage of migration.

      Actual results:

      "migration finalized successfully" in the target virt launcher pod before the VM migration completion

      Expected results:

      Additional info:

              jelejosne Jed Lejosne
              rhn-support-nashok Nijin Ashok
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: