Bug 1700412 - [RFE] Allow in-place rebuild for numa instances
Summary: [RFE] Allow in-place rebuild for numa instances
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: Alpha
: 17.0
Assignee: smooney
QA Contact: James Parker
URL:
Whiteboard:
: 1714039 1751449 (view as bug list)
Depends On:
Blocks: epmosp17features, epmosp17rfe 1751454 1775246 1791998 1821416
TreeView+ depends on / blocked
 
Reported: 2019-04-16 13:39 UTC by Andre
Modified: 2023-09-07 19:55 UTC (History)
21 users (show)

Fixed In Version: openstack-nova-21.1.0-0.20200425164546.347d656.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1775246 (view as bug list)
Environment:
Last Closed: 2022-09-21 12:07:43 UTC
Target Upstream Version: Ussuri
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1763766 0 None None None 2019-09-11 17:42:13 UTC
Launchpad 1804502 0 None None None 2019-05-26 20:22:11 UTC
OpenStack gerrit 687957 0 'None' MERGED Block rebuild when NUMA topology changed 2021-01-19 11:20:14 UTC
OpenStack gerrit 689861 0 'None' MERGED Disable NUMATopologyFilter on rebuild 2021-01-19 11:20:14 UTC
Red Hat Issue Tracker OSP-3133 0 None None None 2022-01-26 11:35:44 UTC
Red Hat Knowledge Base (Solution) 4105801 0 Troubleshoot None Rebuild instance with a different image fails due to NUMATopologyFilter 2019-05-26 20:20:25 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:08:48 UTC

Description Andre 2019-04-16 13:39:04 UTC 
Description of problem:
when customer execute "openstack stack update -t heat.yaml -e heat.env stack_name" with only new image indicated in heat.env, stack update is failed because of "no valid host found". In nova log we can see that nova-scheduler is searching for new resources (cpu, ram) to rebuild instance instead of using the same resources. That's why numatopolgy filter can not find new CPUs to pin and it's reported that no valid host was found.

Version-Release number of selected component (if applicable):
openstack-nova-api-14.1.0-27.el7ost
openstack-nova-cert-14.1.0-27.el7ost
openstack-nova-common-14.1.0-27.el7ost
openstack-nova-compute-14.1.0-27.el7ost
openstack-nova-conductor-14.1.0-27.el7ost
openstack-nova-console-14.1.0-27.el7ost
openstack-nova-migration-14.1.0-27.el7ost
openstack-nova-novncproxy-14.1.0-27.el7ost
openstack-nova-scheduler-14.1.0-27.el7ost

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 smooney 2019-10-15 15:05:29 UTC 
*** Bug 1714039 has been marked as a duplicate of this bug. ***
Comment 5 smooney 2019-10-15 15:10:37 UTC 
*** Bug 1751449 has been marked as a duplicate of this bug. ***
Comment 20 errata-xmlrpc 2022-09-21 12:07:43 UTC 
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543
Note You need to log in before you can comment on or make changes to this bug.