[
https://issues.apache.org/jira/browse/CLOUDSTACK-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624850#comment-13624850
]
Mice Xia commented on CLOUDSTACK-1698:
--------------------------------------
[root cause]
caused by storage related refactoring, attachVolumeToVM was moved to
VolumeManagerImpl.java, but vm snapshots checking was not merged.
> VMSnapshot Limitations Violation: Detaching/Attaching VM volume is not
> allowed if there are VM Snapshots- Currently it is allowed
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1698
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1698
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Chandan Purushothama
> Priority: Critical
> Fix For: 4.2.0
>
>
> ================
> Steps to Reproduce:
> ================
> Case 1:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" type VM snapshot for a VM
> which has 1 datadisk.
> 2. Detach the existing data disk.
> Case 2:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" for a VM which has 1 datadisk.
> 2. Attach a new data disk.
> ======================================
> Expected Results as per FS mentioned Limitations:
> ======================================
> Case 1 and Case 2 should result in rejection of the detacj/attach operations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
