cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alena Prokharchyk <Alena.Prokharc...@citrix.com>
Subject Re: State of my VM Storage Volumes remains "Allocated". Is this correct?
Date Fri, 13 Jul 2012 23:12:03 GMT
You need to figure out why host went into Alert state - check the
management server, the part when the host is being connected.

Also if you deleted volumes + storage SR from the backend, the Storage
pool has to be removed from the cluster on cloudStack.

-Alena.

On 7/13/12 4:06 PM, "Evan Miller" <Evan.Miller@citrix.com> wrote:

>I deleted each of the storage volumes. No storage volumes are left.
>I re-ran the cleanup script.
>I deleted the XenServer Host from the API.
>I re-added the XenServer Host from the API.
>And, the XenServer Host is not Up but it is back in the Alert State.
>
>How do I change the State from Alert to something more appropriate?
>
>Regards,
>Evan
>
>
>
>-----Original Message-----
>From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]
>Sent: Friday, July 13, 2012 3:38 PM
>To: cloudstack-users@incubator.apache.org
>Subject: Re: State of my VM Storage Volumes remains "Allocated". Is this
>correct?
>
>On 7/13/12 3:16 PM, "Evan Miller" <Evan.Miller@citrix.com> wrote:
>
>>Running CloudStack Management Server:
>>  v3.0.2.1
>>On:
>>  [root@cumulus management]# uname -a
>>  Linux cumulus.eng.citrite.net 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6
>>19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
>>  [root@cumulus management]#
>>Hypervisor :
>>  XenServer v6.02
>> 
>>Hi:
>> 
>>I tried running the API Script, createVolume, to change the state of
>>the Volumes used for my VMs from ³Allocated² to ³Created². Please see
>>attached GUI snapshot.
>>Is it correct?
>> 
>>Here is a api log snippet of my two attempts:
>> 
>>2012-07-13 13:46:06,703 INFO  [cloud.api.ApiServer]
>>(catalina-exec-7:null) (userId=2 accountId=2 sessionId=null)
>>10.217.5.18
>>-- GET
>>apikey=8tX2yyZ0FSBY-m6SESTRvT8VMDpRwzWzBMXbQfgxppsVZfeodoi93cICbkZme8QR
>>RB1
>>jBSRg-0FSMDwrtERWbA&command=createVolume&name=Medium_Disk&diskofferingi
>>d=4
>>5bb2a51-0c05-4f0e-8e35-6cdb325b7982&zoneid=13d183a8-58ce-4692-9d53-4e9a
>>619 93b0a&response=json&signature=2v1Y%2FpEBRBzSW45ma6HNld5qtQ0%3D
>> 200 { "createvolumeresponse" :
>>{"id":"30d96393-3cb5-419d-adfc-8dfefd2c8573","jobid":"acd55551-73bc-4f5
>>5-8
>>966-8c3db5da1fdd"} }
>> 
>>2012-07-13 13:49:08,375 INFO  [cloud.api.ApiServer]
>>(catalina-exec-9:null) (userId=2 accountId=2 sessionId=null)
>>10.217.5.18
>>-- GET
>>apikey=8tX2yyZ0FSBY-m6SESTRvT8VMDpRwzWzBMXbQfgxppsVZfeodoi93cICbkZme8QR
>>RB1
>>jBSRg-0FSMDwrtERWbA&command=createVolume&name=Small_Disk&diskofferingid
>>=23
>>5cbe90-b6cd-4976-9d77-3b59c3cda681&zoneid=13d183a8-58ce-4692-9d53-4e9a6
>>199 3b0a&response=json&signature=XXzwhji8t4ik408QzORGiZMvFKI%3D
>> 200 { "createvolumeresponse" :
>>{"id":"4b20c7b1-9fea-47f8-adfc-d08f2fc1f39f","jobid":"8df8129a-30fb-48e
>>c-b
>>0f6-d62c163088c4"} }
>> 
>>I am seeing this in catalina.out:
>> 
>>WARN  [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-82:) Cleanup
>>failed due to ModifyStoragePoolCommand add XenAPIException:Can not see
>>storage pool: c9c0319f-33f0-3494-9ada-4d7a2f1dafd4 from on
>>host:09b3515e-447e-406f-869a-239386d5fe90
>> host:09b3515e-447e-406f-869a-239386d5fe90 pool:
>>10.217.5.192/home/export/primary
>> 
>>WARN  [cloud.vm.VirtualMachineManagerImpl] (AgentTaskPool-2:) Cleanup
>>failed due to ModifyStoragePoolCommand add XenAPIException:Can not see
>>storage pool: c9c0319f-33f0-3494-9ada-4d7a2f1dafd4 from on
>>host:09b3515e-447e-406f-869a-239386d5fe90
>> host:09b3515e-447e-406f-869a-239386d5fe90 pool:
>>10.217.5.192/home/export/primary
>> 
>>Are these warnings related to the storage volume issue I am reporting
>>in this email?
>> 
>>It probably is related to the other issue that I previously submitted
>>today about failing to create a new instance.
>> 
>>Regards,
>> 
>>Evan Miller
>> 
>>Citrix Systems. Inc.
>>Desktop and Cloud Engineering Infrastructure
>>4988 Great America Parkway
>>Santa Clara, CA 95054
>> 
>>
>>
>
>
>
>Evan,
>
>The error shows that the Storage pool from your setup isn't set on the
>backend (can't find SR message proves it) If you ran cleanup script
>provided by me before (which destroys vms, volumes, src); then you have
>to re-add the storage pool from cloudStack api once again - it will
>re-create the SR on the backend.
>
>-Alena.
>
>


Mime
View raw message