Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1766936

Summary: [RFE] allow in-place rebuild for numa instances
Product: Red Hat OpenStack Reporter: Erwan Gallen <egallen>
Component: openstack-novaAssignee: OSP DFG:Compute <osp-dfg-compute>
Status: CLOSED DUPLICATE QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: urgent Docs Contact:
Priority: high    
Version: 16.0 (Train)CC: dasmith, eglynn, jhakimra, kchamart, lyarwood, sbauza, sgordon, vromanso
Target Milestone: ---Keywords: FeatureBackport, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-19 16:21:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Erwan Gallen 2019-10-30 10:17:24 UTC 
This bug was initially created as a copy of Bug #1700412

I am copying this bug because: 



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 2 Lee Yarwood 2020-02-19 16:21:47 UTC 

*** This bug has been marked as a duplicate of bug 1775246 ***