yahoo-eng-team team mailing list archive

[Julie Pichon <1366166@xxxxxxxxxxxxxxxxxx>]

The Nova patch is currently -2d and I have a Horizon patch ready for
this, so I'm reopening and assigning to myself.

There are 3 issues once this problem occurs:

1. The Instance details page become inaccessible. This is particularly problematic because of the Console tab, as it means end-users cannot access the console anymore
2. The Resize screen doesn't open anymore, so users can't even switch the instance to use another flavor that is accessible to them
3. For operations that requires updates for "in progress" operations, the instance row disappears from the table because of the failure to get the flavor

Even if the Nova patch merges soon, I think the Horizon one remains
useful because it lets us handle failures on retrieving flavor
information more gracefully. Even if that API call fails and we can't
tell what's the size of the instance, we shouldn't bar the user from
using the console or accessing other information.

The problem can also be reproduced in Juno and Icehouse.

** Changed in: horizon
       Status: Invalid => Confirmed

** Changed in: horizon
   Importance: Undecided => Medium

** Changed in: horizon
     Assignee: Wei T (nuaafe) => Julie Pichon (jpichon)

** Tags added: icehouse-backport-potential juno-backport-potential

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

Title:
  Private flavor update with horizon will cause access issue of existed
  instances

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  How to reproduce

  1. create a private flavor "private-flavor"
  2. add a tenant access to "private-flavor"
  3. use regular user to create instance "XXX" with "private-flavor"
  4. add/remove tenant access to the "private-flavor" via horizon
  5. nova show XXX, will be end with error message say do not have access to the flavor

  Root cause,

  add/remove tenant access to the "private-flavor" via horizon. will do
  delete old one which will also delete the access to the old flavor,
  create new one with the same configuration, and add accesses back to
  the new flavor.

  The version before H3, horizon will pass flavor uuid to backend then
  will create new flavor with the same uuid, that's why it didn't cause
  problem, but it also cause another bug
  https://bugs.launchpad.net/horizon/+bug/1276371

  
  one quick solution is mark  deleted flavor as public in nova

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