Skip to content
Snippets Groups Projects
  1. Mar 12, 2010
    • Iustin Pop's avatar
      Improve cluster verify with hypervisor errors · 0cf5e7f5
      Iustin Pop authored
      
      In case the hypervisor has issues on one node, currently
      backend.VerifyNode will exit via an exception (two exit paths possible,
      one via HypervisorError from hypervisor.Verify(), and one via RPCFail
      from GetInstanceList). This is bad as it invalidates all other checks of
      that node.
      
      This patch catches these two errors and allows the rest of the
      VerifyNode function to run. This leads to a more complete verify cluster
      run, for example now only real missing LVs are reported, not all of
      them.
      
      The cluster verify is not perfect as it will skip some tests even if it
      has data, but this will require a more complete rewrite (see issue 90).
      
      Also, the patch fixes and improves some error messages in cmdlib.
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      0cf5e7f5
  2. Mar 11, 2010
  3. Mar 10, 2010
  4. Mar 09, 2010
  5. Mar 08, 2010
Loading