Bug 1314866

Summary:	Deleting a private flavor causes access issues with existing instances
Product:	Red Hat OpenStack	Reporter:	Chris St. Pierre <cstpierr>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED DUPLICATE	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0 (Liberty)	CC:	berrange, charcrou, dasmith, eglynn, jdonohue, kchamart, mpryc, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1326625 (view as bug list)		Environment:
Last Closed:	2016-04-13 08:43:46 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:	1194008

Description Chris St. Pierre 2016-03-04 17:45:06 UTC

Description of problem:

Deleting or modifying a private flavor causes various issues when displaying instances booted with that flavor: https://bugs.launchpad.net/nova/+bug/1366168

We'd like the pending upstream fix to be backported into OSP8.

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


How reproducible:

Always

Steps to Reproduce:

https://bugs.launchpad.net/nova/+bug/1366168/comments/17

Actual results:

https://bugs.launchpad.net/nova/+bug/1366168/comments/17

Expected results:

https://bugs.launchpad.net/nova/+bug/1366168/comments/17

Additional info:

Upstream patch is pending at https://review.openstack.org/#/c/211809/

Comment 3 Michal Pryc 2016-03-30 18:52:55 UTC

With the rework of the Flavors the Upstream change
https://review.openstack.org/#/c/211809/ will not be approved.

Nova engineering team will produce another fix for nova client that will
not fail when displaying instances with deleted private flavors.

Comment 4 Michal Pryc 2016-04-13 08:43:46 UTC


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