You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/07/18 07:18:51 UTC

[jira] [Created] (CLOUDSTACK-3622) Built-in template download failure

Prasanna Santhanam created CLOUDSTACK-3622:
----------------------------------------------

             Summary: Built-in template download failure
                 Key: CLOUDSTACK-3622
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3622
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Prasanna Santhanam
            Priority: Blocker


The default built-in tempalte fails to download on latest master (11971b5a5812ab433b33365bc938704f2bd180e3) with the following exception:
 [{"com.cloud.agent.api.SecStorageSetupAnswer":{"_dir":"b5622678-7b80-3cd1-b196-09e9c943ece6","result":true,"details":"success","wait":0}}] }
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com local0: 2013-07-18 04:37:51,209 DEBUG [agent.transport.Request] (AgentConnectTaskPool-5:ctx-6a489527) Seq 5-13434881: Received:  { Ans: , MgmtId: 200973787296321, via: 5, Ver: v1, Flags:
 110, { SecStorageSetupAnswer } }
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com local0: 2013-07-18 04:37:51,209 DEBUG [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-5:ctx-6a489527) Details from executing class com.cloud.agent.api.SecStorageSetupCommand: succ
ess
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com local0: 2013-07-18 04:37:51,242 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-10:null) Seq 5-13434881: No more commands found
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com local0: 2013-07-18 04:37:51,268 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (AgentConnectTaskPool-5:ctx-6a489527) Successfully programmed secondary storage nfs://nfs.fmt.vmops.
com:/export/automation/acs/secondary in secondary storage VM s-1-VM
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com local0: 2013-07-18 04:37:51,303 ERROR [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-5:ctx-6a489527) Monitor SecondaryStorageListener says there is an error in the connect proces
s for 5 due to Index: 0, Size: 0
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at java.util.ArrayList.rangeCheck(ArrayList.java:571)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at java.util.ArrayList.get(ArrayList.java:349)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.utils.db.SearchCriteria2.addAnd(SearchCriteria2.java:117)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.storage.secondary.SecondaryStorageManagerImpl.generateFirewallConfiguration(SecondaryStorageManagerImpl.java:422)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.storage.secondary.SecondaryStorageListener.processConnect(SecondaryStorageListener.java:84)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:588)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1088)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.agent.manager.AgentManagerImpl.access$100(AgentManagerImpl.java:146)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1162)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
Jul 17 21:37:51 cloudstack-centos63.fmt.vmops.com     at java.lang.Thread.run(Thread.java:679)




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