Bug 1313894

Summary:	nova start fails in case flavor is deleted and archived in OSP 6
Product:	Red Hat OpenStack	Reporter:	Martin Tessun <mtessun>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED WONTFIX	QA Contact:	nlevinki <nlevinki>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	berrange, dasmith, dgurtner, eglynn, kchamart, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	6.0 (Juno)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-04 15:29:49 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:

Description Martin Tessun 2016-03-02 15:05:35 UTC

Description of problem:
In case a stopped instance is started after the flavor of it has been deleted and archived, the instance does not start up.

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

How reproducible:
always

Steps to Reproduce:
1. Create a flavor
2. Create an instance based on the flavor
3. Delete the flavor
4. Stop the instance
5. Start the instance
6. Archive the flavor
7. Stop the instance
8. Start the instance

Actual results:
The instance does not start in Step (8)

Expected results:
The instance should still start.

Additional info:
This scenario does work if OSP 7 is used.

Comment 2 Dan Smith 2016-03-03 15:11:24 UTC

OSP7 specifically addresses this by putting flavor data into the instance record itself. That was a ton of work and definitely not backportable to OSP7. In all time before OSP7, if you actually hard delete the flavor from the database (as you're doing by a delete+archive) then the instance can't start because we have lost vital data about it.

The solution is to never purge flavors in OSP6 and previous.