subject:"Removing a zone"

Re: Removing a zone

2023-02-15 Thread jordan j

if you have deleted the storage but there are isos left in the database,
you can disable/delete the entries directly from the db.
one of the places (for isos i think) is template_store_ref table.

Regards,
Jordan



On Mon, Feb 13, 2023 at 9:01 AM Granwille Strauss
 wrote:

> Hi Guys
>
> I am busy cleaning up zones, and managed to delete all pods and cluster
> and so tied to the zone and all that but when deleting the zone itself it
> shows there is storage devices tied to zone. I have checked it all and
> there's none. However, I believe its because image ISO that were initially
> installed, see attached screenshot, which is why the zone can't be deleted.
> I tried adding the secondary storage again, where it was stored, but no
> luck. Any ideas how I can go about cleaning out these old ISOs to delete my
> old zone?
> --
> Regards / Groete
>
>  Granwille Strauss  //  Senior Systems Admin
>
> *e:* granwi...@namhost.com
> *m:* +264 81 323 1260 <+264813231260>
> *w:* www.namhost.com
>
>  
> 
> 
> 
>
>
> 
>
> Namhost Internet Services (Pty) Ltd,
>
> 24 Black Eagle Rd, Hermanus, 7210, RSA
>
>
>
> The content of this message is confidential. If you have received it by
> mistake, please inform us by email reply and then delete the message. It is
> forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone without our explicit consent. The integrity and security
> of this email cannot be guaranteed over the Internet. Therefore, the sender
> will not be held liable for any damage caused by the message. For our full
> privacy policy and disclaimers, please go to
> https://www.namhost.com/privacy-policy
>
> [image: Powered by AdSigner]
> 
>

Re: Removing a zone

2023-02-14 Thread Andrija Panic

(DefaultManagedContext.java:55)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:142)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:96)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:763)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:400)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:645)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:392)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555)
> at
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410)
> at
> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> at java.base/java.lang.Thread.run(Thread.java:829)
>
> I can 100% confirm, there are no primary or secondary storage configured
> for this zone, whatsoever. All network interfaces tied to this zone have
> been removed too.
> On 2/13/23 12:21, Kiran Chavala wrote:
>
> Hi Groete
>
> Could you please share the management server logs exception when you are 
> trying to delete the zone.
>
> I don't think its related to ISO
>
> 
>
> If you want to clean up the stale ISO's in the system
>
> Then you need to update the database
>
>
>   1.  Identify the template id in the vm_template table
>
> select * from vm_template where name="" and format="ISO";
>
>   2.  Update the state field to &qu

Re: Removing a zone

2023-02-13 Thread Granwille Strauss

er.ScopedHandler.nextHandle(ScopedHandler.java:235)
 at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
 at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
 at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434)
 at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
 at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
 at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
 at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
 at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349)
 at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
 at
org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:763)
 at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
 at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
 at org.eclipse.jetty.server.Server.handle(Server.java:516)
 at
org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:400)
 at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:645)
 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:392)
 at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
 at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
 at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
 at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555)
 at
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410)
 at
org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164)
 at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
 at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
 at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
 at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
 at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
 at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
 at
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
 at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
 at
org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
 at java.base/java.lang.Thread.run(Thread.java:829)

I can 100% confirm, there are no primary or secondary storage configured
for this zone, whatsoever. All network interfaces tied to this zone have
been removed too.
On 2/13/23 12:21, Kiran Chavala wrote:

Hi Groete

Could you please share the management server logs exception when you are trying 
to delete the zone.

I don't think its related to ISO



If you want to clean up the stale ISO's in the system

Then you need to update the database


   1.  Identify the template id in the vm_template table

select * from vm_template where name="" and format="ISO";

   2.  Update the state field to "Inactive"

update vm_template set state="Inactive" where template_id="";

   3.  Update the removed field to now();

update template_zone_ref set remvoed=now() where template_id="";

   4.  Update the template_Store_ref;

update template_store_ref set destroyed=1, state="Destroyed" where 
template_id="";



Regards
Kiran


____



From: Granwille Strauss
Sent: Monday, February 13, 2023 12:30
To:users@cloudstack.apache.org
Subject: Removing a zone


Hi Guys

I am busy cleaning up zones, and managed to delete all pods and cluster and so 
tied to the zone and all that but when deleting the zone itself it shows there 
is storage devices tied to zone. I have checked it all and there's none. 
However, I believe its because image ISO that were initially installed, see 
attached screenshot, which is why the zone can't be deleted. I tried adding the 
secondary storage again, where it was stored, but no luck. Any ideas how I can 
go about cleaning out these old ISOs to delete my old zone?

--
Regards / Groete

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/logo/621b3fa39fb210001f975298/cd2904ba-304d-4a49-bf33-cbe9ac76d929_248x-.png]<https://www.namhost.com>
  <https://www.namhost.com>  Granwille Strauss  //  Senior Systems Admin

e:granwi...@namhost.com<mailto:granwi...@namhost.com>  
m: +264 81 323 1260  <+264813231260>
w:www.namhost.com<https://www.namhost.com/>  <https://www.namhost.com/>

[

Re: Removing a zone

2023-02-13 Thread Andrija Panic

t; at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:763)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:400)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:645)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:392)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555)
> at
> org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410)
> at
> org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
> at
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
> at
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> at java.base/java.lang.Thread.run(Thread.java:829)
>
> I can 100% confirm, there are no primary or secondary storage configured
> for this zone, whatsoever. All network interfaces tied to this zone have
> been removed too.
> On 2/13/23 12:21, Kiran Chavala wrote:
>
> Hi Groete
>
> Could you please share the management server logs exception when you are 
> trying to delete the zone.
>
> I don't think its related to ISO
>
> 
>
> If you want to clean up the stale ISO's in the system
>
> Then you need to update the database
>
>
>   1.  Identify the template id in the vm_template table
>
> select * from vm_template where name="" and format="ISO";
>
>   2.  Update the state field to "Inactive"
>
> update vm_template set state="Inactive" where template_id="";
>
>   3.  Update the removed field to now();
>
> update template_zone_ref set remvoed=now() where template_id="";
>
>   4.  Update the template_Store_ref;
>
> update template_store_ref set destroyed=1, state="Destroyed" where 
> template_id="";
>
>
>
> Regards
> Kiran
>
>
> 
>
>
>
> From: Granwille Strauss
> Sent: Monday, February 13, 2023 12:30
> To: users@cloudstack.apache.org
> Subject: Removing a zone
>
>
> Hi Guys
>
> I am busy cleaning up zones, and managed to delete all pods and cluster and 
> so tied to the zone and all that but when deleting the zone itself it shows 
> there is storage devices tied to zone. I have checked it all and there's 
> none. However, I believe its because image ISO that were initially installed, 
> see attached screenshot, which is why the zone can't be deleted. I tried 
> adding the secondary storage again, where it was stored, but no luck. Any 
> ideas how I can go about cleaning out these old ISOs to delete my old zone?
>
> --
> Regards / Groete
>
> [https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/logo/621b3fa39fb210001f975298/cd2904ba-304d-4a49-bf33-cbe9ac76d929_248x-.png]<https://www.namhost.com>
>  <https://www.namhost.com> Granwille Strauss  //  Senior Systems Ad

Re: Removing a zone

2023-02-13 Thread Granwille Strauss


Hi Kiran


No, all running instances are on a different zone and none gives me the 
option to delete. However, I checked the volumes table now and found 
three "Destroy" instances, and used your SQL query to clear them out, 
which then successfully allowed me to delete the zone. Thank you very 
much for your speedy assistance in this regard. However, I believe this 
is a known bug, which stems from 2015 
https://issues.apache.org/jira/browse/CLOUDSTACK-9090 May be worth while 
for the dev's to look at.



On 2/13/23 12:44, Kiran Chavala wrote:

The logs are pointing that there are still active volume in the zone

From the UI are you able to destroy the data volumes or root volumes 
attached to any running instances




DB hack

update volumes set removed=now(), state=Destroy where id="";



Regards
Kiran



*From:* Granwille Strauss
*Sent:* Monday, February 13, 2023 16:05
*To:* users@cloudstack.apache.org
*Cc:* Kiran Chavala
*Subject:* Re: Removing a zone

Thank you,

After removing ISO via DB method you provided, error still exists so 
you were right, it was not the ISO causing this. Here's the log entry 
when I attempt to delete zone:


2023-02-13 12:31:48,258 ERROR [c.c.a.ApiServer] 
(qtp262366552-454:ctx-f498ef20 ctx-6c40cbcd) (logid:dd5b8f8e) 
unhandled exception executing api command: [Ljava.lang.String;@38b34249
com.cloud.utils.exception.CloudRuntimeException: The zone cannot be 
deleted because there are storage volumes in this zone.
    at 
com.cloud.configuration.ConfigurationManagerImpl.checkIfZoneIsDeletable(ConfigurationManagerImpl.java:2234)
    at 
com.cloud.configuration.ConfigurationManagerImpl.deleteZone(ConfigurationManagerImpl.java:2380)
    at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
    at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)

    at com.sun.proxy.$Proxy122.deleteZone(Unknown Source)
    at 
org.apache.cloudstack.api.command.admin.zone.DeleteZoneCmd.execute(DeleteZoneCmd.java:72)

    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:163)
    at com.cloud.api.ApiServer.queueCommand(ApiServer.java:776)
    at com.cloud.api.ApiServer.handleRequest(ApiServer.java:600)
    at 
com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:327)

    at com.cloud.api.ApiServlet$1.run(ApiServlet.java:145)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)

    at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:142)
    at com.cloud.api.ApiServlet.doGet(ApiServlet.java:96)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
    at 
org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450)
    at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
    at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
    at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
    at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
    at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
    at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
    at 
org.eclipse.jetty.server.session.Ses

Re: Removing a zone

2023-02-13 Thread Kiran Chavala

The logs are pointing that there are still active volume in the zone

>From the UI are you able to destroy the data volumes or root volumes attached 
>to any running instances

[cid:e8ca360c-a016-429d-b458-1a845632872e]


DB hack

update volumes set removed=now(), state=Destroy where id="";



Regards
Kiran




 

From: Granwille Strauss
Sent: Monday, February 13, 2023 16:05
To: users@cloudstack.apache.org
Cc: Kiran Chavala
Subject: Re: Removing a zone


Thank you,

After removing ISO via DB method you provided, error still exists so you were 
right, it was not the ISO causing this. Here's the log entry when I attempt to 
delete zone:

2023-02-13 12:31:48,258 ERROR [c.c.a.ApiServer] (qtp262366552-454:ctx-f498ef20 
ctx-6c40cbcd) (logid:dd5b8f8e) unhandled exception executing api command: 
[Ljava.lang.String;@38b34249
com.cloud.utils.exception.CloudRuntimeException: The zone cannot be deleted 
because there are storage volumes in this zone.
at 
com.cloud.configuration.ConfigurationManagerImpl.checkIfZoneIsDeletable(ConfigurationManagerImpl.java:2234)
at 
com.cloud.configuration.ConfigurationManagerImpl.deleteZone(ConfigurationManagerImpl.java:2380)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
at com.sun.proxy.$Proxy122.deleteZone(Unknown Source)
at 
org.apache.cloudstack.api.command.admin.zone.DeleteZoneCmd.execute(DeleteZoneCmd.java:72)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:163)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:776)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:600)
at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:327)
at com.cloud.api.ApiServlet$1.run(ApiServlet.java:145)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:142)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:96)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
at 
org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(Scoped

Re: Removing a zone

2023-02-13 Thread Granwille Strauss

)

    at org.eclipse.jetty.server.Server.handle(Server.java:516)
    at 
org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:400)

    at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:645)
    at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:392)
    at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
    at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)

    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
    at 
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555)
    at 
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410)
    at 
org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164)

    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
    at 
org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
    at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
    at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
    at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
    at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
    at 
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
    at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
    at 
org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)

    at java.base/java.lang.Thread.run(Thread.java:829)


I can 100% confirm, there are no primary or secondary storage configured 
for this zone, whatsoever. All network interfaces tied to this zone have 
been removed too.


On 2/13/23 12:21, Kiran Chavala wrote:

Hi Groete

Could you please share the management server logs exception when you are trying 
to delete the zone.

I don't think its related to ISO



If you want to clean up the stale ISO's in the system

Then you need to update the database


   1.  Identify the template id in the vm_template table

select * from vm_template where name="" and format="ISO";

   2.  Update the state field to "Inactive"

update vm_template set state="Inactive" where template_id="";

   3.  Update the removed field to now();

update template_zone_ref set remvoed=now() where template_id="";

   4.  Update the template_Store_ref;

update template_store_ref set destroyed=1, state="Destroyed" where 
template_id="";



Regards
Kiran




  


From: Granwille Strauss
Sent: Monday, February 13, 2023 12:30
To:users@cloudstack.apache.org
Subject: Removing a zone


Hi Guys

I am busy cleaning up zones, and managed to delete all pods and cluster and so 
tied to the zone and all that but when deleting the zone itself it shows there 
is storage devices tied to zone. I have checked it all and there's none. 
However, I believe its because image ISO that were initially installed, see 
attached screenshot, which is why the zone can't be deleted. I tried adding the 
secondary storage again, where it was stored, but no luck. Any ideas how I can 
go about cleaning out these old ISOs to delete my old zone?

--
Regards / Groete

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/logo/621b3fa39fb210001f975298/cd2904ba-304d-4a49-bf33-cbe9ac76d929_248x-.png]<https://www.namhost.com>
  Granwille Strauss  //  Senior Systems Admin

e:granwi...@namhost.com<mailto:granwi...@namhost.com>
m: +264 81 323 1260
w:www.namhost.com<https://www.namhost.com/>

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_01/621b3fa39fb210001f975298/9151954b-b298-41aa-89c8-1d68af075373_48x48.png]<https://www.facebook.com/namhost>
  
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_02/621b3fa39fb210001f975298/85a9dc7c-7bd1-4958-85a9-e6a25baeb028_48x48.png]<https://twitter.com/namhost>
   
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_03/621b3fa39fb210001f975298/c1c5386c-914c-43cf-9d37-5b4aa8e317ab_48x48.png]<https://www.instagram.com/namhostinternetservices/>
   
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_04/621b3fa39fb210001f975298/3aaa7968-130e-48ec-821d-559a332cce47_48x48.png]<https://www.linkedin.com/company/namhos>
   
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_05/621b3fa39fb210001f975298/3a8c09e6-588f-43a8-acfd-be4423fd3fb6_48x48.png]<https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>

[https://www.adsigner.com/v1/i/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner/940x300]<https://www.adsigner.com/v1/l/6310

Re: Removing a zone

2023-02-13 Thread Kiran Chavala

Hi Groete

Could you please share the management server logs exception when you are trying 
to delete the zone.

I don't think its related to ISO



If you want to clean up the stale ISO's in the system

Then you need to update the database


  1.  Identify the template id in the vm_template table

select * from vm_template where name="" and format="ISO";

  2.  Update the state field to "Inactive"

update vm_template set state="Inactive" where template_id="";

  3.  Update the removed field to now();

update template_zone_ref set remvoed=now() where template_id="";

  4.  Update the template_Store_ref;

update template_store_ref set destroyed=1, state="Destroyed" where 
template_id="";



Regards
Kiran




 

From: Granwille Strauss
Sent: Monday, February 13, 2023 12:30
To: users@cloudstack.apache.org
Subject: Removing a zone


Hi Guys

I am busy cleaning up zones, and managed to delete all pods and cluster and so 
tied to the zone and all that but when deleting the zone itself it shows there 
is storage devices tied to zone. I have checked it all and there's none. 
However, I believe its because image ISO that were initially installed, see 
attached screenshot, which is why the zone can't be deleted. I tried adding the 
secondary storage again, where it was stored, but no luck. Any ideas how I can 
go about cleaning out these old ISOs to delete my old zone?

--
Regards / Groete

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/logo/621b3fa39fb210001f975298/cd2904ba-304d-4a49-bf33-cbe9ac76d929_248x-.png]<https://www.namhost.com>
 Granwille Strauss  //  Senior Systems Admin

e: granwi...@namhost.com<mailto:granwi...@namhost.com>
m: +264 81 323 1260
w: www.namhost.com<https://www.namhost.com/>

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_01/621b3fa39fb210001f975298/9151954b-b298-41aa-89c8-1d68af075373_48x48.png]<https://www.facebook.com/namhost>
 
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_02/621b3fa39fb210001f975298/85a9dc7c-7bd1-4958-85a9-e6a25baeb028_48x48.png]
 <https://twitter.com/namhost>  
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_03/621b3fa39fb210001f975298/c1c5386c-914c-43cf-9d37-5b4aa8e317ab_48x48.png]
 <https://www.instagram.com/namhostinternetservices/>  
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_04/621b3fa39fb210001f975298/3aaa7968-130e-48ec-821d-559a332cce47_48x48.png]
 <https://www.linkedin.com/company/namhos>  
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_05/621b3fa39fb210001f975298/3a8c09e6-588f-43a8-acfd-be4423fd3fb6_48x48.png]
 <https://www.youtube.com/channel/UCTd5v-kVPaic_dguGur15AA>

[https://www.adsigner.com/v1/i/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner/940x300]<https://www.adsigner.com/v1/l/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner>

Namhost Internet Services (Pty) Ltd,

24 Black Eagle Rd, Hermanus, 7210, RSA


The content of this message is confidential. If you have received it by 
mistake, please inform us by email reply and then delete the message. It is 
forbidden to copy, forward, or in any way reveal the contents of this message 
to anyone without our explicit consent. The integrity and security of this 
email cannot be guaranteed over the Internet. Therefore, the sender will not be 
held liable for any damage caused by the message. For our full privacy policy 
and disclaimers, please go to https://www.namhost.com/privacy-policy

[Powered by 
AdSigner]<https://www.adsigner.com/v1/c/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818>

Removing a zone

2023-02-12 Thread Granwille Strauss


Hi Guys

I am busy cleaning up zones, and managed to delete all pods and cluster 
and so tied to the zone and all that but when deleting the zone itself 
it shows there is storage devices tied to zone. I have checked it all 
and there's none. However, I believe its because image ISO that were 
initially installed, see attached screenshot, which is why the zone 
can't be deleted. I tried adding the secondary storage again, where it 
was stored, but no luck. Any ideas how I can go about cleaning out these 
old ISOs to delete my old zone?


--
Regards / Groete

 Granwille Strauss  // Senior Systems Admin

*e:* granwi...@namhost.com
*m:* +264 81 323 1260 
*w:* www.namhost.com 





Namhost Internet Services (Pty) Ltd,

24 Black Eagle Rd, Hermanus, 7210, RSA



The content of this message is confidential. If you have received it by 
mistake, please inform us by email reply and then delete the message. It 
is forbidden to copy, forward, or in any way reveal the contents of this 
message to anyone without our explicit consent. The integrity and 
security of this email cannot be guaranteed over the Internet. 
Therefore, the sender will not be held liable for any damage caused by 
the message. For our full privacy policy and disclaimers, please go to 
https://www.namhost.com/privacy-policy


Powered by AdSigner 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Re: Removing a zone

Removing a zone

9 matches

Site Navigation

Mail list logo

Footer information