1. 03 Dec, 2012 1 commit
  2. 30 Nov, 2012 1 commit
  3. 29 Nov, 2012 1 commit
  4. 27 Nov, 2012 7 commits
  5. 23 Nov, 2012 1 commit
  6. 22 Nov, 2012 1 commit
  7. 21 Nov, 2012 5 commits
  8. 20 Nov, 2012 16 commits
  9. 19 Nov, 2012 1 commit
  10. 12 Nov, 2012 1 commit
    • Iustin Pop's avatar
      Improve error message when migration status fail · 4041a4e3
      Iustin Pop authored
      Commit 6a1434d7
      
       (“Make migration RPC non-blocking”) changed the API
      for reporting migration status, but has a small cosmetic bug: if the
      migration status if failure, but the RPC itself to get the status
      didn't fail, it shows the following error message:
      
        Could not migrate instance instance2: None
      
      since it always uses result.fail_msg, irrespective of which part of
      the if condition failed.
      
      This patch simply updates the msg if not already set, leading to:
      
        Could not migrate instance instance2: hypervisor returned failure
      
      Proper error display can be done once the migration status objects can
      return failure information as well, beside status.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      4041a4e3
  11. 02 Nov, 2012 1 commit
  12. 01 Nov, 2012 1 commit
  13. 30 Oct, 2012 3 commits