cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angeline shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3155) [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone.
Date Thu, 22 Aug 2013 22:01:53 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747948#comment-13747948
] 

angeline shen commented on CLOUDSTACK-3155:
-------------------------------------------

MS  10.223.195.52   build 479

zone vmware has vmware DC associated with it.

http://10.223.195.52:8080/client/api?command=deleteZone&id=62606da9-0bf1-4d43-a432-08b795da4bbe&response=json&sessionkey=8psT5s%2BPJdketXAsXQ15Ms%2FVtIo%3D&_=1377208340791

{ "deletezoneresponse" : {"uuidList":[],"errorcode":530,"cserrorcode":4250,"errortext":"The
zone is not deletable because there are servers running in this zone"} }

MS log:

2013-08-22 14:41:58,069 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===START===  10.215.3.21
-- GET  command=deleteZone&id=62606da9-0bf1-4d43-a432-08b795da4bbe&response=json&sessionkey=8psT5s%2BPJdketXAsXQ15Ms%2FVtIo%3D&_=1377208340791
2013-08-22 14:41:58,104 ERROR [cloud.api.ApiServer] (catalina-exec-2:null) unhandled exception
executing api command: deleteZone
com.cloud.utils.exception.CloudRuntimeException: The zone is not deletable because there are
servers running in this zone
        at com.cloud.configuration.ConfigurationManagerImpl.checkIfZoneIsDeletable(ConfigurationManagerImpl.java:1381)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.configuration.ConfigurationManagerImpl.deleteZone(ConfigurationManagerImpl.java:1527)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at org.apache.cloudstack.api.command.admin.zone.DeleteZoneCmd.execute(DeleteZoneCmd.java:73)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
        at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
        at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
        at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
        at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
2013-08-22 14:41:58,111 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) ===END===  10.215.3.21
-- GET  command=deleteZone&id=62606da9-0bf1-4d43-a432-08b795da4bbe&response=json&sessionkey=8psT5s%2BPJdketXAsXQ15Ms%2FVtIo%3D&_=1377208340791
2013-08-22 14:42:07,388 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-4:null)
SeqA 2-10885: Processing Seq 2-10885:  { Cmd , MgmtId: -1, via: 2, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
 \"connections\": []\n}","wait":0}}] }


                
> [VMware] Deletion of zone should not be allowed if VMware DC is still associated with
that zone.
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3155
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3155
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>              Labels: vmware
>
> Deletion of zone should not be allowed if VMware DC is still associated with that zone.
> Let user go back and remove VMware DC from cloudstack zone and re-try deletion of zone.
> This is inline with the way deletion of zone is handled if there are pods/physical networks
etc. that are part of zone already.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message