← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1301696] [NEW] automatic confirm resize should not set migration to error when encounter problem

 

Public bug reported:

function in compute/manager.py _poll_unconfirmed_resizes will translate the migrate status from finished to error 
whenever it find a problem , consider following case

1) _poll_unconfirmed_resizes running, it found several migrations to be confirmed
2) user want to delete an instance ,its task state will be changed to DELETING by 
3) _poll_unconfirmed_resized will found the task state is not None, it will make the migration error status
4) following code in _delete
if instance.vm_state == vm_states.RESIZED:
                self._confirm_resize_on_deleting(context, instance)
will fail because migration status already updated

so we should not set the migration status to 'error' , let it be and
report warning message is enough

** Affects: nova
     Importance: Undecided
     Assignee: jichencom (jichenjc)
         Status: New


** Tags: compute

-- 
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/1301696

Title:
  automatic confirm resize should not set migration to error when
  encounter problem

Status in OpenStack Compute (Nova):
  New

Bug description:
  function in compute/manager.py _poll_unconfirmed_resizes will translate the migrate status from finished to error 
  whenever it find a problem , consider following case

  1) _poll_unconfirmed_resizes running, it found several migrations to be confirmed
  2) user want to delete an instance ,its task state will be changed to DELETING by 
  3) _poll_unconfirmed_resized will found the task state is not None, it will make the migration error status
  4) following code in _delete
  if instance.vm_state == vm_states.RESIZED:
                  self._confirm_resize_on_deleting(context, instance)
  will fail because migration status already updated

  so we should not set the migration status to 'error' , let it be and
  report warning message is enough

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


Follow ups

References