Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-10183

old nova instances cant be started on post victoria deployments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhos-18.0.2
    • rhos-18.0.0, rhos-18.0.1
    • openstack-nova
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • No Docs Impact
    • openstack-nova-27.5.1-18.0.20240919174811.cf08543.el9osttrunk
    • ?
    • ?
    • None
    • Hide
      .Fix for instances created before OpenStack Victoria

      In OpenStack Victoria, the instance_numa_topology object was extended to enable mix cpus (pinned and unpinned cpus) in the same instance.
      Object conversion code was added to handle upgrades but did not account for flavors that have either `hw:mem_page_size` or `hw:numa_nodes` set with `hw:cpu_policy` not set to dedicated

      As a result instances created before the victoria release could not be started after an upgrade to victoria.

      With this update, non-pinned numa instances can be managed after an FFU from 16.2.
      Show
      .Fix for instances created before OpenStack Victoria In OpenStack Victoria, the instance_numa_topology object was extended to enable mix cpus (pinned and unpinned cpus) in the same instance. Object conversion code was added to handle upgrades but did not account for flavors that have either `hw:mem_page_size` or `hw:numa_nodes` set with `hw:cpu_policy` not set to dedicated As a result instances created before the victoria release could not be started after an upgrade to victoria. With this update, non-pinned numa instances can be managed after an FFU from 16.2.
    • Bug Fix
    • Done
    • Regression Only
    • Important

      This is the 18 backport tracker for
      https://bugzilla.redhat.com/show_bug.cgi?id=2311875

      tl;dr in a down stream context instance create before osp 17
      that request a numa topology without CPU pinning cannot be
      managed by OSP 17.1.3 nova as we are missing migration code
      to uplevel the instance numa topology object to a compatible version.

      this is addressed upstream by https://bugs.launchpad.net/nova/+bug/2080436
      vai https://review.opendev.org/c/openstack/nova/+/929025/3 and https://review.opendev.org/c/openstack/nova/+/929187/3

              smooney@redhat.com Sean Mooney
              smooney@redhat.com Sean Mooney
              rhos-dfg-compute
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: