1. 10 Jul, 2015 1 commit
  2. 08 Jul, 2015 4 commits
  3. 06 Jul, 2015 1 commit
    • Helga Velroyen's avatar
      QA: reload rapi cert after renew crypto · 2e795f2c
      Helga Velroyen authored
      When running the QA, we copy the rapi certficate to the
      machine which steers the QA to use it later in the QA
      for testing RAPI calls. However, before we get to that
      part of the QA, the rapi certificate is replaced when
      'gnt-renew crypto' is called.
      
      This patch makes sure that the new rapi certificate is
      copied to the steering machine so that later RAPI calls
      do not fail. It remains mysterious how this worked before.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      2e795f2c
  4. 27 May, 2015 5 commits
  5. 18 May, 2015 4 commits
    • Klaus Aehlig's avatar
      Increase waiting time to avoid races · cb50990b
      Klaus Aehlig authored
      In tests, give Ganeti enough time to actually start up jobs before
      asserting that they succeed. While normally forking and executing
      a job is finished in less than a second in some circumstances it
      can take longer; so give enough time to avoid flaky tests.
      
      While there, also pause the watcher, so that it doesn't submit
      jobs inbetween that cause our 0.01 second delay jobs to take
      longer while waiting for locks taken by the watcher's jobs.
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      cb50990b
    • Klaus Aehlig's avatar
      Avoid watcher interaction in TestFilterRateLimit · 853a4fb2
      Klaus Aehlig authored
      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: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      853a4fb2
    • Klaus Aehlig's avatar
      Avoid races in TestAdHocReasonRateLimit · b581773d
      Klaus Aehlig authored
      The test submits 3 jobs in an environment rate-limited to two, and verifies
      that the first 2 jobs are running whereas the third one remains queued. However,
      it takes for Ganeti some time to get a submitted job to actually being confirmed
      waiting (in some circumstances over a second). So wait a bit longer to avoid
      losing the race. While there, increase the time of the delay jobs to avoid
      them finishing during that test in an extremely slowly running QA. (Note that
      the jobs are killed forcefully at the end of the test, so that time is never
      really waited for.)
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      b581773d
    • Klaus Aehlig's avatar
      Avoid races in TestFilterRateLimit · 43b45518
      Klaus Aehlig authored
      The test submits 3 jobs in an environment rate-limited to two, and verifies
      that the first 2 jobs are running whereas the third one remains queued. However,
      it takes for Ganeti some time to get a submitted job to actually being confirmed
      waiting (in some circumstances over a second). So wait a bit longer to avoid
      losing the race. While there, increase the time of the delay jobs to avoid
      them finishing during that test in an extremely slowly running QA. (Note that
      the jobs are killed forcefully at the end of the test, so that time is never
      really waited for.)
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      43b45518
  6. 30 Apr, 2015 1 commit
    • Helga Velroyen's avatar
      QA: use relative path to script location for burnin · ff3f66bd
      Helga Velroyen authored
      The QA had the annoying bug that if you run burnin, it
      would try to upload the burnin file from the tools/
      directory relative to the working directory and not
      the location of the qa_cluster.py script. If you
      accidentally start the QA from a differen directory
      than qa/ it would run for a long while and only
      crash when it comes to the burnin part. This patch
      fixes the glitch by taking the location of the
      QA scripts as a reference rather than the working
      directory.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      ff3f66bd
  7. 19 Mar, 2015 4 commits
  8. 18 Mar, 2015 5 commits
  9. 02 Mar, 2015 2 commits
  10. 23 Jan, 2015 1 commit
  11. 19 Jan, 2015 1 commit
  12. 09 Jan, 2015 2 commits
    • Hrvoje Ribicic's avatar
      Rename lxc_tty to num_ttys · f15c61c4
      Hrvoje Ribicic authored
      As noted in the previous commit, the lxc_ prefix is bad and it's good
      to be rid of it, and we can take advantage of this change to rename the
      variable.
      Its previous name was meant to reflect the lxc config option being set
      (lxc.tty), but we should use a more descriptive name.
      Signed-off-by: default avatarHrvoje Ribicic <riba@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      f15c61c4
    • Hrvoje Ribicic's avatar
      Remove the rapi-workload test suite · c0065e0f
      Hrvoje Ribicic authored
      The rapi-workload test suite was introduced in 2.10 to try and provide
      a chunk of workload which could be used to detect regressions in the
      RAPI functionality and format. It served its purpose, helping detect a
      few important regressions in time, but with the assistance of manual
      tools which were never automated. Automating them proved difficult, and
      probably infeasible.
      
      The flaws in the QA that caused the regressions were removed over time,
      and with 2.13 around the corner, it's time to shoot this horse. This
      patch removes the file, and a sole mention of it in the Makefile.
      Signed-off-by: default avatarHrvoje Ribicic <riba@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      c0065e0f
  13. 07 Jan, 2015 2 commits
  14. 28 Nov, 2014 1 commit
  15. 13 Nov, 2014 2 commits
  16. 04 Nov, 2014 1 commit
  17. 21 Oct, 2014 2 commits
  18. 17 Oct, 2014 1 commit