1. 08 May, 2014 1 commit
  2. 14 Apr, 2014 1 commit
  3. 29 Nov, 2013 1 commit
  4. 30 Sep, 2013 1 commit
  5. 12 Sep, 2013 1 commit
  6. 25 Jul, 2013 1 commit
  7. 08 Mar, 2013 1 commit
  8. 10 Jan, 2013 1 commit
  9. 03 Dec, 2012 1 commit
  10. 05 Jul, 2012 1 commit
    • Iustin Pop's avatar
      hbal: return exit status 0 in case of early exit · 2a2e2610
      Iustin Pop authored
      This derives from an internal bug, but the story is consistent across
      both internal and external usage of hbal.
      
      Basically right now, hbal returns exit code 1 if requested to exit
      early, even if all jobs are successful. This is counter-intuitive due
      to two reasons:
      
      - hbal did what it was requested (exit early), so it shouldn't return error
      - there were no job failures, so there's nothing to "cleanup" or
        investigate on the Ganeti cluster, so again it shouldn't return
        error
      
      Therefore the new behaviour is as follows:
      
      - for cases where all jobs were successful, even if terminated early
        via SIGINT or via --limit, we exit with code 0
      - for cases where jobs have failed or there were other errors in
        running hbal, the exit code is 1
      - for cases were hbal is requested an immediate termination (SIGTERM),
        exit code is 2, denoting "unknown whether the Ganeti cluster is
        consistent or not"
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      2a2e2610
  11. 13 Mar, 2012 1 commit
  12. 27 Feb, 2012 1 commit
  13. 11 Oct, 2011 1 commit
  14. 30 Sep, 2011 1 commit
  15. 23 Sep, 2011 1 commit
  16. 19 Jul, 2011 1 commit
  17. 14 Jul, 2011 1 commit
  18. 17 Jun, 2011 1 commit
  19. 31 May, 2011 1 commit
  20. 19 Apr, 2011 1 commit
  21. 18 Mar, 2011 1 commit