yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  Insufficient RPC default timeout for pre_live_migration

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Pre_live_migration on destination node take a long time if the base
  image of the instance to be moved is not yet cached and large. The
  default RPC timeout of 60s is insufficient for this. This would result
  in a timeout error and migration will be aborted. A typical usecase is
  an instance spawned off a snapshot for the first time.

  However, changing the default timeout globally is not recommended
  since it's difficult to model the system behaviour changes that can be
  caused by this. In addition, we have seen that we need timeouts of
  over 1200s in certain scenarios and this is obviously unsuitable for a
  global timeout.

  It would be good to change the timeout just for the pre_live_migration
  RPC api and keep it configurable.

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