Reviewed: https://review.openstack.org/499429
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=bf36f8c934b49310103a1b1831c9f7c8a0d14adf
Submitter: Jenkins
Branch: master
commit bf36f8c934b49310103a1b1831c9f7c8a0d14adf
Author: Kevin Benton <ke...@benton.pub>
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
Change-Id: I3652fbc50ce0c9a7cd1cc193e0933cf0373ecb54
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1714378
Title:
Pecan is missing logic to add project_id to fields when tenant_id is
specified
Status in neutron:
Fix Released
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://github.com/openstack/neutron/blob/8d2c1bd88b14eefbea74c72f384cb9952e7ee62e/neutron/api/v2/base.py#L96
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714378/+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
