On 6/13/12 1:38 PM, "Lu Heng" <[email protected]> wrote:
>Hi > >And btw, I didn't see the maintainace botton for the 3 shared storage, > I only see take snapshoot, snapshoot setting, that's it. > >On Wed, Jun 13, 2012 at 10:35 PM, Lu Heng <[email protected]> wrote: >> Hi >> >> See my reply >> >> On Wed, Jun 13, 2012 at 10:30 PM, Alena Prokharchyk >> <[email protected]> wrote: >>> On 6/13/12 1:24 PM, "Lu Heng" <[email protected]> wrote: >>> >>>>Hi >>>> >>>>I find the reason, three vm are in state of "Expunging" for 3 hours >>>>now, no process is being made, anyone has idea what should I do about >>>>these VMs？ >>> >>> >>> What is expunge.interval in the setup? If the vms stuck in Expunging >>>state >>> with null Removed field, it indicates some problem happening during the >>> expunge. I suspect it's related with the fact you removed the storage >>>from >>> the xen. >>> >> Vise verse, the situation is, the VM in the expunging state for 3 >> hours, and I find no way to delete them, so I try to delete the >> storage. So you deleted the VHDs per each volume, not the storage itself, please confirm. And we should never do it as there is no volume sync, so if the volume is removed on the backend, cloudStack has no idea it has happened. The original issue is - vm got stuck in Expunging state. We have to figure out this one first. Please send the logs starting from the time the Destroy command was executed for the Vm. And mention the vm name. -Alena. >> >> What should I do to fix this now? >>> >>> >>>> >>>>Another question is, I didn't see the delete botton with shared >>>>storage, so I delete it from the xencenter, but after that I still see >>>>the deleted storage exists in the UI, what suppose to be done? >>> >>> >>> Delete storage pool consists of 2 steps: >>> >>> * enable maintenance for the shared storage >>> * after the maintenance is completed, the Delete button will be >>>presented >>> to the admin; and the storage can be removed. >>> >>> You are not supposed to delete primary storage on the backend; >>>cloudStack >>> has no idea if you do things like that, and it expects primary storage >>>to >>> be functioning. >>> >>> So when vm expunge happens, we see that the storage is in UP state, and >>> try to send the destroy volume command to the Xen host. But the command >>> fails there because there is no such primary storage exist. >>> >>> Let me know if its your case. >>> >>> -Alena. >>> >>> >>>> >>>>On Wed, Jun 13, 2012 at 10:08 PM, Alena Prokharchyk >>>><[email protected]> wrote: >>>>> On 6/13/12 12:55 PM, "Lu Heng" <[email protected]> wrote: >>>>> >>>>>>Hi >>>>>> >>>>>>Update: >>>>>> >>>>>>The zone has been stoped. all VM has been destoryed , the route vm >>>>>>has >>>>>>been stoped(no option for destory). >>>>>> >>>>>>Still get error fail to delete network. >>>>> >>>>> >>>>> Can you send management server log file for debugging. >>>>> >>>>> Thanks, >>>>> Alena. >>>>> >>>>> >>>>>> >>>>>> >>>>>>On Wed, Jun 13, 2012 at 7:23 PM, Alena Prokharchyk >>>>>><[email protected]> wrote: >>>>>>> On 6/13/12 10:18 AM, "Tamas Monos" <[email protected]> wrote: >>>>>>> >>>>>>>>Hi, >>>>>>>> >>>>>>>>Also I think the problem is when you are trying to delete the >>>>>>>>network >>>>>>>>the >>>>>>>>router is powered off. >>>>>>>>Therefore when you click delete it wants to remove the firewall >>>>>>>>rules >>>>>>>>for >>>>>>>>that network but the router is not running so the command fails >>>>>>>>which >>>>>>>>fails the delet operation. >>>>>>> >>>>>>> >>>>>>> Also not a problem. The rules can be removed when the router is >>>>>>>stopped. >>>>>>> In this case the rules are removed in DB only. When the router >>>>>>>starts >>>>>>>up, >>>>>>> we start clean (cleanup all the rules) and re-apply all the rules >>>>>>>from >>>>>>>the >>>>>>> DB. So the removed rules won't exist on the router. >>>>>>> >>>>>>> -Alena. >>>>>>> >>>>>>>> >>>>>>>>Regards >>>>>>>> >>>>>>>>Tamas Monos DDI >>>>>>>>+44(0)2034687012 >>>>>>>>Chief Technical Office >>>>>>>>+44(0)2034687000 >>>>>>>>Veber: The Hosting Specialists Fax +44(0)871 >>>>>>>>522 >>>>>>>>7057 >>>>>>>>http://www.veber.co.uk >>>>>>>> >>>>>>>>Follow us on Twitter: www.twitter.com/veberhost >>>>>>>>Follow us on Facebook: www.facebook.com/veberhost >>>>>>>> >>>>>>>> >>>>>>>>-----Original Message----- >>>>>>>>From: Tamas Monos [mailto:[email protected]] >>>>>>>>Sent: 13 June 2012 18:15 >>>>>>>>To: [email protected] >>>>>>>>Subject: RE: Can not delete network >>>>>>>> >>>>>>>>Hi, >>>>>>>> >>>>>>>>I don't think you can delete a network if a router-vm for that >>>>>>>>network >>>>>>>>exists. >>>>>>>>If you are trying to delete a network that network should not have >>>>>>>>any >>>>>>>>VMs. >>>>>>>>Delete the associated router from the management interface then >>>>>>>>delete >>>>>>>>the network. >>>>>>>>This method works for me on 3.0.2 >>>>>>>> >>>>>>>>Regards >>>>>>>> >>>>>>>>Tamas Monos DDI >>>>>>>>+44(0)2034687012 >>>>>>>>Chief Technical Office >>>>>>>>+44(0)2034687000 >>>>>>>>Veber: The Hosting Specialists Fax +44(0)871 >>>>>>>>522 >>>>>>>>7057 >>>>>>>>http://www.veber.co.uk >>>>>>>> >>>>>>>>Follow us on Twitter: www.twitter.com/veberhost Follow us on >>>>>>>>Facebook: >>>>>>>>www.facebook.com/veberhost >>>>>>>> >>>>>>>>-----Original Message----- >>>>>>>>From: Alena Prokharchyk [mailto:[email protected]] >>>>>>>>Sent: 13 June 2012 18:12 >>>>>>>>To: [email protected] >>>>>>>>Subject: Re: Can not delete network >>>>>>>> >>>>>>>>Can you please check the management server log to see if there is >>>>>>>>more >>>>>>>>detailed exception in there. >>>>>>>> >>>>>>>>-Alena. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>On 6/13/12 9:50 AM, "Lu Heng" <[email protected]> wrote: >>>>>>>> >>>>>>>>>Hi >>>>>>>>> >>>>>>>>>I have problem deleting guest network, everytime I tried it always >>>>>>>>>shows "fail to delete network) >>>>>>>>> >>>>>>>>>2012-06-13 11:26:14,243 WARN [cloud.api.ApiDispatcher] >>>>>>>>>(Job-Executor-52:job-95) class com.cloud.api.ServerApiException : >>>>>>>>>Failed to delete network >>>>>>>>> >>>>>>>>>Any idea how it happens? >>>>>>>>>-- >>>>>>>>>-- >>>>>>>>>Kind regards. >>>>>>>>>Lu >>>>>>>>> >>>>>>>>>This transmission is intended solely for the addressee(s) shown >>>>>>>>>above. >>>>>>>>>It may contain information that is privileged, confidential or >>>>>>>>>otherwise protected from disclosure. Any review, dissemination or >>>>>>>>>use >>>>>>>>>of this transmission or its contents by persons other than the >>>>>>>>>intended >>>>>>>>>addressee(s) is strictly prohibited. If you have received this >>>>>>>>>transmission in error, please notify this office immediately and >>>>>>>>>e-mail >>>>>>>>>the original at the sender's address above by replying to this >>>>>>>>>message >>>>>>>>>and including the text of the transmission received. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>>-- >>>>>>-- >>>>>>Kind regards. >>>>>>Lu >>>>>> >>>>>>This transmission is intended solely for the addressee(s) shown >>>>>>above. >>>>>>It may contain information that is privileged, confidential or >>>>>>otherwise protected from disclosure. Any review, dissemination or use >>>>>>of this transmission or its contents by persons other than the >>>>>>intended addressee(s) is strictly prohibited. If you have received >>>>>>this transmission in error, please notify this office immediately and >>>>>>e-mail the original at the sender's address above by replying to this >>>>>>message and including the text of the transmission received. >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>>>-- >>>>-- >>>>Kind regards. >>>>Lu >>>> >>>>This transmission is intended solely for the addressee(s) shown above. >>>>It may contain information that is privileged, confidential or >>>>otherwise protected from disclosure. Any review, dissemination or use >>>>of this transmission or its contents by persons other than the >>>>intended addressee(s) is strictly prohibited. If you have received >>>>this transmission in error, please notify this office immediately and >>>>e-mail the original at the sender's address above by replying to this >>>>message and including the text of the transmission received. >>>> >>> >>> >> >> >> >> -- >> -- >> Kind regards. >> Lu >> >> This transmission is intended solely for the addressee(s) shown above. >> It may contain information that is privileged, confidential or >> otherwise protected from disclosure. Any review, dissemination or use >> of this transmission or its contents by persons other than the >> intended addressee(s) is strictly prohibited. If you have received >> this transmission in error, please notify this office immediately and >> e-mail the original at the sender's address above by replying to this >> message and including the text of the transmission received. > > > >-- >-- >Kind regards. >Lu > >This transmission is intended solely for the addressee(s) shown above. >It may contain information that is privileged, confidential or >otherwise protected from disclosure. Any review, dissemination or use >of this transmission or its contents by persons other than the >intended addressee(s) is strictly prohibited. If you have received >this transmission in error, please notify this office immediately and >e-mail the original at the sender's address above by replying to this >message and including the text of the transmission received. >
