Change I1aa3ca6cc70cef65d24dec1e7db9491c9b73f7ab in Queens,
which was backported through to Newton, introduced a regression
when listing deleted servers with a marker because it assumes
that if BuildRequestList.get_by_filters does not raise
MarkerNotFound that the marker was found among the build requests
and does not account for that get_by_filters method short-circuiting
if filtering servers with deleted/cleaned/limit=0. The API code
then nulls out the marker which means you'll continue to get the
marker instance back in the results even though you shouldn't,
and that can cause an infinite loop in some client-side tooling like
nova's CLI:
nova list --deleted --limit -1
This adds a functional recreate test for the regression which will
be updated when the bug is fixed.
Reviewed: https:/ /review. opendev. org/690428 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=45c2752f2ce 08b314012eff044 b01aa7d626b43d
Committed: https:/
Submitter: Zuul
Branch: master
commit 45c2752f2ce08b3 14012eff044b01a a7d626b43d
Author: Matt Riedemann <email address hidden>
Date: Tue Oct 22 17:53:20 2019 -0400
Add functional regression test for bug 1849409
Change I1aa3ca6cc70cef 65d24dec1e7db94 91c9b73f7ab in Queens, t.get_by_ filters does not raise cleaned/ limit=0. The API code
which was backported through to Newton, introduced a regression
when listing deleted servers with a marker because it assumes
that if BuildRequestLis
MarkerNotFound that the marker was found among the build requests
and does not account for that get_by_filters method short-circuiting
if filtering servers with deleted/
then nulls out the marker which means you'll continue to get the
marker instance back in the results even though you shouldn't,
and that can cause an infinite loop in some client-side tooling like
nova's CLI:
nova list --deleted --limit -1
This adds a functional recreate test for the regression which will
be updated when the bug is fixed.
Change-Id: I324193129acb6a c739133c7e76920 762a8987a84
Related-Bug: #1849409