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

Bug 1751449

Summary: [RFE] allow in-place instance rebuild
Product: Red Hat OpenStack Reporter: jzaher
Component: openstack-novaAssignee: OSP DFG:Compute <osp-dfg-compute>
Status: CLOSED DUPLICATE QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: high Docs Contact:
Priority: high    
Version: 16.0 (Train)CC: dasmith, eglynn, jhakimra, kchamart, mbooth, sbauza, sgordon, smooney, vromanso
Target Milestone: ---Keywords: FutureFeature, 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:
: 1751454 (view as bug list) Environment:
Last Closed: 2019-10-15 15:10:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1751454    

Description jzaher 2019-09-12 03:54:26 UTC
Description of problem:

The goal of this RFE would be to develop a feature by which a user could run "server rebuild" on an instance running in a dense cloud using CPU pinning.  The feature should allow completion of the rebuild even if the only available pins for the newly-rebuilt instance are the ones that the existing instance are consuming prior to deletion.

Version-Release number of selected component (if applicable):

Root BZ for Train (OSP16)

How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Currently this is to serve as a placeholder for tracking while our customer develops the spec for the intended feature.

Comment 1 Artom Lifshitz 2019-09-12 18:17:03 UTC
The earliest this could possibly happen is OSP17, because OSP16/Train's upstream feature freeze was today. I'll remove the release from the name and allow the RFE triage process to take place.

Comment 4 smooney 2019-10-15 15:10:37 UTC

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