1. 20 Nov, 2012 14 commits
  2. 19 Nov, 2012 1 commit
  3. 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
  4. 02 Nov, 2012 1 commit
  5. 01 Nov, 2012 1 commit
  6. 30 Oct, 2012 3 commits
  7. 26 Oct, 2012 1 commit
  8. 19 Oct, 2012 2 commits
    • Iustin Pop's avatar
      Update blockdev's "info" at instance rename · 48e175a2
      Iustin Pop authored
      
      
      Currently, we set "info" metadata on block devices at device creation
      time, but we never update it, leading to stale data in case of
      instance renames. This would not be a big problem in case of regular
      renames (assuming this is a rare operation), but importing instances
      into the cluster via the import/export feature usually is done with a
      rename; this means that all imported instances have wrong information
      in their block devices.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      48e175a2
    • Iustin Pop's avatar
      Fix disk adoption interaction with ipolicy checks · ba147ff8
      Iustin Pop authored
      
      
      In Ganeti 2.6, disk adoption is broken due to the ipolicy checks being
      done before we read volume size from remote nodes. We fix this by
      simply moving these checks to after the disk adoption code which
      updates the disk size; it's not that nice that we fail a (almost)
      config-level check after we've reserved the LVs, etc., but we need to
      do so in order to validate the ipolicy correctly.
      
      Tested:
      
      - normal instance creation
      - creation via adoption with good size (pass)
      - creation via adoption with wrong LV size (fail as expected)
      - QA in progress
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      ba147ff8
  9. 17 Oct, 2012 1 commit
  10. 11 Oct, 2012 2 commits
  11. 05 Oct, 2012 4 commits
  12. 04 Oct, 2012 1 commit
  13. 03 Oct, 2012 4 commits
  14. 27 Sep, 2012 3 commits
  15. 24 Sep, 2012 1 commit