Adding current project as flavor access is throwing an error
Bug #1286297 reported by
Santiago Baldassin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Santiago Baldassin | ||
OpenStack Dashboard (Horizon) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce
1. Create a new flavor, setting and add the current project as flavor access
2. The flavor is created but an error is displayed saying "Unable to set flavor access for project....."
The error is thrown because Horizon creates the flavor and add the access after that. The problem is that once a private flavor is created, nova adds the current project within the flavor accesses so when Horizon tries to add the access, nova throws an "Access already exist for this flavor" exception
Changed in horizon: | |
assignee: | nobody → Santiago Baldassin (santiago-b-baldassin) |
description: | updated |
summary: |
- Creating a flavor with access is throwing an error + Adding current project as flavor access is throwing an error |
description: | updated |
Changed in nova: | |
assignee: | nobody → Santiago Baldassin (santiago-b-baldassin) |
tags: | added: console |
tags: |
added: compute removed: console |
Changed in nova: | |
status: | Incomplete → New |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-rc1 → 2014.1 |
tags: |
added: nova removed: compute |
To post a comment you must log in.
I see two alternatives to solve the issue.
1. Avoid adding the current project when a non public flavor is created
2. in Horizon, before adding the tenants selected by the user, remove all flavor access that already exist.