On Mon, May 18, 2015 at 02:46:49PM +0200, 'Klaus Aehlig' via ganeti-devel wrote:
This test verifies a global limit on the number of jobs running. This
requires knowledge of all jobs submitted between the addition of the
filter and the submission of our last test job. While we send these
commands directly one after the other, this still takes a second or
two, thus giving the watcher slightly less than a 1% change of
interfering. Avoid this by pausing the watcher during this test.
Signed-off-by: Klaus Aehlig <[email protected]>
---
qa/qa_filters.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/qa/qa_filters.py b/qa/qa_filters.py
index 0de7594..3eaa7e7 100644
--- a/qa/qa_filters.py
+++ b/qa/qa_filters.py
@@ -332,6 +332,7 @@ def TestFilterRateLimit():
# (simply set it to the default).
AssertCommand(["gnt-cluster", "modify", "--max-running-jobs=20"])
AssertCommand(["gnt-cluster", "modify", "--max-tracked-jobs=25"])
+ AssertCommand(["gnt-cluster", "watcher", "pause", "600"])
# Add a filter that rejects all new jobs.
uuid = stdout_of([
@@ -362,6 +363,7 @@ def TestFilterRateLimit():
# Clean up.
AssertCommand(["gnt-filter", "delete", uuid])
KillWaitJobs([jid1, jid2, jid3])
+ AssertCommand(["gnt-cluster", "watcher", "continue"])
def TestAdHocReasonRateLimit():
--
2.2.0.rc0.207.ga3a616c
LGTM
