← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1944947] Re: NUMA instance with shared CPU policy cannot be restarted after upgrade to Victoria

 

*** This bug is a duplicate of bug 1952941 ***
    https://bugs.launchpad.net/bugs/1952941

This should be resolved by
https://review.opendev.org/c/openstack/nova/+/820153

** This bug has been marked a duplicate of bug 1952941
   Migration fails with "NotImplementedError: Cannot load 'pcpuset' in the base class" when a pre Victoria instance with cpu pinning is migrated in Victoria

-- 
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/1944947

Title:
  NUMA instance with shared CPU policy cannot be restarted after upgrade
  to Victoria

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========
  NUMA instances without hw:cpu_policy=dedicated set cannot be restarted after upgrading from Ussuri to Victoria. The nova-compute service fails with the following exception:

  NotImplementedError: Cannot load 'pcpuset' in the base class

  Steps to reproduce
  ==================
  * Deploy Nova using Ussuri
  * Create a flavor with hw:numa_nodes='2' but without setting hw:cpu_policy
  * Start instance with flavor
  * Upgrade Nova to Victoria
  * openstack server stop <instance>
  * openstack server start <instance>

  Expected result
  ===============
  Instance should start.

  Actual result
  =============
  Instance doesn't start.

  Environment
  ===========
  python3-nova-22.2.2-1.el8.noarch
  openstack-nova-compute-22.2.2-1.el8.noarch

  Packaged as Docker images by Kolla.

  Logs & Configs
  ==============
  The following trace is logged: https://paste.openstack.org/show/809556/

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



References