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, 26 Aug 2015 09:45:46 GMT

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

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

Github user bhaisaab commented on the pull request:

    https://github.com/apache/cloudstack/pull/548#issuecomment-134926126
  
    LGTM


> 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: Suresh Kumar Anaparti
>             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