yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1215068

Title:
  Error messages in compute.api when setting vm_state to error don't
  provide context for debugging

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When certain actions in compute.manager raise an exception this sets
  the vm_state to error and prints out an error message with a line
  like:

  LOG.error(_('%s. Setting instance vm_state to ERROR'),
                     error, instance=instance)

  However, this doesn't really help for debugging what is causing the
  failure. It will tell you what type of exception it is but often times
  this really isn't specific enough to debug the failure. See:

  http://logs.openstack.org/63/42063/1/gate/gate-tempest-devstack-vm-
  testr-full/fa32f42/logs/screen-n-cpu.txt.gz#_2013-08-16_13_59_20_999

  Which has an error message:

  2013-08-16 13:59:20.999 ERROR nova.compute.manager [req-
  9f1776c8-f12a-4859-b15b-5e1db034bca6
  ServerActionsTestJSON1899714206-user
  ServerActionsTestJSON1152578709-tenant] [instance:
  ed3c7212-f4b6-4365-91b8-bddddc9e1a60] int() argument must be a string
  or a number, not 'NoneType'. Setting instance vm_state to ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1215068/+subscriptions