cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2293) [BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external devices
Date Tue, 30 Apr 2013 09:10:15 GMT
venkata swamybabu budumuru created CLOUDSTACK-2293:
------------------------------------------------------

             Summary: [BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external
devices
                 Key: CLOUDSTACK-2293
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2293
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Controller
    Affects Versions: 4.2.0
         Environment: commit 0e2ffe72aa641f4551cae63fbc36454c5934342f
            Reporter: venkata swamybabu budumuru
            Assignee: Murali Reddy
             Fix For: 4.2.0


Steps to reproduce :

1. Have at least one basic zone created with Xen Cluster using "EIP/ELB Offering with NetScaler"
mysql> select * from network_offerings where id=15\G
*************************** 1. row ***************************
                       id: 15
                     name: EIPOffering
                     uuid: 6207d909-c780-4661-8a61-7e397aad7b77
              unique_name: EIPOffering
             display_text: EIPOffering
                  nw_rate: NULL
                  mc_rate: 10
             traffic_type: Guest
                     tags: NULL
              system_only: 0
             specify_vlan: 1
      service_offering_id: NULL
            conserve_mode: 0
                  created: 2013-04-24 17:23:07
                  removed: NULL
                  default: 0
             availability: Optional
     dedicated_lb_service: 0
shared_source_nat_service: 0
                 sort_key: 0
 redundant_router_service: 0
                    state: Enabled
               guest_type: Shared
       elastic_ip_service: 1
  eip_associate_public_ip: 0
       elastic_lb_service: 1
        specify_ip_ranges: 1
                   inline: 0
            is_persistent: 0

2. Deleted all the physical network that exists in the basic zone but, it didn't cleanup the
NetScaler info associated with Physical network.Can see the netscaler info in the cloud.host_details
table.

3. Due to the above reason, deleteZone is failing saying there are servers running in this
zone. 

2013-04-30 10:30:50,205 DEBUG [cloud.api.ApiServlet] (1098099294@qtp-293858992-68:null) ===START===
 10.252.248.175 -- GET  command=deleteZone&id=f0d20b77-3aec-4a0d-a154-9f1324c31956&response=json&sessionkey=CnR%2Bbnhyla1mzycOIXluse0E5o4%3D&_=1367312502554
2013-04-30 10:30:50,277 ERROR [cloud.api.ApiServer] (1098099294@qtp-293858992-68: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:1128)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.configuration.ConfigurationManagerImpl.deleteZone(ConfigurationManagerImpl.java:1262)
        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:155)
        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:512)
        at com.cloud.api.ApiServer.handleRequest(ApiServer.java:362)
        at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
        at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Attaching the db dump along  with other logs.

--
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