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 <nitin.mahar...@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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to