You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Daan Hoogland (JIRA)" <ji...@apache.org> on 2015/05/01 13:44:06 UTC

[jira] [Resolved] (CLOUDSTACK-8316) VolumeOrchestrator checks StorageHAMigrationEnabled setting where it should not

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daan Hoogland resolved CLOUDSTACK-8316.
---------------------------------------
    Resolution: Fixed

cherrypicked solution from master

> VolumeOrchestrator checks StorageHAMigrationEnabled setting where it should not
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8316
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8316
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Volumes
>    Affects Versions: 4.4.2
>            Reporter: Remi Bergsma
>            Assignee: Daan Hoogland
>             Fix For: 4.4.3
>
>
> Scenario:
> enable.ha.storage.migration = false
> Attach a volume to a disk that is on another storage pool than the vm you are attaching to.
> Error: Cannot migrate volumes. Volume Migration is disabled
> Cause:
> file: engine/orchestration/src/org/apache/cloudstack/engine/orchestration/VolumeOrchestrator.java
> ....
> if (StorageHAMigrationEnabled.value()) {
> ....
> It checks the HA setting, but this is not an HA event!
> Proposed solution:
> Option A: add setting: enable.storage.migration and check that instead
> Option B: remove the check altogether as it does not provide much value



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