[
https://issues.apache.org/jira/browse/CLOUDSTACK-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105396#comment-15105396
]
ASF subversion and git services commented on CLOUDSTACK-9231:
-------------------------------------------------------------
Commit f0fca609937885006df5c5e59ae6504d0559f99d in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0fca60 ]
Merge pull request #1336 from nitin-maharana/CloudStack-Nitin19_4.7
CLOUDSTACK-9231: Root volume migration from one primary to another primary
storage within the same cluster is failingEXPECTED 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.
* pr/1336:
CLOUDSTACK-9231: Root volume migration from one primary to another primary
storage within the same cluster is failing
Signed-off-by: Remi Bergsma <[email protected]>
> 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)
