cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Koneti (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-3839) add host is taking too long which causes createstorage pool to fail as the host is not up
Date Mon, 12 Aug 2013 07:09:47 GMT

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

Kiran Koneti edited comment on CLOUDSTACK-3839 at 8/12/13 7:08 AM:
-------------------------------------------------------------------

it is reproduced every time we make setup in the our location. Not sure with other locations.
I actually fails initially to add the primary storage saying the host is not ready and if
we wait for some time i.e around 2 minutes and re add the primary storage then the storage
creations goes on well without any issues.

This probably is the timing issue as the primary storage try's to add before the host status
is UP in the CS.
                
      was (Author: kiran_koneti):
    it is reproduced every time we make setup in the HYD lab. Not sure with other locations.
I actually fails initially to add the primary storage saying the host is not ready and if
we wait for some time i.e around 2 minutes and re add the primary storage then the storage
creations goes on well without any issues.

This probably is the timing issue as the primary storage try's to add before the host status
is UP in the CS.
                  
> add host is taking too long which causes createstorage pool to fail as the host is not
up
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3839
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3839
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Srikanteswararao Talluri
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> ==============
> Use zone create wizard to create a new zone. As the zone create process tries to add
primary storage, it finds that hosts are not ready yet. 
> Addition of primary storage succeeds after a while.
> ===START===  10.101.255.7 -- GET  command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616
> 2013-07-26 13:25:28,682 DEBUG [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-1:null) createPool Params @ scheme - nfs storageHost - 10.147.28.8 hostPath
- /vol/dgVol/automation/adv/pri_2 port - -1
> 2013-07-26 13:25:28,721 DEBUG [cloud.storage.StorageManagerImpl] (catalina-exec-1:null)
Failed to add data store
> com.cloud.utils.exception.CloudRuntimeException: No host up to associate a storage pool
with in cluster 2
>         at org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:368)
>         at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:724)
>         at com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:175)
>         at org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168)
>         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-07-26 13:25:28,729 INFO  [cloud.api.ApiServer] (catalina-exec-1:null) null
> 2013-07-26 13:25:28,730 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===END===
 10.101.255.7 -- GET  command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616

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