Public bug reported: As we move towards having 'reader' roles in nova, we can get into some interesting situations where a user can see a resource but not use it.
Today I have a case where I've added a private flavor to projects A and B, created a VM in project B, and then removed the flavor project B. I belong to both projects, so in some contexts I can still see the flavor. In the Horizon instance view for project A, though, the flavor is shown as 'not available'. That's reasonable behavior, but it happens to be unnecessary. The code change to make the flavor appear for that VM is trivial, and doesn't affect the ability to create VMs with the removed flavor (which would be bad). Supporting this case also provides a potential solution to the issue raised in bug 1259262, phasing out a flavor without causing VMs to know know what size they are; flavors can be moved out of scope for a project (thus preventing their re-use for new instances) but still remain viewable by the project. ** Affects: horizon Importance: Undecided Status: New -- 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/1919369 Title: Instances panel shows some readable flavors as 'Not available ' Status in OpenStack Dashboard (Horizon): New Bug description: As we move towards having 'reader' roles in nova, we can get into some interesting situations where a user can see a resource but not use it. Today I have a case where I've added a private flavor to projects A and B, created a VM in project B, and then removed the flavor project B. I belong to both projects, so in some contexts I can still see the flavor. In the Horizon instance view for project A, though, the flavor is shown as 'not available'. That's reasonable behavior, but it happens to be unnecessary. The code change to make the flavor appear for that VM is trivial, and doesn't affect the ability to create VMs with the removed flavor (which would be bad). Supporting this case also provides a potential solution to the issue raised in bug 1259262, phasing out a flavor without causing VMs to know know what size they are; flavors can be moved out of scope for a project (thus preventing their re-use for new instances) but still remain viewable by the project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1919369/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp