Filtering on resource name can be accomplished by using the db
filters instead of using a filter method. Furthermore, using a
custom filter breaks certain assumptions made by other parts of
the codebase, which lead to pagination being broken.
Specifically, custom filter for resource name is applied only
after other filtering is finished. As a result, we try to find
result from only 1 event and this event belongs to whole
stack and thus its resource_name is equal to the stack name.
This returns an event not found error instead of returning
the first event assosciated with the resource name.
Change-Id: Ie7d28ffb88a79d6e0f516f0db385be2eed59f7f0
Closes-Bug: #1502751
(cherry picked from commit 6322ff6fceabdfa226e5359328bde292d189e703)
Reviewed: https:/ /review. openstack. org/231804 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=7e911cec083 e98f344bfcfeb7e 2e843ce2330d5d
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit 7e911cec083e98f 344bfcfeb7e2e84 3ce2330d5d
Author: Pratik Mallya <email address hidden>
Date: Mon Oct 5 00:34:12 2015 -0500
Correctly filter events on resource name
Filtering on resource name can be accomplished by using the db
filters instead of using a filter method. Furthermore, using a
custom filter breaks certain assumptions made by other parts of
the codebase, which lead to pagination being broken.
Specifically, custom filter for resource name is applied only
after other filtering is finished. As a result, we try to find
result from only 1 event and this event belongs to whole
stack and thus its resource_name is equal to the stack name.
This returns an event not found error instead of returning
the first event assosciated with the resource name.
Change-Id: Ie7d28ffb88a79d 6e0f516f0db385b e2eed59f7f0 226e5359328bde2 92d189e703)
Closes-Bug: #1502751
(cherry picked from commit 6322ff6fceabdfa