project_id filter doesn't work when listing limits with more than one filters

[wangxiyuan]

when a non-admin list limits with a filter ("resource_name", "region_id", "service_id"), all project's related limits will return.

Because when a non-admin list limits, keystone will add "project_id" filter internal and then query db.
But the "project_id" is ignored in db query.

This can be fixed by adding the project_id filter action back in db query.

[wangxiyuan (wangxiyuan)]

This bug is introduced when refactor the limit db schema, really sorry about it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/581177

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/581177
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4cdb4a0b72701f400647cd5899d50cb7e9615cfd
Submitter: Zuul
Branch: master

commit 4cdb4a0b72701f400647cd5899d50cb7e9615cfd
Author: wangxiyuan <email address hidden>
Date: Tue Jul 10 10:55:13 2018 +0800

    Filter project_id for list limits

    When list limits, if more than one filter is provided and
    "project_id" is contained, the limits should be filtered
    with "project_id" as well.

    Closes-bug: #1780896
    Change-Id: I7c231130358ab8d7b0b2f507c52d34366ca0060a

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/keystone 14.0.0.0rc1 release candidate.