| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
With the patch [1] got merged, keystone has the ablity to cache
catalog/v3 catalog, and will invalidate the cache when there is any
changes about the catalog, i.e. add_endpoint_to_project,
remove_endpoint_from_project. But the testcase was missed there, this
means there is no testcase covered in keystone even the API in the
Manager layer was not defined correctly [2].
The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project`
and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed.
[1] https://review.openstack.org/#/c/215212/
[2] https://review.openstack.org/#/c/243951/
** Affects: keystone
Importance: Undecided
Assignee: Dave Chen (wei-d-chen)
Status: New
** Description changed:
With the patch [1] got merged, keystone has the ablity to cache
catalog/v3 catalog, and will invalidate the cache when there is any
changes about the catalog, i.e. add_endpoint_to_project,
remove_endpoint_from_project. But the testcase was missed there, this
means there is no testcase covered in keystone even the API in the
Manager layer was not defined correctly [2].
-
The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project`
- and `remove_endpoint_group_from_project` as it is, this is beacuse these two should be impact the endpoints but in theory but it's not in practice. So, add some testcase to test it impact catalog is impossible. There should be anthor bug filed and will add the testcase when that bug was fixed.
+ and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed.
[1] https://review.openstack.org/#/c/215212/
[2] https://review.openstack.org/#/c/243951/
** Changed in: keystone
Assignee: (unassigned) => Dave Chen (wei-d-chen)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1516468
Title:
miss the testcase for caching to get_catalog/get_v3_catalog in
endpoint filter extension
Status in OpenStack Identity (keystone):
New
Bug description:
With the patch [1] got merged, keystone has the ablity to cache
catalog/v3 catalog, and will invalidate the cache when there is any
changes about the catalog, i.e. add_endpoint_to_project,
remove_endpoint_from_project. But the testcase was missed there, this
means there is no testcase covered in keystone even the API in the
Manager layer was not defined correctly [2].
The bug will focus on `add_endpoint_to_project` and `remove_endpoint_from_project` and leave `add_endpoint_group_to_project`
and `remove_endpoint_group_from_project` as it is, this is beacuse these two API should impact the endpoints in theory but it's not in practice. So, add some testcase to test its impact on catalog is impossible. There should be anothor bug filed and testcase will be added when that bug was fixed.
[1] https://review.openstack.org/#/c/215212/
[2] https://review.openstack.org/#/c/243951/
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1516468/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
