yahoo-eng-team team mailing list archive

[Matthew Heler <2080436@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The commit c1ccc1a3165ec1556c605b3b036274e992b0a09d introduced
a regression when NUMA live migration was done on shared storage

            power_management_possible = (
                'dst_numa_info' in migrate_data and
                migrate_data.dst_numa_info is not None)
            # No instance booting at source host, but instance dir
            # must be deleted for preparing next block migration
            # must be deleted for preparing next live migration w/o shared
            # storage
            # vpmem must be cleaned
            do_cleanup = (not migrate_data.is_shared_instance_path or
                          has_vpmem or has_mdevs or power_management_possible)

Based on the commit, if any type of NUMA system is used with shared
storage. Live migration will delete the backing folder for the VM,
making the VM unusable for future operations.

My team is experiencing this issue on 2024.1

** Affects: nova
     Importance: Undecided
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2080436

Title:
  Live migration breaks VM on NUMA enabled systems with shared storage

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The commit c1ccc1a3165ec1556c605b3b036274e992b0a09d introduced
  a regression when NUMA live migration was done on shared storage

              power_management_possible = (
                  'dst_numa_info' in migrate_data and
                  migrate_data.dst_numa_info is not None)
              # No instance booting at source host, but instance dir
              # must be deleted for preparing next block migration
              # must be deleted for preparing next live migration w/o shared
              # storage
              # vpmem must be cleaned
              do_cleanup = (not migrate_data.is_shared_instance_path or
                            has_vpmem or has_mdevs or power_management_possible)

  Based on the commit, if any type of NUMA system is used with shared
  storage. Live migration will delete the backing folder for the VM,
  making the VM unusable for future operations.

  My team is experiencing this issue on 2024.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2080436/+subscriptions