I am having an issue with my Cloud Platform Storage. My hyper-visor is vmware and I have the storage added as vmfs.
Due to me getting some configuration settings wrong, which has caused issues with deploying my system VMs. So to resolve this, I am trying to put my primary storage in maintenance so my vms go into a stopped state so I can remove them. I was able to start the process, but it hasn't changed for the last hour or so. When I check the status I see:
PrepareForMaintenance
When I try to cancel maintenance mode I can see Storage Unreachable due to status: PrepareForMaintence.
Is there any way I can force this out of maintenance mode so I can kick of the rebuild for my system vms?
My management-server.log shows the following:
2013-02-19 09:11:24,170 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-7:job-14) Complete async job-14, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Resource [StoragePool:203] is unreachable: Primary storage with id 203 is not ready to complete migration, as the status is:PrepareForMaintenance com.cloud.utils.exception.CloudRuntimeException: Resource [StoragePool:203] is unreachable: Primary storage with id 203 is not ready to complete migration, as the status is:PrepareForMaintenance 2013-02-19 09:20:02,955 DEBUG
Ideally I would need to take a deeper look at the logs and/or db before making recommendations.
The following DB update should put the storage back in the desired state: --- update storage_pool set status='Up' where id=<storage_pool_id>; //if you wanted to set it to Up or update storage_pool set status='Removed' where id=<storage_pool_id>; //if you wanted to mark it as removed ---
But note, without knowing exactly why this operation is stuck/failing and fixing that, we'd potentially end up in a similar situation.
I have solve my problem like PrepareForMaintenance by changing in the db 1. stop the management server 2. update storage_pool set status='Maintenance' where id=<storage_pool_id>; 3. start the management server 4. cancel the Maintenance mode in the primary storage after login to the cloudstack webGui.
Good that it worked for you but a couple of points, a. this procedure doesn't address the underlying issue that is actually preventing the operation to complete successfully. b. this is not the recommended procedure, one may not be able to foresee the side affects.
