The user_id field is missing from RequestSpec
Bug #1768107 reported by
Mathieu Gagné
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mathieu Gagné |
Bug Description
The user_id field used to be available from filter_properties in Nova scheduler filter:
filter_
This change introduced a regression where user_id is no longer available when using the new RequestSpec object that Nova scheduler filter now uses:
https:/
Changed in nova: | |
assignee: | nobody → Mathieu Gagné (mgagne) |
status: | New → In Progress |
Changed in nova: | |
assignee: | Mathieu Gagné (mgagne) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Mathieu Gagné (mgagne) |
To post a comment you must log in.
To be clear, there are no in-tree filters that rely on RequestSpec. user_id, but people have out of tree filters that could have been using filter_ properties[ 'instance_ properties' ]['user_ id'] and the change in mitaka regressed them. It also seems OK to have RequestSpec.user_id since we have RequestSpec. project_ id, and I could see it being useful to know which user created an instance when it's being moved if another user in the same project is moving the instance.