yahoo-eng-team team mailing list archive

[Feodor Tersin <ftersin@xxxxxxxxxxxxxxxx>]

The same result is occured with a deleted public flavor or when a private flavor become inaccessible for the instance project.
For all cases Nova reports the flavor id and doesn't crash. The failure occures in novaclient side.
Nova reports the id always, even when the flavor exists and is accessible.

Similar cases could occure with an instance image. But novaclient
properly handles these, though Nova returns only image id as well.

So i propose to fix this in novaclient and do nothing for Nova.

** Also affects: python-novaclient
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1366168

Title:
  delete private flavor will cause access problem with existed instance

Status in OpenStack Compute (Nova):
  Confirmed
Status in Python client library for Nova:
  New

Bug description:
  How to reproduce

  
  1. create a private flavor "private-flavor"
  2. add a tenant access to "private-flavor"
  3. use Member role user to create instance "XXX" with "private-flavor"
  4. nova flavor-delete "private-flavor" with admin role
  5. nova show XXX with Member role suer, will be end with error message say do not have access to the flavor

  
  Reason 

  the delete a flavor will also delete the access in
  instance_type_projects table

  
  Solution

  One quick solution is mark flavor as public while do soft delete

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1366168/+subscriptions