[
https://issues.apache.org/jira/browse/CLOUDSTACK-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-6918.
-----------------------------------
Resolution: Fixed
> CancelStorageMaintenance: Not all vms get restarted as a part of canceling
> maintenance mode
> --------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6918
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6918
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.4.0
> Reporter: Alena Prokharchyk
> Assignee: edison su
> Priority: Critical
> Fix For: 4.5.0
>
>
> Steps to reproduce:
> 1) Have one storage pool in a zone.
> 2) Start regular user vm and the VR
> 3) Enable storage maintenance. All vms get stopped automatically, and records
> for them are added to storage_pool_work table with stopped_for_maintenance
> flag set to 1.
> 4) Cancel storage maintenance. All the vms that were stopped as a part of
> maintenance, should be restarted now. But it doesn't happen as
> StoragePoolAutomationImpl.java, cancelMaintain method when loop through
> pendingWorks, the result is returned right after the first pendingWork is
> completed successfully.
> for (StoragePoolWorkVO work : pendingWork) {
--
This message was sent by Atlassian JIRA
(v6.2#6252)
