You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/13 18:05:39 UTC
[jira] [Commented] (CLOUDSTACK-9231) Root volume migration from one
primary to another primary storage within the same cluster is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096551#comment-15096551 ]
ASF GitHub Bot commented on CLOUDSTACK-9231:
--------------------------------------------
GitHub user nitin-maharana opened a pull request:
https://github.com/apache/cloudstack/pull/1336
CLOUDSTACK-9231: Root volume migration from one primary to another primary storage within the same cluster is failing
EXPECTED BEHAVIOUR:
====================
Root Volume migration within cluster should work.
ACTUAL BEHAVIOUR:
==================
Root volume migration within cluster failed.
This situation arises when there are two management server accessing the same database.
When the migration request comes the command is forwarded from one management server to another because the host is owned by the second management server. So, serialisation of map from one to another fails.
Fix:
===
This is fixed by converting the maps to lists.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nitin-maharana/CloudStack CloudStack-Nitin19_4.7
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1336.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 #1336
----
commit 40e3dfc61702a5c6c9b5710b525e1db43cd2920e
Author: Nitin Kumar Maharana <ni...@gmail.com>
Date: 2015-10-30T19:23:53Z
CLOUDSTACK-9231: Root volume migration from one primary to another primary storage within the same cluster is failing
This situation arises when there are two management server accessing the same database.
When the migration request comes the command is forwarded from one management server to another because
the host is owned by the second management server. So, serialization of map from one to another fails.
This is fixed by converting the maps to lists.
----
> Root volume migration from one primary to another primary storage within the same cluster is failing
> ----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9231
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Nitin Kumar Maharana
>
> EXPECTED BEHAVIOR
> ===================
> Root Volume migration within cluster should work.
> ACTUAL BEHAVIOR
> ================
> Root volume migration within cluster failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)