Setting quota fails saying admin project is not a valid project
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Sean Dague | ||
kolla-kubernetes |
New
|
Undecided
|
Chung Chih, Hung | ||
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
This is what's in the logs http://
2017-02-24 11:07:08.893276 | 2017-02-24 11:07:02.000 | 2017-02-24 11:07:02,929 INFO: + openstack quota set --cores -1 --instances -1 --ram -1 b0fe52b0ac15450
2017-02-24 11:07:08.893365 | 2017-02-24 11:07:08.000 | 2017-02-24 11:07:08,674 INFO: Project ID b0fe52b0ac15450
2017-02-24 11:07:08.893493 | 2017-02-24 11:07:08.000 | 2017-02-24 11:07:08,758 INFO: [2017-02-24 11:07:08,757] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/
Changed in tripleo: | |
status: | New → Triaged |
milestone: | none → pike-1 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in kolla-kubernetes: | |
assignee: | nobody → Chung Chih, Hung (lyanchih) |
Changed in nova: | |
importance: | Low → High |
assignee: | nobody → Sean Dague (sdague) |
This is because checking for the validity of the project_id was recently added to nova with this patch https:/ /github. com/openstack/ nova/commit/ f6fbfc7ff07b790 ef052a759552c69 429b3d79c7 However, it seems that it's tied to using keystone v3, while it should be using the keystoneclient's functions and attempt to be version agnostic.