[
https://issues.apache.org/jira/browse/CLOUDSTACK-8771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711193#comment-14711193
]
ASF GitHub Bot commented on CLOUDSTACK-8771:
--------------------------------------------
GitHub user nitt10prashant opened a pull request:
https://github.com/apache/cloudstack/pull/742
[Automation]Volume migration between pools times out in ACS, but but the
migration completes on Xenserve
Ticket :CLOUDSTACK-8771
description:
Volume migration between pools times out in ACS, but the migration
completes on Xenserver
steps:
---------
test results
========
put storage in maintenance mode and start ha vm and check usage ... ===
TestName: test_migrate_volume_timeout | Status : SUCCESS ===
ok
----------------------------------------------------------------------
Ran 1 test in 250.958s
OK
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nitt10prashant/cloudstack migrate_volume
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/742.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #742
----
commit d7f1f4b0c0b95f127be8353854e8d3d1cb609fb6
Author: nitt10prashant <[email protected]>
Date: 2015-08-25T12:25:11Z
CLOUDSTACK-8771:[Automation]Volume migration between pools times out in
ACS, but the migration completes on Xenserver
Adding descriptions
----
> [Automation]Volume migration between pools times out in ACS, but the
> migration completes on Xenserver
> -----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8771
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8771
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: 4.5.1
> Reporter: prashant kumar mishra
> Assignee: prashant kumar mishra
> Fix For: 4.5.1
>
>
> Verification steps:
> 1. Created 2 primary storages (PS1 and PS2)
> 2. created a volume of 5 GB and attach to VM ( on PS1)
> 3. set the migratewait time to 60 sec
> 4. start the migration of the volume ( onto PS2)
> 5. The migration failed after 60 sec.
> Volume migration failed with timeout error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
