cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8602) MigrateVirtualMachineWithVolume leaves old chain data for volume
Date Wed, 01 Jul 2015 09:29:04 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609819#comment-14609819
] 

ASF GitHub Bot commented on CLOUDSTACK-8602:
--------------------------------------------

GitHub user likitha opened a pull request:

    https://github.com/apache/cloudstack/pull/548

    CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain dat…

    …a for volume.
    
    Update chain info of a volume after  migration.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8602

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/548.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 #548
    
----
commit fc33dc35645d52caf5cdbed112101df83104feab
Author: Likitha Shetty <likitha.shetty@citrix.com>
Date:   2015-04-17T18:33:26Z

    CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain data for volume.
    Update chain info of a volume after  migration.

----


> MigrateVirtualMachineWithVolume leaves old chain data for volume
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8602
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8602
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.6.0
>
>
> CS maintains chain info of every volume in DB, where chain info is the complete volume
path. When the volumes associated with a VM are migrated to different storage pool, their
chain info changes, but this information is not reflected in the DB.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message