Pecan is missing logic to add project_id to fields when tenant_id is specified
Bug #1714378 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Kevin Benton |
Bug Description
Pecan is missing this logic in the old controller code that adds 'tenant_id' to the filters required by the policy engine when the 'project_id' field is specified: https:/
This is necessary when tenants request that only the tenant_id field is returned and we have a new class of resource that has a project_id field only.
Changed in neutron: | |
importance: | Undecided → High |
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
status: | New → In Progress |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/499429 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=bf36f8c934b 49310103a1b1831 c9f7c8a0d14adf
Committed: https:/
Submitter: Jenkins
Branch: master
commit bf36f8c934b4931 0103a1b1831c9f7 c8a0d14adf
Author: Kevin Benton <email address hidden>
Date: Wed Aug 30 20:05:30 2017 -0700
Pecan: set tenant_id field when project_id set
Add logic to pecan to add 'project_id' as a mandatory policy
field whenever 'tenant_id' is specified as a policy field.
This logic was added to the previous controller code to ensure
that 'project_id' was queried in the database whenever 'tenant_id'
was required by the policy engine and the user had fields set.
Closes-Bug: #1714378 a7cd1cc193e0933 cf0373ecb54
Change-Id: I3652fbc50ce0c9