[ https://issues.apache.org/jira/browse/CLOUDSTACK-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146205#comment-14146205 ]
ASF subversion and git services commented on CLOUDSTACK-7534: ------------------------------------------------------------- Commit c55bc0b2d11be4820a24af426e23da3db54a0cb1 in cloudstack's branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c55bc0b ] CLOUDSTACK-7534: ResetVM for VM with attached datadisk fails when enable.ha.storage.migration is false Separate global config to enable/disable Storage Migration during normal deployment Introduced a configuration parameter named enable.storage.migration > ResetVM for VM with attached datadisk fails when enable.ha.storage.migration > is false > ------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-7534 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7534 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.5.0 > Reporter: Harikrishna Patnala > Assignee: Harikrishna Patnala > Fix For: 4.5.0 > > > ResetVM for a VM having a attached datadisk fails if, > 1. there are 2 or more storage pools in the cluster > 2. enable.ha.storage.migration is set to false > 3. allocator has chosen a different pool for the datadisk than where it > currently exists and migration from one pool to another failed because > enable.ha.storage.migration set to false. > The issue is currently "enable.ha.storage.migration" applies to both normal > and HA deployment. We should have another parameter which is specific to > normal deployments (say enable.storage.migration) so that during migration > check we can clearly differentiate normal and HA deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)