yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

If we call confirm_resize() that sets migration.status to 'confirming'
and sends an  RPC cast to the compute node.

If there's a glitch and that cast is received but never processed,
there's no way to confirm the resize since it only looks for migrations
with a status of "finished".  It looks like it should be safe as-is to
allow calling confirm_resize on a migration in the "confirming" state
since it's already synchronized on the instance.

A similar problem holds for an interrupted revert_resize(), but in that
case there's no synchronization currently.  Not sure if that's a problem
or not.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  unable to re-issue confirm/revert of resize

Status in OpenStack Compute (nova):
  New

Bug description:
  If we call confirm_resize() that sets migration.status to 'confirming'
  and sends an  RPC cast to the compute node.

  If there's a glitch and that cast is received but never processed,
  there's no way to confirm the resize since it only looks for
  migrations with a status of "finished".  It looks like it should be
  safe as-is to allow calling confirm_resize on a migration in the
  "confirming" state since it's already synchronized on the instance.

  A similar problem holds for an interrupted revert_resize(), but in
  that case there's no synchronization currently.  Not sure if that's a
  problem or not.

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