Insufficient RPC default timeout for pre_live_migration

[Loganathan Parthipan]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/61728

[Timofey Durakov (tdurakov)]

@jichenjc, are you working on this patch?

[jichenjc (jichenjc)]

Removed my self, thanks~

[lvmxh (shaohef)]

https://review.openstack.org/61728 was abandon on Dec 22, 2013.

It simply add a config option live_migration_rpc_timeout

Joe Gordon , prefers to fix the logic so we don't use a call that can potentially take so long to respond.

It should be async.

[Markus Zoeller (markus_z) (mzoeller)]

Solving an inconsistency: This bug report has an assignee and it looks
like this could result in a patch. Therefore I switch the status to
"In Progress".
Dear assignee, please provide a patch in the next 2 weeks. If you stop
working on this report, please remove yourself as assignee and switch
the status back. If you need assistance, reach out on the IRC channel
#openstack-nova or use the mailing list.

[Paul Carlton (paul-carlton2)]

This is still a live issue, HPE are carrying a patch for this in our product that I'd like to remove, will progress this issue.

[Paul Carlton (paul-carlton2)]

stgleb, if you are working on this then feel free to assign the bug back to you

[Paul Carlton (paul-carlton2)]

cancel that, apparently we should have dropped this patch

[Pushkar Umaranikar (pushkar-umaranikar)]

Solving inconsistency: Changing bug status from "In progress" to "Confirmed" as it has not assigned to anyone.

[Markus Zoeller (markus_z) (mzoeller)]

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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 0.0.10 release.