[jira] [Updated] (CLOUDSTACK-3288) [BVT] DeployVM in Affinity Group Test fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3288: --- Summary: [BVT] DeployVM in Affinity Group Test fails (was: [BVT] DeployVM in Affinity Grou Test fails) > [BVT] DeployVM in Affinity Group Test fails > --- > > Key: CLOUDSTACK-3288 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3288 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > Attachments: 456.tar.bz2 > > > For the past 17 or so builds the test for deploying VMs in affinity group has > been failing > Execute cmd: deployvirtualmachine failed, due to: errorCode: 431, > errorText:Unable to find affinity group by name webvms > Stacktrace > Traceback (most recent call last): > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/test/integration/smoke/test_affinity_groups.py", > line 126, in test_DeployVmAntiAffinityGroup > affinitygroupnames=[self.ag.name] > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/integration/lib/base.py", > line 317, in create > virtual_machine = apiclient.deployVirtualMachine(cmd, method=method) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", > line 550, in deployVirtualMachine > response = self.connection.marvin_request(command, > response_type=response, method=method) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackConnection.py", > line 222, in marvin_request > response = jsonHelper.getResultObj(response.json(), response_type) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/jsonHelper.py", > line 148, in getResultObj > raise cloudstackException.cloudstackAPIException(respname, errMsg) > cloudstackAPIException: Execute cmd: deployvirtualmachine failed, due to: > errorCode: 431, errorText:Unable to find affinity group by name webvms -- 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
[jira] [Commented] (CLOUDSTACK-3283) System VM does not start on Hyper-V Server 2012
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696053#comment-13696053 ] Prasanna Santhanam commented on CLOUDSTACK-3283: Where are the HyperV drivers? They should go into tools/appliance/systemvm* to create the new template having the drivers > System VM does not start on Hyper-V Server 2012 > --- > > Key: CLOUDSTACK-3283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3283 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: Future > Environment: Hyper-V hypervisor >Reporter: Donal Lafferty > > The SystemVM is supposed to have Hyper-V drivers installed. > A VM was created with the SystemVM image attached and started. > Although CPU was stuck at 12%, the console displayed no text. It was > impossible to login from the console. -- 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
[jira] [Commented] (CLOUDSTACK-3023) Tag missing for test integration.component.test_ldap.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696050#comment-13696050 ] ASF subversion and git services commented on CLOUDSTACK-3023: - Commit 56a001d1c49221397621759d784bd6000b38f5e4 in branch refs/heads/master from [~sadhu] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=56a001d ] CLOUDSTACK-3023: added tags for all the test cases Signed-off-by: Prasanna Santhanam > Tag missing for test integration.component.test_ldap.py > --- > > Key: CLOUDSTACK-3023 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3023 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.0 > Environment: Automation >Reporter: Rayees Namathponnan >Assignee: sadhu suresh > Fix For: 4.2.0 > > > Tag missing for test integration.component.test_ldap.py, and this case not > getting excuted -- 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
[jira] [Commented] (CLOUDSTACK-3074) Automation framework need to be updated for adding DC to zone, in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696051#comment-13696051
]
ASF subversion and git services commented on CLOUDSTACK-3074:
-
Commit f3e30486825c69670eec733517c8aa766c299dc1 in branch refs/heads/master
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f3e3048 ]
CLOUDSTACK-3074: include support for vmwaredc mapping to zone
vmware dc can be mapped to the zone after CLOUDSTACK-1963. include
support in marvin for adding the vmwaredc.
vmwaredc : {
name:
username:
vcenter:
password:
zoneid:
}
Will be sent during pod creation before cluster creation.
Signed-off-by: Prasanna Santhanam
> Automation framework need to be updated for adding DC to zone, in vmware
>
>
> Key: CLOUDSTACK-3074
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3074
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
> Environment: Automation
>Reporter: Rayees Namathponnan
>Assignee: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> deployDataCenter.py need to update for adding DC to ZOne
--
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
[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696052#comment-13696052
]
ASF subversion and git services commented on CLOUDSTACK-1963:
-
Commit f3e30486825c69670eec733517c8aa766c299dc1 in branch refs/heads/master
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f3e3048 ]
CLOUDSTACK-3074: include support for vmwaredc mapping to zone
vmware dc can be mapped to the zone after CLOUDSTACK-1963. include
support in marvin for adding the vmwaredc.
vmwaredc : {
name:
username:
vcenter:
password:
zoneid:
}
Will be sent during pod creation before cluster creation.
Signed-off-by: Prasanna Santhanam
> New mapping model for CloudStack zone and Vmware datacenter
>
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here,
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel
--
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
[jira] [Updated] (CLOUDSTACK-3288) [BVT] DeployVM in Affinity Grou Test fails
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3288: --- Attachment: 456.tar.bz2 management server logs > [BVT] DeployVM in Affinity Grou Test fails > -- > > Key: CLOUDSTACK-3288 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3288 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > Attachments: 456.tar.bz2 > > > For the past 17 or so builds the test for deploying VMs in affinity group has > been failing > Execute cmd: deployvirtualmachine failed, due to: errorCode: 431, > errorText:Unable to find affinity group by name webvms > Stacktrace > Traceback (most recent call last): > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/test/integration/smoke/test_affinity_groups.py", > line 126, in test_DeployVmAntiAffinityGroup > affinitygroupnames=[self.ag.name] > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/integration/lib/base.py", > line 317, in create > virtual_machine = apiclient.deployVirtualMachine(cmd, method=method) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", > line 550, in deployVirtualMachine > response = self.connection.marvin_request(command, > response_type=response, method=method) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackConnection.py", > line 222, in marvin_request > response = jsonHelper.getResultObj(response.json(), response_type) > File > "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/jsonHelper.py", > line 148, in getResultObj > raise cloudstackException.cloudstackAPIException(respname, errMsg) > cloudstackAPIException: Execute cmd: deployvirtualmachine failed, due to: > errorCode: 431, errorText:Unable to find affinity group by name webvms -- 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
[jira] [Created] (CLOUDSTACK-3288) [BVT] DeployVM in Affinity Grou Test fails
Prasanna Santhanam created CLOUDSTACK-3288: -- Summary: [BVT] DeployVM in Affinity Grou Test fails Key: CLOUDSTACK-3288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3288 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Priority: Critical Fix For: 4.2.0 Attachments: 456.tar.bz2 For the past 17 or so builds the test for deploying VMs in affinity group has been failing Execute cmd: deployvirtualmachine failed, due to: errorCode: 431, errorText:Unable to find affinity group by name webvms Stacktrace Traceback (most recent call last): File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run testMethod() File "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/test/integration/smoke/test_affinity_groups.py", line 126, in test_DeployVmAntiAffinityGroup affinitygroupnames=[self.ag.name] File "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/integration/lib/base.py", line 317, in create virtual_machine = apiclient.deployVirtualMachine(cmd, method=method) File "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", line 550, in deployVirtualMachine response = self.connection.marvin_request(command, response_type=response, method=method) File "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 222, in marvin_request response = jsonHelper.getResultObj(response.json(), response_type) File "/var/lib/jenkins/workspace/test-smoke-matrix/suite/test_affinity_groups/559/lib/python2.7/site-packages/marvin/jsonHelper.py", line 148, in getResultObj raise cloudstackException.cloudstackAPIException(respname, errMsg) cloudstackAPIException: Execute cmd: deployvirtualmachine failed, due to: errorCode: 431, errorText:Unable to find affinity group by name webvms -- 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
[jira] [Created] (CLOUDSTACK-3287) [GSLB] API "updateGlobalLoadBalancerRule" is not recognised by CloudStack
venkata swamybabu budumuru created CLOUDSTACK-3287: -- Summary: [GSLB] API "updateGlobalLoadBalancerRule" is not recognised by CloudStack Key: CLOUDSTACK-3287 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3287 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: venkata swamybabu budumuru Assignee: Murali Reddy Priority: Critical Fix For: 4.2.0 Steps to reproduce: (1) Have latest CloudStack setup with at least 2 advanced zones running with XenServer (2) Try to execute "updateGlobalLoadBalancerRule" API Observations: (i) When tried to execute, it fails with the following error http://10.147.59.194:8096/api?command=updateGlobalLoadBalancerRule 432Unknown API command: updateGlobalLoadBalancerRule (ii) Other commands like create,assign, removeFrom GSLB rule works fine. -- 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
[jira] [Commented] (CLOUDSTACK-3167) [Automation] List VLAN range API call failed with null pointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696006#comment-13696006 ] Abhinandan Prateek commented on CLOUDSTACK-3167: 3119 is resolved, resolving this. > [Automation] List VLAN range API call failed with null pointer exception > - > > Key: CLOUDSTACK-3167 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3167 > 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: Master build, >Reporter: Rayees Namathponnan >Assignee: Bharat Kumar >Priority: Blocker > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-3167.rar, dbdump.rar > > > SSVM test cases failed from BVT > run listVLAN Range command, its fails willl null pointer exception > http://10.223.49.195:8096/?command=listVlanIpRanges&zoneid=72deef27-805a-4c6a-bf37-2b04d6c614d0&response=json > 2013-06-24 17:32:44,763 DEBUG [cloud.projects.ProjectManagerImpl] > (Job-Executor-17:job-3320) Accounts are unassign successfully from project > Project[94|name=Project-TRGJ8K|domainid=1] as a part of project cleanup... > 2013-06-24 17:32:44,795 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Complete async job-3320, jobStatus: 1, resultCode: > 0, result: org.apache.cloudstack.api.response.SuccessResponse@7c56947b > 2013-06-24 17:32:44,799 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Done executing > org.apache.cloudstack.api.command.user.project.DeleteProjectCmd for job-3320 > 2013-06-24 17:32:45,192 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listVlanIpRanges > java.lang.NullPointerException > at > com.cloud.configuration.ConfigurationManagerImpl.getVlanAccount(ConfigurationManagerImpl.java:4570) > at com.cloud.api.ApiDBUtils.getVlanAccount(ApiDBUtils.java:1062) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:604) > at > org.apache.cloudstack.api.command.admin.vlan.ListVlanIpRangesCmd.execute(ListVlanIpRangesCmd.java:145) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServer.handle(ApiServer.java:302) > at > org.apache.http.protocol.HttpService.doService(HttpService.java:375) > at > org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290) > at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:992) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- 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
[jira] [Resolved] (CLOUDSTACK-3167) [Automation] List VLAN range API call failed with null pointer exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek resolved CLOUDSTACK-3167. Resolution: Fixed > [Automation] List VLAN range API call failed with null pointer exception > - > > Key: CLOUDSTACK-3167 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3167 > 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: Master build, >Reporter: Rayees Namathponnan >Assignee: Bharat Kumar >Priority: Blocker > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-3167.rar, dbdump.rar > > > SSVM test cases failed from BVT > run listVLAN Range command, its fails willl null pointer exception > http://10.223.49.195:8096/?command=listVlanIpRanges&zoneid=72deef27-805a-4c6a-bf37-2b04d6c614d0&response=json > 2013-06-24 17:32:44,763 DEBUG [cloud.projects.ProjectManagerImpl] > (Job-Executor-17:job-3320) Accounts are unassign successfully from project > Project[94|name=Project-TRGJ8K|domainid=1] as a part of project cleanup... > 2013-06-24 17:32:44,795 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Complete async job-3320, jobStatus: 1, resultCode: > 0, result: org.apache.cloudstack.api.response.SuccessResponse@7c56947b > 2013-06-24 17:32:44,799 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-17:job-3320) Done executing > org.apache.cloudstack.api.command.user.project.DeleteProjectCmd for job-3320 > 2013-06-24 17:32:45,192 ERROR [cloud.api.ApiServer] (ApiServer-2:null) > unhandled exception executing api command: listVlanIpRanges > java.lang.NullPointerException > at > com.cloud.configuration.ConfigurationManagerImpl.getVlanAccount(ConfigurationManagerImpl.java:4570) > at com.cloud.api.ApiDBUtils.getVlanAccount(ApiDBUtils.java:1062) > at > com.cloud.api.ApiResponseHelper.createVlanIpRangeResponse(ApiResponseHelper.java:604) > at > org.apache.cloudstack.api.command.admin.vlan.ListVlanIpRangesCmd.execute(ListVlanIpRangesCmd.java:145) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServer.handle(ApiServer.java:302) > at > org.apache.http.protocol.HttpService.doService(HttpService.java:375) > at > org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290) > at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:992) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- 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
[jira] [Assigned] (CLOUDSTACK-3240) [Multiple_IP_Ranges] Failed to create ip alias on VR while deploying guest vm with ip address from new CIDR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3240:
--
Assignee: Bharat Kumar
> [Multiple_IP_Ranges] Failed to create ip alias on VR while deploying guest vm
> with ip address from new CIDR
> ---
>
> Key: CLOUDSTACK-3240
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3240
> 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
> Environment: Latest build from master-6-17-stable branch
>Reporter: Sanjeev N
>Assignee: Bharat Kumar
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Failed to create ip alias on VR while deploying guest vm with ip address from
> new CIDR:
> Repro steps:
> ===
> 1.Bring up CS in Advanced zone with VMWare Cluster
> 2.Create shared network and add CIDR in the network
> 3.Add another guest ip range in new cidr in the shared network
> 4.Exhaust all guest IP addresses from the primary IP range
> 5.Try to deploy guest vm using the shared network created at step2 (CS will
> try to assing ip address from new cidr added at step3)
> Expected Result:
> ==
> Since vm gets IP address from new cidr ip alias should be created on router
> vm to server dhcp requests
> Actual Result:
>
> vm deployment failed since ip alias creation failed.
> Observations:
>
> createipAlias command looks for createipAlias.sh script on router vm but
> actually the script name is "createIpAlias.sh". So it should try to execute
> createIpAlias.sh instead of createipAlias.sh on router vm.
> Following is the log snippet from management server log:
> 2013-06-27 13:16:39,776 INFO [vmware.resource.VmwareResource]
> (DirectAgent-304:10.147.40.9) Executing createipAlias command:
> {"routerip":"10.147.33.11","ipAliasTOs":[{"routerip":"10.147.33.130","netmask":"255.255.255.192","alias_count":"31"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}
> 2013-06-27 13:16:39,776 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-304:10.147.40.9) Run command on domR 10.147.40.249,
> /root/createipAlias 10.147.40.249 31:10.147.33.130:255.255.255.192-
> 2013-06-27 13:16:39,776 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-304:10.147.40.9) Use router's private IP for SSH control. IP :
> 10.147.40.249
> 2013-06-27 13:16:40,030 ERROR [utils.ssh.SshHelper]
> (DirectAgent-304:10.147.40.9) SSH execution of command /root/createipAlias.sh
> 10.147.40.249 31:10.147.33.130:255.255.255.192- has an error status code in
> return. result output: bash: /root/createipAlias.sh: No such file or directory
> 2013-06-27 13:16:40,035 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-304:10.147.40.9) ipAlias command on domr 10.147.40.249 failed,
> message: bash: /root/createipAlias.sh: No such file or directory
> 2013-06-27 13:16:40,035 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-304:null) Seq 9-1765409128: Cancelling because one of the
> answers is false and it is stop on error.
> 2013-06-27 13:16:40,035 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-304:null) Seq 9-1765409128: Response Received:
> 2013-06-27 13:16:40,035 DEBUG [agent.transport.Request]
> (DirectAgent-304:null) Seq 9-1765409128: Processing: { Ans: , MgmtId:
> 7332683579487, via: 9, Ver: v1, Flags: 10,
> [{"Answer":{"result":false,"details":"createipAlias failed due to bash:
> /root/createipAlias.sh: No such file or directory\n","wait":0}}] }
> 2013-06-27 13:16:40,036 DEBUG [agent.transport.Request]
> (Job-Executor-157:job-157) Seq 9-1765409128: Received: { Ans: , MgmtId:
> 7332683579487, via: 9, Ver: v1, Flags: 10, { Answer } }
> 2013-06-27 13:16:40,057 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-157:job-157) Failed to start instance VM[User|z3-s2-passwd]
> com.cloud.utils.exception.CloudRuntimeException: failed to configure ip alias
> on the router as a part of dhcp config
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.configDhcpForSubnet(VirtualNetworkApplianceManagerImpl.java:2834)
> at
> com.cloud.network.element.VirtualRouterElement.configDhcpSupportForSubnet(VirtualRouterElement.java:870)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:1978)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2093)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2034)
> at
> com.cloud.vm.Virtual
[jira] [Commented] (CLOUDSTACK-3144) [Automation] Deletion of templates failing. Fails to find image store housing template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695989#comment-13695989 ] ASF subversion and git services commented on CLOUDSTACK-3144: - Commit 87c401aaafbe786bd699091779a5f2741ab03889 in branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=87c401a ] CLOUDSTACK-3144: [Automation] Deletion of templates failing. Fails to find image store housing template. > [Automation] Deletion of templates failing. Fails to find image store housing > template > -- > > Key: CLOUDSTACK-3144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: 427.tar.bz2, dbdump.tar.bz2 > > > Deletion of templates during account GC fails with the following exception > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,698 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: EVSCLU due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[205-VHD-2ed8c0aee-7437-3c19-b3ac-cec513d806c0 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 12:22:07 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,701 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: Public template-CS42CN due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[206-VHD-247c4a699-73e3-32e7-b69e-8ea4858ef389 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07
[jira] [Commented] (CLOUDSTACK-3145) StorageManager-Scavenger NPEs when cleaning up templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695990#comment-13695990 ] ASF subversion and git services commented on CLOUDSTACK-3145: - Commit 2c31f38c05c16d661812cb89317eb2d4e6c8faf3 in branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2c31f38 ] CLOUDSTACK-3145:StorageManager-Scavenger NPEs when cleaning up templates. > StorageManager-Scavenger NPEs when cleaning up templates > > > Key: CLOUDSTACK-3145 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3145 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > > This is possibly related to the issue seen in CLOUDSTACK-3144. In this case > the storage cleanup thread is set to run every 5 minutes and after the > template deletion fails during account gc. The following NPE is notieced from > the storagemanager scavenger: > Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,384 WARN > [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) problem > cleaning up templates in secondary storage store > nfs://nfs.fmt.vmops.com:/export/automation/acs/secondary > Jun 23 12:18:52 java.lang.NullPointerException > Jun 23 12:18:52 java.lang.NullPointerException > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.TemplateObject.getInstallPath(TemplateObject.java:325) > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.to.TemplateObjectTO.(TemplateObjectTO.java:59) > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.TemplateObject.getTO(TemplateObject.java:312) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1134) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1025) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1328) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 12:18:52 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,386 DEBUG > [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) > Secondary storage garbage collector found 0 snapshots to cleanup on secondary > storage host: n > fs://nfs.fmt.vmops.com:/export/automation/acs/secondary -- 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
[jira] [Resolved] (CLOUDSTACK-2276) NPE while attaching the volume to the instance which is created from ROOT Disk Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das resolved CLOUDSTACK-2276.
-
Resolution: Fixed
The issue is not present in master but in master-6-17-stable. Fixed it in
master-6-17-stable
> NPE while attaching the volume to the instance which is created from ROOT
> Disk Snapshot
> ---
>
> Key: CLOUDSTACK-2276
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2276
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Koushik Das
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Setup: Advanced Networking Zone with Xen 6.1 , MS -RHEL 6.3
> Steps:
> 1. Deploy instance as ROOT admin
> 2. Create the snapshot from this instance ROOT disk
> 3. Create Volume from this snapshot
> 4. Try to attach this volume to the instance .
> Observation:
> NPE while attaching the volume to the instance which is created from ROOT
> Disk Snapshot
> 2013-04-29 16:51:02,412 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===END=== 10.144.6.19 -- GET
> command=attachVolume&id=3c8487fd-a30f-42d6-bc14-e19ec6c4090c&virtualMachineId=cc2a94bb-bdf0-4d36-9f2c-a501c75f53dd&response=json&sessionkey=50KnW0aaOd0wvF2hspe71pXsfqI%3D&_=1367234593280
> 2013-04-29 16:51:02,450 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-41:job-57) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-57
> 2013-04-29 16:51:02,528 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-41:job-57) Checking pool: 1 for volume allocation
> [Vol[26|vm=null|DATADISK]], maxSize : 1759218630656, totalAllocatedSize :
> 108885410816, askingSize : 21474836480, allocated disable threshold: 0.85
> 2013-04-29 16:51:02,530 DEBUG [cloud.storage.VolumeManagerImpl]
> (Job-Executor-41:job-57) Trying to create
> org.apache.cloudstack.storage.volume.VolumeObject@28b8ef9e on
> org.apache.cloudstack.storage.datastore.DefaultPrimaryDataStore@57b82f5
> 2013-04-29 16:51:02,566 DEBUG [agent.transport.Request]
> (Job-Executor-41:job-57) Seq 1-1019093539: Sending { Cmd , MgmtId:
> 73143235720, via: 1, Ver: v1, Flags: 100111,
> [{"storage.CreateCommand":{"volId":26,"pool":{"id":1,"uuid":"ba45e9e1-5b6f-3005-a920-00c02a73d9e1","host":"10.102.192.100","path":"/cpg_vol/sailaja/masterxenps","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":21474836480,"tags":[],"type":"DATADISK","name":"VolumefromsnapshotofROOT15","useLocalStorage":false,"recreatable":true,"diskOfferingId":1,"volumeId":26},"templateUrl":"c2f7de45-83c8-40a8-9937-a450b0d8660a","wait":0}}]
> }
> 2013-04-29 16:51:02,577 DEBUG [agent.transport.Request]
> (Job-Executor-41:job-57) Seq 1-1019093539: Executing: { Cmd , MgmtId:
> 73143235720, via: 1, Ver: v1, Flags: 100111,
> [{"storage.CreateCommand":{"volId":26,"pool":{"id":1,"uuid":"ba45e9e1-5b6f-3005-a920-00c02a73d9e1","host":"10.102.192.100","path":"/cpg_vol/sailaja/masterxenps","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":21474836480,"tags":[],"type":"DATADISK","name":"VolumefromsnapshotofROOT15","useLocalStorage":false,"recreatable":true,"diskOfferingId":1,"volumeId":26},"templateUrl":"c2f7de45-83c8-40a8-9937-a450b0d8660a","wait":0}}]
> }
> 2013-04-29 16:51:02,592 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-343:null) Seq 1-1019093539: Executing request
> 2013-04-29 16:51:02,710 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) SR retrieved for ba45e9e1-5b6f-3005-a920-00c02a73d9e1
> 2013-04-29 16:51:02,726 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) Checking ba45e9e1-5b6f-3005-a920-00c02a73d9e1 or SR
> 527d8f70-7760-6381-04bf-2d7f86c7f037 on
> XS[40d72111-4e51-4bda-9d2a-65de0f1bebb5-10.102.192.13]
> 2013-04-29 16:51:02,809 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-04-29 16:51:03,772 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) Succesfully created VDI for
> com.cloud.agent.api.storage.CreateCommand. Uuid =
> 2f8bfe2f-3cf4-4924-899d-0409c776430b
> 2013-04-29 16:51:03,773 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-343:null) Seq 1-1019093539: Response Received:
> 2013-04-29 16:51:03,773 DEBUG [agent.transport.Request]
> (DirectAgent-343:null) Seq 1-1019093539: Processing: { Ans: , MgmtId:
> 73143235720, via: 1, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"volume":{"id":26,"name":"VolumefromsnapshotofROOT15","mountPoint":"/cp
[jira] [Commented] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695973#comment-13695973 ] Rayees Namathponnan commented on CLOUDSTACK-2927: - Submitted Patch https://reviews.apache.org/r/12184/ > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI, Packaging >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Priority: Blocker > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- 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
[jira] [Commented] (CLOUDSTACK-2276) NPE while attaching the volume to the instance which is created from ROOT Disk Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695970#comment-13695970
]
ASF subversion and git services commented on CLOUDSTACK-2276:
-
Commit 661e32b3e2ddff253acf83749738b3bc0d7e7509 in branch
refs/heads/master-6-17-stable from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=661e32b ]
CLOUDSTACK-2276: NPE while attaching the volume to the instance which is
created from ROOT Disk Snapshot
Storage pool id was not getting set while creating volume from snapshot. Fix is
to set the storage pool id.
> NPE while attaching the volume to the instance which is created from ROOT
> Disk Snapshot
> ---
>
> Key: CLOUDSTACK-2276
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2276
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Koushik Das
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Setup: Advanced Networking Zone with Xen 6.1 , MS -RHEL 6.3
> Steps:
> 1. Deploy instance as ROOT admin
> 2. Create the snapshot from this instance ROOT disk
> 3. Create Volume from this snapshot
> 4. Try to attach this volume to the instance .
> Observation:
> NPE while attaching the volume to the instance which is created from ROOT
> Disk Snapshot
> 2013-04-29 16:51:02,412 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===END=== 10.144.6.19 -- GET
> command=attachVolume&id=3c8487fd-a30f-42d6-bc14-e19ec6c4090c&virtualMachineId=cc2a94bb-bdf0-4d36-9f2c-a501c75f53dd&response=json&sessionkey=50KnW0aaOd0wvF2hspe71pXsfqI%3D&_=1367234593280
> 2013-04-29 16:51:02,450 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-41:job-57) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-57
> 2013-04-29 16:51:02,528 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-41:job-57) Checking pool: 1 for volume allocation
> [Vol[26|vm=null|DATADISK]], maxSize : 1759218630656, totalAllocatedSize :
> 108885410816, askingSize : 21474836480, allocated disable threshold: 0.85
> 2013-04-29 16:51:02,530 DEBUG [cloud.storage.VolumeManagerImpl]
> (Job-Executor-41:job-57) Trying to create
> org.apache.cloudstack.storage.volume.VolumeObject@28b8ef9e on
> org.apache.cloudstack.storage.datastore.DefaultPrimaryDataStore@57b82f5
> 2013-04-29 16:51:02,566 DEBUG [agent.transport.Request]
> (Job-Executor-41:job-57) Seq 1-1019093539: Sending { Cmd , MgmtId:
> 73143235720, via: 1, Ver: v1, Flags: 100111,
> [{"storage.CreateCommand":{"volId":26,"pool":{"id":1,"uuid":"ba45e9e1-5b6f-3005-a920-00c02a73d9e1","host":"10.102.192.100","path":"/cpg_vol/sailaja/masterxenps","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":21474836480,"tags":[],"type":"DATADISK","name":"VolumefromsnapshotofROOT15","useLocalStorage":false,"recreatable":true,"diskOfferingId":1,"volumeId":26},"templateUrl":"c2f7de45-83c8-40a8-9937-a450b0d8660a","wait":0}}]
> }
> 2013-04-29 16:51:02,577 DEBUG [agent.transport.Request]
> (Job-Executor-41:job-57) Seq 1-1019093539: Executing: { Cmd , MgmtId:
> 73143235720, via: 1, Ver: v1, Flags: 100111,
> [{"storage.CreateCommand":{"volId":26,"pool":{"id":1,"uuid":"ba45e9e1-5b6f-3005-a920-00c02a73d9e1","host":"10.102.192.100","path":"/cpg_vol/sailaja/masterxenps","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":21474836480,"tags":[],"type":"DATADISK","name":"VolumefromsnapshotofROOT15","useLocalStorage":false,"recreatable":true,"diskOfferingId":1,"volumeId":26},"templateUrl":"c2f7de45-83c8-40a8-9937-a450b0d8660a","wait":0}}]
> }
> 2013-04-29 16:51:02,592 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-343:null) Seq 1-1019093539: Executing request
> 2013-04-29 16:51:02,710 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) SR retrieved for ba45e9e1-5b6f-3005-a920-00c02a73d9e1
> 2013-04-29 16:51:02,726 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) Checking ba45e9e1-5b6f-3005-a920-00c02a73d9e1 or SR
> 527d8f70-7760-6381-04bf-2d7f86c7f037 on
> XS[40d72111-4e51-4bda-9d2a-65de0f1bebb5-10.102.192.13]
> 2013-04-29 16:51:02,809 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-04-29 16:51:03,772 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-343:null) Succesfully created VDI for
> com.cloud.agent.api.storage.CreateCommand. Uuid =
> 2f8bfe2f-3cf4-4924-899d-0409c776430b
> 2013-04-29 16:51:03,773 DEBUG [agent.
[jira] [Commented] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695958#comment-13695958
]
Fang Wang commented on CLOUDSTACK-3237:
---
Which version of MS you are testing with?
1. the observation I got, I used an older version of CS before the Object Store
code is in;
2. I am testing the newer MS version with the object store in, the path problem
we saw may have different behavior.
> [vmware][SM] Migrate volume is failing when there are snapshots for that
> volume
> ---
>
> Key: CLOUDSTACK-3237
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3237
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
> Environment: vmware,
>Reporter: Srikanteswararao Talluri
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: mgmt_27.log.zip
>
>
> Steps to reproduce:
> 1. create a VM
> 2. take snapshot of root volume of VM
> 3. migrate root volume to a suitable storage pool
> ===START=== 10.101.255.87 -- GET
> command=findStoragePoolsForMigration&id=f7c12988-61a8-49dc-a5d3-cd8653744a8e&response=json&sessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D&_=1372333879848
> 2013-06-27 22:46:36,408 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (catalina-exec-14:null) LocalStoragePoolAllocator trying to find storage pool
> to fit the vm
> 2013-06-27 22:46:36,410 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2013-06-27 22:46:36,410 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> Looking for pools in dc: 1 pod:1 cluster:1
> 2013-06-27 22:46:36,419 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 1
> 2013-06-27 22:46:36,419 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> StoragePool is in avoid set, skipping this pool
> 2013-06-27 22:46:36,421 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 3
> 2013-06-27 22:46:36,429 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool 3 for storage, totalSize:
> 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable
> threshold: 0.85
> 2013-06-27 22:46:36,461 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool: 3 for volume allocation
> [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize :
> 23622320128, askingSize : 0, allocated disable threshold: 0.85
> 2013-06-27 22:46:36,464 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 5
> 2013-06-27 22:46:36,471 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool 5 for storage, totalSize:
> 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable
> threshold: 0.85
> 2013-06-27 22:46:36,492 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool: 5 for volume allocation
> [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize :
> 35433480192, askingSize : 0, allocated disable threshold: 0.85
> 2013-06-27 22:46:36,492 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> FirstFitStoragePoolAllocator returning 2 suitable storage pools
> 2013-06-27 22:46:36,506 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
> ===END=== 10.101.255.87 -- GET
> command=findStoragePoolsForMigration&id=f7c12988-61a8-49dc-a5d3-cd8653744a8e&response=json&sessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D&_=1372333879848
> 2013-06-27 22:46:39,967 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-9:null) Ping from 4
> 2013-06-27 22:46:40,804 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 3-10940: Processing Seq 3-10940: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-06-27 22:46:40,813 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 3-10940: Sending Seq 3-10940: { Ans: ,
> MgmtId: 7566222426160, via: 3, Ver: v1, Flags: 100010,
> [{"AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-06-27 22:46:41,091 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
> ===START=== 10.101.255.87 -- GET
> command=migrateVolume&livemigrate=true&storageid
[jira] [Updated] (CLOUDSTACK-3286) [VPC] [UI] Unable to choose between VpcVirtualRouter and Netscaler as LB Provider while creating network offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan updated CLOUDSTACK-3286: Attachment: CS3286.png Attached screenshot > [VPC] [UI] Unable to choose between VpcVirtualRouter and Netscaler as LB > Provider while creating network offering > - > > Key: CLOUDSTACK-3286 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3286 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Hypervisor: Xen server >Reporter: Sowmya Krishnan > Fix For: 4.2.0 > > Attachments: CS3286.png > > > Unable to choose Netscaler as the service provider for LB when I choose Load > Balancer Type as Public LB from the UI. Although both options Netscaler and > VpcVirtualRouter are available it always defaults to VpcVirtualRouter even if > I try to choose Netscaler. > Steps: > = > 1. Create Network Offering > 2. Choose VPC > 3. Select Load balancer provider as Public LB > 4. Try to choose service provider for LB as Netscaler -- 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
[jira] [Commented] (CLOUDSTACK-3082) System VMs are failed to start with Xen 6.2.0( Failing to create VIF's)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695955#comment-13695955 ] ASF subversion and git services commented on CLOUDSTACK-3082: - Commit 9e4b4a707f433d30c4513926cbdbb352d527ed55 in branch refs/heads/master-6-17-stable from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9e4b4a7 ] CLOUDSTACK-3082: System VMs are failed to start with Xen 6.2.0( Failing to create VIF's) > System VMs are failed to start with Xen 6.2.0( Failing to create VIF's) > --- > > Key: CLOUDSTACK-3082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3082 > 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: Sharad Yadav >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.2013-06-19.gz > > -- 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
[jira] [Created] (CLOUDSTACK-3286) [VPC] [UI] Unable to choose between VpcVirtualRouter and Netscaler as LB Provider while creating network offering
Sowmya Krishnan created CLOUDSTACK-3286: --- Summary: [VPC] [UI] Unable to choose between VpcVirtualRouter and Netscaler as LB Provider while creating network offering Key: CLOUDSTACK-3286 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3286 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Hypervisor: Xen server Reporter: Sowmya Krishnan Fix For: 4.2.0 Unable to choose Netscaler as the service provider for LB when I choose Load Balancer Type as Public LB from the UI. Although both options Netscaler and VpcVirtualRouter are available it always defaults to VpcVirtualRouter even if I try to choose Netscaler. Steps: = 1. Create Network Offering 2. Choose VPC 3. Select Load balancer provider as Public LB 4. Try to choose service provider for LB as Netscaler -- 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
[jira] [Commented] (CLOUDSTACK-3082) System VMs are failed to start with Xen 6.2.0( Failing to create VIF's)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695952#comment-13695952 ] ASF subversion and git services commented on CLOUDSTACK-3082: - Commit 1659ee225c936b074bae1ede955194f60c546c02 in branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1659ee2 ] CLOUDSTACK-3082: System VMs are failed to start with Xen 6.2.0( Failing to create VIF's) > System VMs are failed to start with Xen 6.2.0( Failing to create VIF's) > --- > > Key: CLOUDSTACK-3082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3082 > 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: Sharad Yadav >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.2013-06-19.gz > > -- 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
[jira] [Commented] (CLOUDSTACK-3215) Cannot Deploy VM when using S3 object store without NFS Cache
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695937#comment-13695937 ] ASF subversion and git services commented on CLOUDSTACK-3215: - Commit 58f9202818ffe78f3cd6748fc8710433d11bd5a2 in branch refs/heads/master from [~dlaffe...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=58f9202 ] CLOUDSTACK-3215: Cannot Deploy VM when using S3 object store without NFS Cache Signed-off-by: Edison Su > Cannot Deploy VM when using S3 object store without NFS Cache > - > > Key: CLOUDSTACK-3215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0, Future > Environment: Tested with Windows development environment, Hyper-V > hypervisor. However, the problem appears to be more general. >Reporter: Donal Lafferty > > This scenario arises when S3 is used for secondary storage, but no NFS cache > is added. > Tested on Master. May affect 4.2.0 as well. > Cause: AncientDataMotionStrategy.needCacheStorage does not allow for > CloudStack to deployed without NFS and without an image cache. -- 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
[jira] [Commented] (CLOUDSTACK-3266) Failed to delete Anti affinitygroup for the first time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695932#comment-13695932 ] Alena Prokharchyk commented on CLOUDSTACK-3266: --- Looks like a UI bug to me - it doesn't pass the ID of the group to delete > Failed to delete Anti affinitygroup for the first time > --- > > Key: CLOUDSTACK-3266 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3266 > 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: Sailaja Mada > Attachments: apilog.log, deleteAntiAff.png, management-server.log > > > Setup : Advanced Networking Zone - VMWARE > Steps: > 1. Have one instance deployed with enw user account > 2. later create Anti affinitygroup 1 > 3. Tried to delete it from UI > It failed saying: > 2013-06-28 14:37:18,594 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) > ===END=== 10.144.6.19 -- GET > command=deleteAffinityGroup&response=json&sessionkey=cAlesfWeL1LC7v5VBrAi%2B%2FiRJ%2F8%3D&_=1372410634034 > 2013-06-28 14:37:18,595 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > for job-91 > 2013-06-28 14:37:18,620 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Unexpected exception while executing > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd > com.cloud.exception.InvalidParameterValueException: Either the affinity group > Id or group name must be specified to delete the group > at > org.apache.cloudstack.affinity.AffinityGroupServiceImpl.deleteAffinityGroup(AffinityGroupServiceImpl.java:147) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.affinitygroup.DeleteAffinityGroupCmd.execute(DeleteAffinityGroupCmd.java:125) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > 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-06-28 14:37:18,620 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-113:job-91) Complete async job-91, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Either the affinity group Id or > group name must be specified to delete the group > 5. Again tried deleting the second group. > Then it deleted the group. (Attached UI and 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
[jira] [Commented] (CLOUDSTACK-3238) creating template from snapshot fails in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695930#comment-13695930
]
Fang Wang commented on CLOUDSTACK-3238:
---
After the object store code is in, this function needs to be pulled in and
rewritten.
> creating template from snapshot fails in vmware
> ---
>
> Key: CLOUDSTACK-3238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3238
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
>Affects Versions: 4.2.0
> Environment: vmware advanced zone with cluster level primary storage
>Reporter: shweta agarwal
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloud.out, management-server.zip
>
>
> Repro steps:
> Create a VM
> create a snapshot of root disk of the VM
> Create a template from the backed up snapshot
> Bug:
> hittting exception:
> 2013-06-27 17:16:10,912 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) submit async job-371, details: AsyncJobVO {id:371,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 228, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"u7fuCDtJanfTR6ObPknZNoA9z6c\u003d","ctxUserId":"2","httpmethod":"GET","osTypeId":"9e1b6a5c-d98f-11e2-95e7-0682fe17","isPublic":"false","response":"json","id":"228","displayText":"admin","snapshotid":"045d12f4-257b-4c28-b975-1b594fd9b2a6","passwordEnabled":"false","name":"admin","_":"1372333569675","ctxAccountId":"2","ctxStartEventId":"1426"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7159676928023,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-27 17:16:10,915 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.146.0.12 -- GET
> command=createTemplate&response=json&sessionkey=u7fuCDtJanfTR6ObPknZNoA9z6c%3D&snapshotid=045d12f4-257b-4c28-b975-1b594fd9b2a6&name=admin&displayText=admin&osTypeId=9e1b6a5c-d98f-11e2-95e7-0682fe17&isPublic=false&passwordEnabled=false&_=1372333569675
> 2013-06-27 17:16:10,980 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-371
> 2013-06-27 17:16:11,186 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-56:job-371) Failed to create
> templatejava.lang.NullPointerException
> 2013-06-27 17:16:11,265 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.lang.NullPointerException
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1770)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-06-27 17:16:11,268 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Complete async job-371, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Failed to create
> templatejava.lang.NullPointerException
> 2013-06-27 17:16:11,270 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-422:null) Seq 1-646158771: Response Received:
> 2013-06-27 17:16:11,271 DEBUG [agent.transport.Request]
> (StatsCollector-2:null) Seq 1-646158771: Received: { Ans: , MgmtId:
> 7159676928023, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-06-27 17:16:11,283 DEBUG [agent.manager.DirectAgentAttache] (DirectA
> Attaching MS log and ssvm logs for the same
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
[jira] [Commented] (CLOUDSTACK-3237) [vmware][SM] Migrate volume is failing when there are snapshots for that volume
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695928#comment-13695928
]
Fang Wang commented on CLOUDSTACK-3237:
---
There is an issue for volume migration for a snapshot volume, a volume created
from a snapshot.
I tried your scenerio, if I do a simple snapshot, then migration, it works ok;
1. take a snapshot of a root volume;
2. migrate the vol; -- this work ok;
3. take a snapshot again;
4. migrate -- this will fail; the reason is after the third step, the
original ROOT disk no longer in the expected directory.
The DB path is incorrect.
> [vmware][SM] Migrate volume is failing when there are snapshots for that
> volume
> ---
>
> Key: CLOUDSTACK-3237
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3237
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
> Environment: vmware,
>Reporter: Srikanteswararao Talluri
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: mgmt_27.log.zip
>
>
> Steps to reproduce:
> 1. create a VM
> 2. take snapshot of root volume of VM
> 3. migrate root volume to a suitable storage pool
> ===START=== 10.101.255.87 -- GET
> command=findStoragePoolsForMigration&id=f7c12988-61a8-49dc-a5d3-cd8653744a8e&response=json&sessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D&_=1372333879848
> 2013-06-27 22:46:36,408 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (catalina-exec-14:null) LocalStoragePoolAllocator trying to find storage pool
> to fit the vm
> 2013-06-27 22:46:36,410 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2013-06-27 22:46:36,410 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> Looking for pools in dc: 1 pod:1 cluster:1
> 2013-06-27 22:46:36,419 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 1
> 2013-06-27 22:46:36,419 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> StoragePool is in avoid set, skipping this pool
> 2013-06-27 22:46:36,421 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 3
> 2013-06-27 22:46:36,429 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool 3 for storage, totalSize:
> 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable
> threshold: 0.85
> 2013-06-27 22:46:36,461 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool: 3 for volume allocation
> [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize :
> 23622320128, askingSize : 0, allocated disable threshold: 0.85
> 2013-06-27 22:46:36,464 DEBUG
> [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-14:null)
> Checking if storage pool is suitable, name: null ,poolId: 5
> 2013-06-27 22:46:36,471 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool 5 for storage, totalSize:
> 590228480, usedBytes: 3490243883008, usedPct: 0.5913377617779474, disable
> threshold: 0.85
> 2013-06-27 22:46:36,492 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Checking pool: 5 for volume allocation
> [Vol[4|vm=4|ROOT]], maxSize : 1180456960, totalAllocatedSize :
> 35433480192, askingSize : 0, allocated disable threshold: 0.85
> 2013-06-27 22:46:36,492 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-14:null)
> FirstFitStoragePoolAllocator returning 2 suitable storage pools
> 2013-06-27 22:46:36,506 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
> ===END=== 10.101.255.87 -- GET
> command=findStoragePoolsForMigration&id=f7c12988-61a8-49dc-a5d3-cd8653744a8e&response=json&sessionkey=dfd5NAw2qEmBOi3931kcin3eZtQ%3D&_=1372333879848
> 2013-06-27 22:46:39,967 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-9:null) Ping from 4
> 2013-06-27 22:46:40,804 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 3-10940: Processing Seq 3-10940: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-06-27 22:46:40,813 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-11:null) SeqA 3-10940: Sending Seq 3-10940: { Ans: ,
> MgmtId: 7566222426160, via: 3, Ver: v1, Flags: 100010,
> [{"AgentControlAnswer":{"result":true,"
[jira] [Commented] (CLOUDSTACK-3284) [GSLB] GSLBRule state stuck in "Add" if there is anyting wrong happens during the assignToGloabalLBRule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695913#comment-13695913 ] venkata swamybabu budumuru commented on CLOUDSTACK-3284: Same is the case with REVOKE state. (1) Try to delete GSLB rule while the GSLB provider is not reachable Observations: (i) It will fail to cleanup and it leaves the rule in Revoke state forever. > [GSLB] GSLBRule state stuck in "Add" if there is anyting wrong happens during > the assignToGloabalLBRule > --- > > Key: CLOUDSTACK-3284 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3284 > 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 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Minor > Fix For: 4.2.0 > > > Steps to reproduce: > 1. Have latest CS setup with at least 2 advanced zones. > 2. Enable each zone with Netscaler with GSLB > 3. As a non-ROOT domain user, create a GSLB rule > 4. assign one LB rule (using VR) from zone1. > 5. assign another LB rule from another zone2. > Observations: > (i) second LB rule assignment failed with the following error "Failed to > configure GSLB rule in the zone" > (ii) When the above operations failed, the state of the LB rule just stuck in > "Add" state. -- 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
[jira] [Commented] (CLOUDSTACK-3278) In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695909#comment-13695909 ] ASF subversion and git services commented on CLOUDSTACK-3278: - Commit 281e70e9010974559a0aa0b7834798b4613b24d3 in branch refs/heads/4.1 from [~htrippaers] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=281e70e ] CLOUDSTACK-3278 Add the 410 to 411 upgrade to the PremiumDatabaseUpgradeChecker Can someone hand me a brown paper bag. > In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1 > > > Key: CLOUDSTACK-3278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.1 > Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build >Reporter: Ryan Lei >Assignee: Hugo Trippaers >Priority: Blocker > Fix For: 4.1.1 > > > Use git 4.1 branch to build non-OSS from source with the following commands: > (1) Put the necessary jars in deps/ > (2) Run deps/install-non-oss.sh with success > (3) $ mvn clean install -DskipTests=true -Dnonoss > (4) $ mvn -P developer -pl developer -Ddeploydb > (5) $ mvn -pl :cloud-client-ui jetty:run > Then I get these DB version errors which made jetty quit: > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker encryptionSecretKeyChecker > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker databaseIntegrityChecker > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to > check for database integrity. > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database > integrity check > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker managementServerNode > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker premiumDatabaseUpgradeChecker > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to > check for database upgrade. > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 > Code Version = 4.1.1-SNAPSHOT > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must > be performed from 4.0.0 to 4.1.1-SNAPSHOT > ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade > version is actually at 4.1.0 but our management server code version is at > 4.1.1-SNAPSHOT > ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check > failed. Refuse to startup > In MySQL, the 'version' table has only one entry whose value is 4.0.0. > Manually modifying the value to 4.1.1 led to other exceptions. Looks like > CloudStack "forgets" to upgrade the database. > However, the OSS build works fine. Jetty does run Upgrade40to41 and > Upgrade410to411 in the log. The 'version' table has three entries. > mysql> select * from version; > ++-+-+--+ > | id | version | updated | step | > ++-+-+--+ > | 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete | > | 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete | > | 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete | > ++-+-+--+ > The non-OSS build with the 4.1.0 source code release works fine, too. -- 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
[jira] [Assigned] (CLOUDSTACK-3139) TemplateServiceImpl.handleTemplateSync does not take the sec storage.proxy settings into account resulting in download errors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su reassigned CLOUDSTACK-3139: - Assignee: edison su > TemplateServiceImpl.handleTemplateSync does not take the sec storage.proxy > settings into account resulting in download errors > - > > Key: CLOUDSTACK-3139 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3139 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Hugo Trippaers >Assignee: edison su >Priority: Blocker > > The following bit of code tries to get the template size from an http or > https connection. If the secondary storage is behind a proxy this fails with > the error below. > > _resourceLimitMgr.checkResourceLimit(_accountMgr.getAccount(accountId), > > com.cloud.configuration.Resource.ResourceType.secondary_storage, > tmpltInfo.getSize() - > UriUtils.getRemoteSize(tmplt.getUrl())); > 2013-06-22 13:17:31,265 ERROR [agent.manager.AgentManagerImpl] > (AgentConnectTaskPool-3:null) Monitor DownloadListener says there is an error > in the connect process for 5 due to null > java.lang.NumberFormatException: null > at java.lang.Long.parseLong(Long.java:404) > at java.lang.Long.parseLong(Long.java:483) > at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113) > at > org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:328) > at > com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) > at > com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:583) > at > com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1083) > at > com.cloud.agent.manager.AgentManagerImpl.access$1(AgentManagerImpl.java:1075) > at > com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1158) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) -- 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
[jira] [Updated] (CLOUDSTACK-3139) TemplateServiceImpl.handleTemplateSync does not take the sec storage.proxy settings into account resulting in download errors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers updated CLOUDSTACK-3139: --- Priority: Blocker (was: Major) > TemplateServiceImpl.handleTemplateSync does not take the sec storage.proxy > settings into account resulting in download errors > - > > Key: CLOUDSTACK-3139 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3139 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Hugo Trippaers >Priority: Blocker > > The following bit of code tries to get the template size from an http or > https connection. If the secondary storage is behind a proxy this fails with > the error below. > > _resourceLimitMgr.checkResourceLimit(_accountMgr.getAccount(accountId), > > com.cloud.configuration.Resource.ResourceType.secondary_storage, > tmpltInfo.getSize() - > UriUtils.getRemoteSize(tmplt.getUrl())); > 2013-06-22 13:17:31,265 ERROR [agent.manager.AgentManagerImpl] > (AgentConnectTaskPool-3:null) Monitor DownloadListener says there is an error > in the connect process for 5 due to null > java.lang.NumberFormatException: null > at java.lang.Long.parseLong(Long.java:404) > at java.lang.Long.parseLong(Long.java:483) > at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113) > at > org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:328) > at > com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307) > at > com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:583) > at > com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1083) > at > com.cloud.agent.manager.AgentManagerImpl.access$1(AgentManagerImpl.java:1075) > at > com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1158) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) -- 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
[jira] [Created] (CLOUDSTACK-3285) UCS: Need support for HTTP redirects and HTTPS Certificate handling
Parth Jagirdar created CLOUDSTACK-3285: -- Summary: UCS: Need support for HTTP redirects and HTTPS Certificate handling Key: CLOUDSTACK-3285 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3285 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UCS Affects Versions: 4.2.0 Environment: Master; Basic Bare-metal and UCS Reporter: Parth Jagirdar Priority: Critical By default UCS has HTTP to HTTPs redirect enabled. At which point, addUcsManager fails with following error. 2013-06-28 14:19:57,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) ===START=== 10.217.252.127 -- GET command=addUcsManager&zoneid=d92cc843-8c50-4f57-9c07-1041bf859f8d&name=ucsmanager&url=10.223.184.2&username=admin&response=json&sessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D&_=1372454390205 2013-06-28 14:19:57,256 WARN [cloudstack.api.AddUcsManagerCmd] (catalina-exec-20:null) Exception: com.cloud.utils.exception.CloudRuntimeException: Cannot get cookie at com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:174) at com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:179) at com.cloud.ucs.manager.UcsManagerImpl.discoverBlades(UcsManagerImpl.java:123) at com.cloud.ucs.manager.UcsManagerImpl.addUcsManager(UcsManagerImpl.java:154) at org.apache.cloudstack.api.AddUcsManagerCmd.execute(AddUcsManagerCmd.java:68) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) 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: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:2268) 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) Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 302 Found Found The document has moved https://10.223.184.2/nuova";>here. at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:50) at com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:166) ... 26 more Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 302 Found Found The document has moved https://10.223.184.2/nuova";>here. at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:41) ... 27 more 2013-06-28 14:19:57,257 INFO [cloud.api.ApiServer] (catalina-exec-20:null) Cannot get cookie 2013-06-28 14:19:57,258 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) ===END=== 10.217.252.127 -- GET command=addUcsManager&zoneid=d92cc843-8c50-4f57-9c07-1041bf859f8d&name=ucsmanager&url=10.223.184.2&username=admin&response=json&sessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D&_=1372454390205 2013-06-28 14:20:02,479 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector is running... 2013-06-28 14:20:02,481 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) VmStatsCollector is running... 2013-06-28 14:20:02,482 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) StorageCollector is running... 2013-06-28 14:20:13,761 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is not ready to launch secondary storage VM yet However if we disable
[jira] [Resolved] (CLOUDSTACK-2327) cloudstack-setup-agent does not properly detect openvswitch and fails if the brcompat driver is not loaded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers resolved CLOUDSTACK-2327. Resolution: Fixed Assignee: Hiroaki Kawai (was: Hugo Trippaers) > cloudstack-setup-agent does not properly detect openvswitch and fails if the > brcompat driver is not loaded > -- > > Key: CLOUDSTACK-2327 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2327 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.1.0 >Reporter: Hugo Trippaers >Assignee: Hiroaki Kawai > > isBridge fails in the networking configuration is brcompat is not loaded. > Cloudstack-setup-agent should have a parameter that specifies if you want to > use traditional bridge or openvswitch -- 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
[jira] [Resolved] (CLOUDSTACK-728) Add support for Nicira NVP to VmWare hypervisor orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers resolved CLOUDSTACK-728. --- Resolution: Fixed Fix Version/s: (was: Future) 4.2.0 > Add support for Nicira NVP to VmWare hypervisor orchestration > - > > Key: CLOUDSTACK-728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-728 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers > Fix For: 4.2.0 > > -- 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
[jira] [Resolved] (CLOUDSTACK-2326) OvsVifDriver should not use the vlan tag if the libvirt version is lower van 0.10.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers resolved CLOUDSTACK-2326. Resolution: Fixed commit f74e635225c1241054985c8911be59233b747f60 Author: Hugo Trippaers Date: Thu Jun 20 08:11:05 2013 -0700 Setting the required version of libvirt to 10.0 for the openvswitch support. This version actually supports setting the vlan tag on an interface. > OvsVifDriver should not use the vlan tag if the libvirt version is lower van > 0.10.x > --- > > Key: CLOUDSTACK-2326 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2326 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0, 4.2.0 >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers > > As a workaround the fake bridges can be used -- 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
[jira] [Updated] (CLOUDSTACK-715) Make VmWare plugin a oss component
[ https://issues.apache.org/jira/browse/CLOUDSTACK-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Huang updated CLOUDSTACK-715: -- Remaining Estimate: 0h Original Estimate: 0h Summary: Make VmWare plugin a oss component (was: Make VmWare plugin a non-oss component) > Make VmWare plugin a oss component > -- > > Key: CLOUDSTACK-715 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-715 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.0.0 >Reporter: Alex Huang > Original Estimate: 0h > Remaining Estimate: 0h > > The VmWare component is using a client stub library from vmware and the > client stub library is not licensed appropriately. That's my understanding > of why vmware component is not in the apache release. We should just go > against the wsdl that vmware releases. This is a bug to track against that > effort. If my understanding is not right, please update this bug. > I assigned it to Kelven for this comments. -- 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
[jira] [Updated] (CLOUDSTACK-3110) [VMWARE]NPE while adding primary storage(scope=cluster) with Invalid hostname
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati updated CLOUDSTACK-3110:
Status: Ready To Review (was: In Progress)
> [VMWARE]NPE while adding primary storage(scope=cluster) with Invalid hostname
> --
>
> Key: CLOUDSTACK-3110
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3110
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Venkata Siva Vijayendra Bhamidipati
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Steps:
> 1.Configure Advanced Zone with VMWARe
> 2. Add Additional primary storage at the cluster level by providing wrong
> Server Name.
> Observation:
> 1. It failed to add the primary storage but there is NPE during this.
> 2013-06-21 12:03:09,788 DEBUG [agent.manager.AgentManagerImpl]
> (catalina-exec-14:null) Details from executing class
> com.cloud.agent.api.CreateStoragePoolCommand: success
> 2013-06-21 12:03:09,790 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Adding pool null to host 1
> 2013-06-21 12:03:09,796 DEBUG [agent.transport.Request]
> (catalina-exec-14:null) Seq 1-503583091: Sending { Cmd , MgmtId:
> 94838926819810, via: 1, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}}]
> }
> 2013-06-21 12:03:09,796 DEBUG [agent.transport.Request]
> (catalina-exec-14:null) Seq 1-503583091: Executing: { Cmd , MgmtId:
> 94838926819810, via: 1, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}}]
> }
> 2013-06-21 12:03:09,796 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-236:null) Seq 1-503583091: Executing request
> 2013-06-21 12:03:09,797 INFO [vmware.resource.VmwareResource]
> (DirectAgent-236:10.102.192.18) Executing resource ModifyStoragePoolCommand:
> {"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}
> 2013-06-21 12:03:10,854 INFO [vmware.mo.HostMO]
> (DirectAgent-236:10.102.192.18) Creation of NFS datastore on vCenter failed.
> Details: vCenter API trace - mountDatastore(). target MOR: host-1086, vmfs:
> false, poolHost: newdps1, poolHostPort: 2049, poolPath:
> /cpg_vol/sailaja/newdummyps1, poolUuid: 67132a340414332ca00ae1196f6b27ee.
> Exception mesg: An error occurred during host configuration.
> 2013-06-21 12:03:10,854 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-236:10.102.192.18) ModifyStoragePoolCommand failed due to
> Exception: java.lang.Exception
> Message: Creation of NFS datastore on vCenter failed.
> java.lang.Exception: Creation of NFS datastore on vCenter failed.
> at
> com.cloud.hypervisor.vmware.mo.HostMO.mountDatastore(HostMO.java:765)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3727)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:426)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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-06-21 12:03:10,856 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-236:null) Seq 1-503583091: Response Received:
> 2013-06-21 12:03:10,857 DEBUG [agent.transport.Request]
> (DirectAgent-236:nu
[jira] [Commented] (CLOUDSTACK-3110) [VMWARE]NPE while adding primary storage(scope=cluster) with Invalid hostname
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695863#comment-13695863
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3110:
-
Fix posted to https://reviews.apache.org/r/12180/ for review.
> [VMWARE]NPE while adding primary storage(scope=cluster) with Invalid hostname
> --
>
> Key: CLOUDSTACK-3110
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3110
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Venkata Siva Vijayendra Bhamidipati
> Fix For: 4.2.0
>
> Attachments: apilog.log, management-server.log
>
>
> Steps:
> 1.Configure Advanced Zone with VMWARe
> 2. Add Additional primary storage at the cluster level by providing wrong
> Server Name.
> Observation:
> 1. It failed to add the primary storage but there is NPE during this.
> 2013-06-21 12:03:09,788 DEBUG [agent.manager.AgentManagerImpl]
> (catalina-exec-14:null) Details from executing class
> com.cloud.agent.api.CreateStoragePoolCommand: success
> 2013-06-21 12:03:09,790 DEBUG [cloud.storage.StorageManagerImpl]
> (catalina-exec-14:null) Adding pool null to host 1
> 2013-06-21 12:03:09,796 DEBUG [agent.transport.Request]
> (catalina-exec-14:null) Seq 1-503583091: Sending { Cmd , MgmtId:
> 94838926819810, via: 1, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}}]
> }
> 2013-06-21 12:03:09,796 DEBUG [agent.transport.Request]
> (catalina-exec-14:null) Seq 1-503583091: Executing: { Cmd , MgmtId:
> 94838926819810, via: 1, Ver: v1, Flags: 100011,
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}}]
> }
> 2013-06-21 12:03:09,796 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-236:null) Seq 1-503583091: Executing request
> 2013-06-21 12:03:09,797 INFO [vmware.resource.VmwareResource]
> (DirectAgent-236:10.102.192.18) Executing resource ModifyStoragePoolCommand:
> {"add":true,"pool":{"id":2,"uuid":"67132a34-0414-332c-a00a-e1196f6b27ee","host":"newdps1","path":"/cpg_vol/sailaja/newdummyps1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//67132a34-0414-332c-a00a-e1196f6b27ee","wait":0}
> 2013-06-21 12:03:10,854 INFO [vmware.mo.HostMO]
> (DirectAgent-236:10.102.192.18) Creation of NFS datastore on vCenter failed.
> Details: vCenter API trace - mountDatastore(). target MOR: host-1086, vmfs:
> false, poolHost: newdps1, poolHostPort: 2049, poolPath:
> /cpg_vol/sailaja/newdummyps1, poolUuid: 67132a340414332ca00ae1196f6b27ee.
> Exception mesg: An error occurred during host configuration.
> 2013-06-21 12:03:10,854 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-236:10.102.192.18) ModifyStoragePoolCommand failed due to
> Exception: java.lang.Exception
> Message: Creation of NFS datastore on vCenter failed.
> java.lang.Exception: Creation of NFS datastore on vCenter failed.
> at
> com.cloud.hypervisor.vmware.mo.HostMO.mountDatastore(HostMO.java:765)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3727)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:426)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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-06-21 12:03:10,856 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-236:null) Seq 1-503583091: Response Receive
[jira] [Assigned] (CLOUDSTACK-669) Better VM Sync
[ https://issues.apache.org/jira/browse/CLOUDSTACK-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Huang reassigned CLOUDSTACK-669: - Assignee: Alex Huang (was: Kelven Yang) > Better VM Sync > -- > > Key: CLOUDSTACK-669 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-669 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Hari Kannan >Assignee: Alex Huang > Fix For: 4.2.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VMWare+Enhancements+-+Support+for+DRS+and+VM+HA -- 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
[jira] [Reopened] (CLOUDSTACK-2980) Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan reopened CLOUDSTACK-2980: - Basic zone setup failed after this fix , reverted by https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=e8b2d74a00348c25d6810d6e0078bfeb9d76cdea > Adding a VLAN range that overlaps with two existing ranges results in > inconsistent DB entries > - > > Key: CLOUDSTACK-2980 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2980 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Under PhysicalNetwork - Guest, Add 2 VLAN ranges - 360-369;380-385 > Then adding one new VLAN range, 367-383 results in the following 2 issues, > 1. The new range displayed in the UI is 360-383;380-385 > 2. In the DB 'op_dc_vnet_alloc' table every VLAN in the range 370-379 is > missing. This is because we are trying to add VLANs from 370-383 and since > the entries 380-383 are duplicates the DB insert throws an exception. -- 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
[jira] [Reopened] (CLOUDSTACK-2150) DB table entries of phisical network is not proper.Shows Duplicate entries.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan reopened CLOUDSTACK-2150: - Basic zone creation failed after this check-in, its check-in reverted already , https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=e8b2d74a00348c25d6810d6e0078bfeb9d76cdea > DB table entries of phisical network is not proper.Shows Duplicate entries. > - > > Key: CLOUDSTACK-2150 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2150 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Created a network with the vlan range 921-925;then added a Vlan range from > 930-934; > The db table entries shows correctly. > Then added the IP range from 921-934; then the db entries show the same range > twice ,as shown below. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-934;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) > Then deleted the range from 926 -934;then one entry is deleted in the table > but the second entry still shows 921-934.The below table explains the same. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-925;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) -- 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
[jira] [Created] (CLOUDSTACK-3284) [GSLB] GSLBRule state stuck in "Add" if there is anyting wrong happens during the assignToGloabalLBRule
venkata swamybabu budumuru created CLOUDSTACK-3284: -- Summary: [GSLB] GSLBRule state stuck in "Add" if there is anyting wrong happens during the assignToGloabalLBRule Key: CLOUDSTACK-3284 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3284 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 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Priority: Minor Fix For: 4.2.0 Steps to reproduce: 1. Have latest CS setup with at least 2 advanced zones. 2. Enable each zone with Netscaler with GSLB 3. As a non-ROOT domain user, create a GSLB rule 4. assign one LB rule (using VR) from zone1. 5. assign another LB rule from another zone2. Observations: (i) second LB rule assignment failed with the following error "Failed to configure GSLB rule in the zone" (ii) When the above operations failed, the state of the LB rule just stuck in "Add" state. -- 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
[jira] [Updated] (CLOUDSTACK-3282) [GSLB] Unable to add multiple LB rules to same GSLB rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-3282: --- Priority: Blocker (was: Critical) > [GSLB] Unable to add multiple LB rules to same GSLB rule > > > Key: CLOUDSTACK-3282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3282 > 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 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Blocker > Fix For: 4.2.0 > > > Steps to reproduce: > 1. Have latest CS setup with at least 2 advanced zones. > 2. Enable each zone with Netscaler with GSLB > 3. As a non-ROOT domain user, create a GSLB rule > 4. assign one LB rule (using VR) from zone1. > 5. assign another LB rule from another zone2. > Observations:- > (i) second LB rule assignment failed with the following error "Failed to > configure GSLB rule in the zone" > 013-06-28 21:15:11,570 DEBUG [agent.manager.AgentManagerImpl] > (Job-Executor-79:job-116) Details from executing class > com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply > GSLB configuration due to Resource already exists > 2013-06-28 21:15:11,570 DEBUG [network.element.NetscalerElement] > (Job-Executor-79:job-116) Unable to apply global load balancer rule to the > gslb service provider in zone 1 > 2013-06-28 21:15:11,570 WARN > [region.gslb.GlobalLoadBalancingRulesServiceImpl] (Job-Executor-79:job-116) > Failed to configure GSLB rul in the zone P[1:200] due to Resource > [DataCenter:1] is unreachable: Unable to apply global load balancer rule to > the gslb service provider in zone 1 > 2013-06-28 21:15:11,571 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-116) Unexpected exception while executing > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to configure GSLB rul > in the zone > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.applyGlobalLoadBalancerRuleConfig(GlobalLoadBalancingRulesServiceImpl.java:652) > at > org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:263) > at > org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-28 21:15:11,572 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-79:job-116) Complete async job-116, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Failed to configure GSLB rul in the > zone > 2013-06-28 21:15:11,588 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-79:job-116) Sync queue (21) is currently empty > (ii) Here is the snippet from Zone1 Netscaler which shows what commands > failed and resulted in this error. > Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : > UI CMD_EXECUTED 3842 0 : User nsroot - Remote_ip 10.147.59.194 - Command > "set gslb service cloud-gslb-service-cloudsite1-10.147.44.66-22 -IPAddress > 10.147.44.66 -publicIP 10.147.44.66 -publicPort 22 -cip DISABLED > -sitePersistence NONE -maxClient 0 -healthMonitor YES -maxBandwidth 0 > -downStateFlush DISABLED -maxAAAUsers 0 0.0.0.0 -monThreshold 0 -appflowLog > ENABLED" - Status "Success" > Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : > UI CMD_EXECUTED 3843 0 : User nsroot - Remote_ip 10.147.59.194 - Command > "bind gslb vserver cloud-gslb-vserver-hello.xyztelco.com -serviceName > cloud-gslb-service-cloudsite1-10.147.44.66-22 -weight 1 -devno 19759104" - > Status "ERROR: Resource already exists" > Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : > UI CMD_EXECUTED 3844 0 : User nsroot - Remote_ip 10.147.59.194 - Command > "add lb monitor cloud-monitor-10.147.44.66 TCP -resptimeoutThresh 0 -retries > 3 -failureRetries 0
[jira] [Resolved] (CLOUDSTACK-3278) In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers resolved CLOUDSTACK-3278. Resolution: Fixed commit b330f2aa909d7ddc387863e0806f71964f6d5f80 Author: Hugo Trippaers Date: Fri Jun 28 10:57:51 2013 -0700 CLOUDSTACK-3278 Add the 410 to 411 upgrade to the PremiumDatabaseUpgradeChecker > In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1 > > > Key: CLOUDSTACK-3278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.1 > Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build >Reporter: Ryan Lei >Assignee: Hugo Trippaers >Priority: Blocker > Fix For: 4.1.1 > > > Use git 4.1 branch to build non-OSS from source with the following commands: > (1) Put the necessary jars in deps/ > (2) Run deps/install-non-oss.sh with success > (3) $ mvn clean install -DskipTests=true -Dnonoss > (4) $ mvn -P developer -pl developer -Ddeploydb > (5) $ mvn -pl :cloud-client-ui jetty:run > Then I get these DB version errors which made jetty quit: > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker encryptionSecretKeyChecker > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker databaseIntegrityChecker > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to > check for database integrity. > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database > integrity check > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker managementServerNode > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker premiumDatabaseUpgradeChecker > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to > check for database upgrade. > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 > Code Version = 4.1.1-SNAPSHOT > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must > be performed from 4.0.0 to 4.1.1-SNAPSHOT > ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade > version is actually at 4.1.0 but our management server code version is at > 4.1.1-SNAPSHOT > ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check > failed. Refuse to startup > In MySQL, the 'version' table has only one entry whose value is 4.0.0. > Manually modifying the value to 4.1.1 led to other exceptions. Looks like > CloudStack "forgets" to upgrade the database. > However, the OSS build works fine. Jetty does run Upgrade40to41 and > Upgrade410to411 in the log. The 'version' table has three entries. > mysql> select * from version; > ++-+-+--+ > | id | version | updated | step | > ++-+-+--+ > | 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete | > | 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete | > | 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete | > ++-+-+--+ > The non-OSS build with the 4.1.0 source code release works fine, too. -- 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
[jira] [Created] (CLOUDSTACK-3283) System VM does not start on Hyper-V Server 2012
Donal Lafferty created CLOUDSTACK-3283: -- Summary: System VM does not start on Hyper-V Server 2012 Key: CLOUDSTACK-3283 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3283 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: Future Environment: Hyper-V hypervisor Reporter: Donal Lafferty The SystemVM is supposed to have Hyper-V drivers installed. A VM was created with the SystemVM image attached and started. Although CPU was stuck at 12%, the console displayed no text. It was impossible to login from the console. -- 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
[jira] [Created] (CLOUDSTACK-3282) [GSLB] Unable to add multiple LB rules to same GSLB rule
venkata swamybabu budumuru created CLOUDSTACK-3282: -- Summary: [GSLB] Unable to add multiple LB rules to same GSLB rule Key: CLOUDSTACK-3282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3282 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 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Priority: Critical Fix For: 4.2.0 Steps to reproduce: 1. Have latest CS setup with at least 2 advanced zones. 2. Enable each zone with Netscaler with GSLB 3. As a non-ROOT domain user, create a GSLB rule 4. assign one LB rule (using VR) from zone1. 5. assign another LB rule from another zone2. Observations:- (i) second LB rule assignment failed with the following error "Failed to configure GSLB rule in the zone" 013-06-28 21:15:11,570 DEBUG [agent.manager.AgentManagerImpl] (Job-Executor-79:job-116) Details from executing class com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply GSLB configuration due to Resource already exists 2013-06-28 21:15:11,570 DEBUG [network.element.NetscalerElement] (Job-Executor-79:job-116) Unable to apply global load balancer rule to the gslb service provider in zone 1 2013-06-28 21:15:11,570 WARN [region.gslb.GlobalLoadBalancingRulesServiceImpl] (Job-Executor-79:job-116) Failed to configure GSLB rul in the zone P[1:200] due to Resource [DataCenter:1] is unreachable: Unable to apply global load balancer rule to the gslb service provider in zone 1 2013-06-28 21:15:11,571 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-79:job-116) Unexpected exception while executing org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd com.cloud.utils.exception.CloudRuntimeException: Failed to configure GSLB rul in the zone at org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.applyGlobalLoadBalancerRuleConfig(GlobalLoadBalancingRulesServiceImpl.java:652) at org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:263) at org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-06-28 21:15:11,572 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-79:job-116) Complete async job-116, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to configure GSLB rul in the zone 2013-06-28 21:15:11,588 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-79:job-116) Sync queue (21) is currently empty (ii) Here is the snippet from Zone1 Netscaler which shows what commands failed and resulted in this error. Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : UI CMD_EXECUTED 3842 0 : User nsroot - Remote_ip 10.147.59.194 - Command "set gslb service cloud-gslb-service-cloudsite1-10.147.44.66-22 -IPAddress 10.147.44.66 -publicIP 10.147.44.66 -publicPort 22 -cip DISABLED -sitePersistence NONE -maxClient 0 -healthMonitor YES -maxBandwidth 0 -downStateFlush DISABLED -maxAAAUsers 0 0.0.0.0 -monThreshold 0 -appflowLog ENABLED" - Status "Success" Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : UI CMD_EXECUTED 3843 0 : User nsroot - Remote_ip 10.147.59.194 - Command "bind gslb vserver cloud-gslb-vserver-hello.xyztelco.com -serviceName cloud-gslb-service-cloudsite1-10.147.44.66-22 -weight 1 -devno 19759104" - Status "ERROR: Resource already exists" Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : UI CMD_EXECUTED 3844 0 : User nsroot - Remote_ip 10.147.59.194 - Command "add lb monitor cloud-monitor-10.147.44.66 TCP -resptimeoutThresh 0 -retries 3 -failureRetries 0 -alertRetries 0 -successRetries 1 -IPMapping 0.0.0.0 -state ENABLED -reverse NO -transparent NO -ipTunnel NO -tos NO -secure NO -devno 19791872" - Status "ERROR: Resource already exists" Jun 28 11:46:33 10.147.44.5 06/28/2013:11:46:33 GMT 0-PPE-0 : UI CMD_EXECUTED 3845 0 : User nsroot - Remote_ip 10.147.59.194 - Command "logout" - Status "Success" Jun
[jira] [Commented] (CLOUDSTACK-3260) [Automation] Volume attach and detach failed with null pointer exception in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695728#comment-13695728
]
ASF subversion and git services commented on CLOUDSTACK-3260:
-
Commit 75f98eea4e89c6cbbf0762ee13bac77229e86e3c in branch
refs/heads/master-6-17-stable from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75f98ee ]
CLOUDSTACK-3260 [Automation] Volume attach and detach failed with null pointer
exception in vmware
Log files shows multiple Exceptions where some of the NPE are observed when
file is non-existant file in datastore.
Fixing NullPointerExceptions seen while searching for file in datastore.
> [Automation] Volume attach and detach failed with null pointer exception in
> vmware
> --
>
> Key: CLOUDSTACK-3260
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3260
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
> Environment: Vmware
> Build from master_stable build
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3260.rar
>
>
> Regression test case
> ntegration.component.test_volumes.TestAttachDetachVolume.test_01_volume_attach_detach
> failed with null pointer exception
> 2013-06-27 20:12:45,487 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-500:null) Seq 1-94963056: Executing request
> 2013-06-27 20:12:45,487 INFO [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) Executing resource CreateCommand:
> {"volId":217,"pool":{
> "id":1,"uuid":"4faf04c2-6dd8-3025-b43f-65d32cc49d02","host":"10.223.110.232","path":"/export/home/automation/SC-CLOUD-QA03/primary1","port":2049,"type"
> :"NetworkFilesystem"},"diskCharacteristics":{"size":1073741824,"tags":[],"type":"DATADISK","name":"TestDiskServ","useLocalStorage":false,"recreatable":
> false,"diskOfferingId":107,"volumeId":217},"executeInSequence":false,"wait":0}
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO]
> (DirectAgent-500:10.223.250.130) find VM e5ed7f8bea2c499b94c74c9ff35ae23c on
> host
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO]
> (DirectAgent-500:10.223.250.130) load VM cache on host
> 2013-06-27 20:12:46,066 INFO [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) Destroy dummy VM after volume creation
> 2013-06-27 20:12:46,066 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) CreateCommand failed due to Exception:
> java.lang.NullPo
> interException
> Message: null
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4765)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 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:722)
> 2013-06-27 20:12:46,067 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-500:null) Seq 1-94963056: Response Received:
> 2013-06-27 20:12:46,067 DEBUG [agent.transport.Request]
> (DirectAgent-500:null) Seq 1-94963056: Processing: { Ans: , MgmtId:
> 90928106758026, via: 1, Ver: v1, Flags: 10,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> java.lang.Exception\nMessage: java.lang.NullPointerException\nStack:
> java.lang.Exception: java.lang.NullPointerException\n\tat
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4777)\n\tat
>
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)\n\tat
>
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)\n\tat
>
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)\n\tat
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.
[jira] [Commented] (CLOUDSTACK-3021) Test case TestServiceOfferingHierarchy failed; resource clean up should delete sub domain before delete main domain
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695724#comment-13695724
]
Rayees Namathponnan commented on CLOUDSTACK-3021:
-
Test case not executing after this fix
> Test case TestServiceOfferingHierarchy failed; resource clean up should
> delete sub domain before delete main domain
> ---
>
> Key: CLOUDSTACK-3021
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3021
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
>
> Failed below test case
> test/integration/component/test_accounts: TestServiceOfferingHierarchy
> Test case should cleanup, sub domain before deleting main domain
> Error in automation log
> Warning: Exception during cleanup : Execute cmd: asyncquery failed, due to:
> {errorcode : 530, errortext : u'Delete failed on domain Domain-O9IVMI (id:
> 55); Please make sure all users and sub domains have been removed from the
> domain before deleting'}
> Stacktrace
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 227, in
> run
> self.tearDown()
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 350, in
> tearDown
> self.teardownContext(ancestor)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 366, in
> teardownContext
> try_run(context, names)
> File "/usr/local/lib/python2.7/site-packages/nose/util.py", line 469, in
> try_run
> return func()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_accounts.py", line
> 771, in tearDownClass
> raise Exception("Warning: Exception during cleanup : %s" % e)
> Exception: Warning: Exception during cleanup : Execute cmd: asyncquery
> failed, due to: {errorcode : 530, errortext : u'Delete failed on domain
> Domain-O9IVMI (id: 55); Please make sure all users and sub domains have been
> removed from the domain before deleting'}
--
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
[jira] [Commented] (CLOUDSTACK-3279) Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695711#comment-13695711 ] ASF subversion and git services commented on CLOUDSTACK-3279: - Commit 869083f062db5e5467da401275a4c97f9e1a4368 in branch refs/heads/master-6-17-stable from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=869083f ] CLOUDSTACK-3279 Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware. Signed-off-by: Sateesh Chodapuneedi > Need mechanism to detect if hotadd for cpu/memory is supported per a specific > guest OS supported by VMware. > --- > > Key: CLOUDSTACK-3279 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3279 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi >Priority: Critical > Fix For: 4.2.0 > > > Vmware publishes a list for vmware guest os and their supported capabilities > for each vmware release. Example for guest OS Ubuntu 10.04 and ESX some > release 4.x we only support hot add of vcpu (and not hot add memory) > GuestOS Release > Ubuntu 10.04 Desktop > Supported Releases > ESX 4.1 U31, 2, 3, 4, 5, 6, 4.1 U21, 2, 3, 4, 5, 6, 4.1 U11, 2, 3, 4, 5, 6, > 4.12, 1, 6, 5, 4, 3 > Support Details > Hot Add vCPU etc > More info @ > http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf > Vmware says that the attributes hot add cpu and memory should be turned on > during deployment of vm (i.e. As part of deployvm api) so that in future the > user can dynamically scale cpu and memory(scale vm api). Now I wanted to > understand how to enforce this check in Cloudstack. The best would be Vmware > providing a method to check whether hot add cpu and memory is enabled for the > current GuestOS version in the vmware release. Need such mechanism. > This is related to dynamic scaling of cpu/memory in case of VMware > environments. -- 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
[jira] [Resolved] (CLOUDSTACK-2831) Automation : New mapping model for CloudStack zone and Vmware datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-2831. Resolution: Fixed > Automation : New mapping model for CloudStack zone and Vmware datacenter > - > > Key: CLOUDSTACK-2831 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2831 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > -- 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
[jira] [Reopened] (CLOUDSTACK-2831) Automation : New mapping model for CloudStack zone and Vmware datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reopened CLOUDSTACK-2831: > Automation : New mapping model for CloudStack zone and Vmware datacenter > - > > Key: CLOUDSTACK-2831 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2831 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > -- 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
[jira] [Commented] (CLOUDSTACK-3060) BVT test_routers.py test case failing in Vmware with connection error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695699#comment-13695699 ] ASF subversion and git services commented on CLOUDSTACK-3060: - Commit 2c8776341471d3785238c4446918264ddcd401a8 in branch refs/heads/master-6-17-stable from [~gauravaradhye] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2c87763 ] CLOUDSTACK-3060: condition for vmware while getting process status. Signed-off-by: Prasanna Santhanam (cherry picked from commit 1fc7aeaaea80e30651a47024cf928ff11fb29e9c) > BVT test_routers.py test case failing in Vmware with connection error > -- > > Key: CLOUDSTACK-3060 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3060 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.0 > Environment: Automation VMware >Reporter: Rayees Namathponnan >Assignee: Gaurav Aradhye >Priority: Blocker > Fix For: 4.2.0 > > > integration.smoke.test_routers.TestRouterServices.test_01_router_internal_basic > > integration.smoke.test_routers.TestRouterServices.test_02_router_internal_adv > integration.smoke.test_routers.TestRouterServices.test_04_restart_network_wo_cleanup > > integration.smoke.test_routers.TestRouterServices.test_10_network_gc > Test cases failed with error > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File "/data/Repo2/qa/cloudstack/test/integration/smoke/test_routers.py", > line 839, in test_10_network_gc > "Check state of the router after stopping all VMs associated" > File "/usr/local/lib/python2.7/unittest/case.py", line 494, in assertEqual > assertion_func(first, second, msg=msg) > File "/usr/local/lib/python2.7/unittest/case.py", line 487, in > _baseAssertEqual > raise self.failureException(msg) > Check state of the router after stopping all VMs associated -- 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
[jira] [Commented] (CLOUDSTACK-2254) Automation: Add automation for Affinity and Anti Affinity rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695698#comment-13695698 ] ASF subversion and git services commented on CLOUDSTACK-2254: - Commit 7bad7327236366b662518ed644aaad6fa4a3ac6b in branch refs/heads/master-6-17-stable from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7bad732 ] CLOUDSTACK-2254: Tests for Affinity and Anti Affinity rules TestCreateAffinityGroup TestListAffinityGroups TestDeleteAffinityGroups TestUpdateVMAffinityGroups TestDeployVMAffinityGroups TestAffinityGroupsAdminUser Signed-off-by: Prasanna Santhanam (cherry picked from commit 3c0c6cb0b3c21d08d88763b229c17f4b41c74145) > Automation: Add automation for Affinity and Anti Affinity rules > --- > > Key: CLOUDSTACK-2254 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2254 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Sudha Ponnaganti >Assignee: Girish Shilamkar > Fix For: 4.2.0 > > -- 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
[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695697#comment-13695697
]
ASF subversion and git services commented on CLOUDSTACK-1963:
-
Commit 93712c2715c540150b86efdcc8e02c8f7facd0dc in branch
refs/heads/master-6-17-stable from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=93712c2 ]
CLOUDSTACK-3074: include support for vmwaredc mapping to zone
vmware dc can be mapped to the zone after CLOUDSTACK-1963. include
support in marvin for adding the vmwaredc.
vmwaredc : {
name:
username:
vcenter:
password:
zoneid:
}
Will be sent during pod creation before cluster creation.
Signed-off-by: Prasanna Santhanam
(cherry picked from commit 9f4b7dcff896810e2276e02fa034de283964bf49)
Conflicts:
tools/marvin/marvin/configGenerator.py
Signed-off-by: Prasanna Santhanam
> New mapping model for CloudStack zone and Vmware datacenter
>
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here,
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel
--
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
[jira] [Commented] (CLOUDSTACK-3074) Automation framework need to be updated for adding DC to zone, in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695696#comment-13695696
]
ASF subversion and git services commented on CLOUDSTACK-3074:
-
Commit 93712c2715c540150b86efdcc8e02c8f7facd0dc in branch
refs/heads/master-6-17-stable from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=93712c2 ]
CLOUDSTACK-3074: include support for vmwaredc mapping to zone
vmware dc can be mapped to the zone after CLOUDSTACK-1963. include
support in marvin for adding the vmwaredc.
vmwaredc : {
name:
username:
vcenter:
password:
zoneid:
}
Will be sent during pod creation before cluster creation.
Signed-off-by: Prasanna Santhanam
(cherry picked from commit 9f4b7dcff896810e2276e02fa034de283964bf49)
Conflicts:
tools/marvin/marvin/configGenerator.py
Signed-off-by: Prasanna Santhanam
> Automation framework need to be updated for adding DC to zone, in vmware
>
>
> Key: CLOUDSTACK-3074
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3074
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
> Environment: Automation
>Reporter: Rayees Namathponnan
>Assignee: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> deployDataCenter.py need to update for adding DC to ZOne
--
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
[jira] [Resolved] (CLOUDSTACK-3255) [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not being passed from UI - inside a VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-3255. -- Resolution: Fixed After my check-in: http://localhost:8080/client/api?command=createAutoScaleVmProfile&response=json&sessionkey=I4hr0Zf1oKKmYLBKUtxcFZmGS6g%3D&zoneid=51451358-f434-4253-80b2-aef2d115b54d&serviceofferingid=ab0eb106-5f89-40ae-885c-342653043c93&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372446900858 > [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not > being passed from UI - inside a VPC > --- > > Key: CLOUDSTACK-3255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: latest master branch > Hypervisor: Xen server >Reporter: Sowmya Krishnan >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Autoscale is practically broken from UI since zone id is not being passed > while creating auto scale vm profile. > This is found while configuring Auto scale for a network tier inside a VPC. > For a non-VPC isolated network, autoscale configuration is working fine. > Since there are lot of configurations in autoscale and it's easier done > through the UI, this is critical. > Steps: > = > Create a VPC network with external LB > Create a network tier within the VPC with external LB offering provided by > Netscaler. > Acquire a public IP and configure autoscale with the IP > Input all required configurations for autoscale > Result: > Fails while creating auto scale VM profile due to missing zone id parameter. > Zone id has always been a required param for createAutoScaleVMProfile > Following are the logs > 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===START=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=jso > n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg > raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca > leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null) > Unable to execute API command autoscalevmprofile due to missing parameter > zoneid > 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > The same works fine while configuring in a non-VPC isolated network -- 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
[jira] [Commented] (CLOUDSTACK-3255) [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not being passed from UI - inside a VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695691#comment-13695691 ] ASF subversion and git services commented on CLOUDSTACK-3255: - Commit ab185fb2bf30b970e5d95d491a2003a550332d5c in branch refs/heads/master-6-17-stable from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ab185fb ] CLOUDSTACK-3255: UI > VPC section - IP Address - Load Balancing - autoscale - fix a bug that failed to get zoneid for createAutoScaleVmProfile API. > [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not > being passed from UI - inside a VPC > --- > > Key: CLOUDSTACK-3255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: latest master branch > Hypervisor: Xen server >Reporter: Sowmya Krishnan >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Autoscale is practically broken from UI since zone id is not being passed > while creating auto scale vm profile. > This is found while configuring Auto scale for a network tier inside a VPC. > For a non-VPC isolated network, autoscale configuration is working fine. > Since there are lot of configurations in autoscale and it's easier done > through the UI, this is critical. > Steps: > = > Create a VPC network with external LB > Create a network tier within the VPC with external LB offering provided by > Netscaler. > Acquire a public IP and configure autoscale with the IP > Input all required configurations for autoscale > Result: > Fails while creating auto scale VM profile due to missing zone id parameter. > Zone id has always been a required param for createAutoScaleVMProfile > Following are the logs > 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===START=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=jso > n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg > raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca > leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null) > Unable to execute API command autoscalevmprofile due to missing parameter > zoneid > 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > The same works fine while configuring in a non-VPC isolated network -- 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
[jira] [Commented] (CLOUDSTACK-3255) [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not being passed from UI - inside a VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695692#comment-13695692 ] ASF subversion and git services commented on CLOUDSTACK-3255: - Commit dfb2e1d4f5bbb4e1be0160a4a65dc324ead27fbb in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dfb2e1d ] CLOUDSTACK-3255: UI > VPC section - IP Address - Load Balancing - autoscale - fix a bug that failed to get zoneid for createAutoScaleVmProfile API. > [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not > being passed from UI - inside a VPC > --- > > Key: CLOUDSTACK-3255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: latest master branch > Hypervisor: Xen server >Reporter: Sowmya Krishnan >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Autoscale is practically broken from UI since zone id is not being passed > while creating auto scale vm profile. > This is found while configuring Auto scale for a network tier inside a VPC. > For a non-VPC isolated network, autoscale configuration is working fine. > Since there are lot of configurations in autoscale and it's easier done > through the UI, this is critical. > Steps: > = > Create a VPC network with external LB > Create a network tier within the VPC with external LB offering provided by > Netscaler. > Acquire a public IP and configure autoscale with the IP > Input all required configurations for autoscale > Result: > Fails while creating auto scale VM profile due to missing zone id parameter. > Zone id has always been a required param for createAutoScaleVMProfile > Following are the logs > 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===START=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=jso > n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg > raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca > leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null) > Unable to execute API command autoscalevmprofile due to missing parameter > zoneid > 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > The same works fine while configuring in a non-VPC isolated network -- 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
[jira] [Created] (CLOUDSTACK-3281) StartCommand carries VolumeObjectTO with format field of NULL
Donal Lafferty created CLOUDSTACK-3281:
--
Summary: StartCommand carries VolumeObjectTO with format field of
NULL
Key: CLOUDSTACK-3281
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3281
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: Future
Environment: Hyper-V cluster
Reporter: Donal Lafferty
Disk image format is missing from VolumeObjectTO in StartCommand. Not clear
whether Hypervisor needs to set this in the CopyCmdAnswer returned when the
volume is created, if the hypervisor is never to use the format when looking up
an image or if there is a bug in the system.
Sample command:
{
"vm": {
"id": 2,
"name": "v-2-VM",
"type": "ConsoleProxy",
"cpus": 1,
"minSpeed": 500,
"maxSpeed": 500,
"minRam": 1073741824,
"maxRam": 1073741824,
"arch": "i686",
"os": "Debian GNU/Linux 5.0 (32-bit)",
"bootArgs": " template=domP type=consoleproxy host=10.80.3.83 port=8250
name=v-2-VM premium=true zone=1 pod=1 guid=Proxy.2 proxy_vm=2
disable_rp_filter=true eth2ip=10.70.176.125 eth2mask=255.255.240.0
gateway=10.70.176.1 eth0ip=169.254.1.121 eth0mask=255.255.0.0
eth1ip=10.70.176.96 eth1mask=255.255.240.0 mgmtcidr=10.80.2.0/23
localgw=10.70.176.1 internaldns1=10.70.176.118 internaldns2=10.70.160.66
dns1=4.4.4.4",
"rebootOnCrash": false,
"enableHA": false,
"limitCpuUse": false,
"enableDynamicallyScaleVm": false,
"vncPassword": "ce12c56d3290de94",
"params": {},
"uuid": "89384857-b45d-47c0-8c7e-b011b0fcb118",
"disks": [
{
"data": {
"org.apache.cloudstack.storage.to.VolumeObjectTO": {
"uuid": "35a079e4-7767-47d1-8629-72d32c866a08",
"volumeType": "ROOT",
"dataStore": {
"org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
"uuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
"id": 1,
"poolType": "Filesystem",
"host": "10.70.176.29",
"path": "E:\\Disks\\",
"port": 0
}
},
"name": "ROOT-2",
"size": 140616708,
"volumeId": 2,
"vmName": "v-2-VM",
"accountId": 1,
"id": 2
}
},
"diskSeq": 0,
"type": "ROOT"
}
],
"nics": [
{
"deviceId": 2,
"networkRateMbps": -1,
"defaultNic": true,
"uuid": "022f8487-aba2-441b-85dd-3a68c3614fec",
"ip": "10.70.176.125",
"netmask": "255.255.240.0",
"gateway": "10.70.176.1",
"mac": "06:9d:26:00:00:0c",
"dns1": "4.4.4.4",
"broadcastType": "Vlan",
"type": "Public",
"broadcastUri": "vlan://untagged",
"isolationUri": "vlan://untagged",
"isSecurityGroupEnabled": false
},
{
"deviceId": 0,
"networkRateMbps": -1,
"defaultNic": false,
"uuid": "4fbb6713-de1e-4930-a944-6b5685c4ac62",
"ip": "169.254.1.121",
"netmask": "255.255.0.0",
"gateway": "169.254.0.1",
"mac": "0e:00:a9:fe:01:79",
"broadcastType": "LinkLocal",
"type": "Control",
"isSecurityGroupEnabled": false
},
{
"deviceId": 1,
"networkRateMbps": -1,
"defaultNic": false,
"uuid": "2eeefa17-429e-47a5-bf41-bfa4742b712c",
"ip": "10.70.176.96",
"netmask": "255.255.240.0",
"gateway": "10.70.176.1",
"mac": "06:26:ae:00:00:07",
"broadcastType": "Native",
"type": "Management",
"isSecurityGroupEnabled": false
}
]
},
"hostIp": "10.70.176.29",
"executeInSequence": false,
"contextMap": {},
"wait": 0
}
--
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
[jira] [Created] (CLOUDSTACK-3280) [GSLB] Clean up of lb monitors is not happening as part of deleteGSLBRule
venkata swamybabu budumuru created CLOUDSTACK-3280: -- Summary: [GSLB] Clean up of lb monitors is not happening as part of deleteGSLBRule Key: CLOUDSTACK-3280 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3280 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 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Steps to reproduce: 1.Have a latest CS setup with at least 2 advanced zone running XenServer 2. Add Netscaler and enable it for GSLB in each zone 3. As a non-ROOT domain user, create a GSLB rule 4. assign one LB rule (using VR) from any of the zone. 5. delete GSLB rule Observations:- (i) GSLB rule get delete successfully without any issues from CloudStack (ii) but, on NetScaler, deleteGSLBRule is not cleaning the lb monitor that was created automatically as part of step:4 Here is the snippet from NS. # show lb monitor TCP 20) Name...:cloud-monitor-10.147.44.66 Type..: TCP State: ENABLED Attaching all the logs along with db dump from mgmt server -- 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
[jira] [Created] (CLOUDSTACK-3279) Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware.
Sateesh Chodapuneedi created CLOUDSTACK-3279: Summary: Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware. Key: CLOUDSTACK-3279 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3279 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Vmware publishes a list for vmware guest os and their supported capabilities for each vmware release. Example for guest OS Ubuntu 10.04 and ESX some release 4.x we only support hot add of vcpu (and not hot add memory) GuestOS Release Ubuntu 10.04 Desktop Supported Releases ESX 4.1 U31, 2, 3, 4, 5, 6, 4.1 U21, 2, 3, 4, 5, 6, 4.1 U11, 2, 3, 4, 5, 6, 4.12, 1, 6, 5, 4, 3 Support Details Hot Add vCPU etc More info @ http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf Vmware says that the attributes hot add cpu and memory should be turned on during deployment of vm (i.e. As part of deployvm api) so that in future the user can dynamically scale cpu and memory(scale vm api). Now I wanted to understand how to enforce this check in Cloudstack. The best would be Vmware providing a method to check whether hot add cpu and memory is enabled for the current GuestOS version in the vmware release. Need such mechanism. This is related to dynamic scaling of cpu/memory in case of VMware environments. -- 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
[jira] [Assigned] (CLOUDSTACK-2994) [Automation][Object_Store] Failed to attach ISO to vm
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su reassigned CLOUDSTACK-2994:
-
Assignee: edison su
> [Automation][Object_Store] Failed to attach ISO to vm
> -
>
> Key: CLOUDSTACK-2994
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2994
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: ISO
>Affects Versions: 4.2.0
> Environment: Object_Store branch build
> KVM
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
>
> BVT test
> integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
> failed due to this
> Steps to reproduce
> Step 1 : Add iSO http://people.apache.org/~tsp/dummy.iso
> Step 2 : Create new VM
> Step 3 : Attach ISO to VM
> Attach ISO failedwith below error
> 2013-06-13 10:27:36,215 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===START=== 10.216.51.168 -- GET
> command=attachIso&virtualmachineid=b50c968b-92c2-44fb-b82a-de6891f77a5b&id=6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36&response=json&sessionkey=ThbZI1AXRGDVsDUBZS5Iq9ZvFhw%3D&_=1371133809191
> 2013-06-13 10:27:36,218 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-332:null) Ping from 1
> 2013-06-13 10:27:36,249 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-35:job-279) Executing
> org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-279
> 2013-06-13 10:27:36,253 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-279, details: AsyncJobVO {id:279,
> userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId:
> null, cmd: org.apache.cloudstack.api.command.user.iso.AttachIsoCmd,
> cmdOriginator: null, cmdInfo:
> {"id":"6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36","response":"json","sessionkey":"ThbZI1AXRGDVsDUBZS5Iq9ZvFhw\u003d","virtualmachineid":"b50c968b-92c2-44fb-b82a-de6891f77a5b","ctxUserId":"2","httpmethod":"GET","_":"1371133809191","ctxAccountId":"2","ctxStartEventId":"1239"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 29066118877352,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-13 10:27:36,255 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
> ===END=== 10.216.51.168 -- GET
> command=attachIso&virtualmachineid=b50c968b-92c2-44fb-b82a-de6891f77a5b&id=6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36&response=json&sessionkey=ThbZI1AXRGDVsDUBZS5Iq9ZvFhw%3D&_=1371133809191
> 2013-06-13 10:27:36,286 DEBUG [agent.transport.Request]
> (Job-Executor-35:job-279) Seq 4-1568017056: Sending { Cmd , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/210/210-2-726db663-1f18-3551-9358-1124895169dc.iso","origUrl":"http://people.apache.org/~tsp/dummy.iso","uuid":"6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36","id":210,"format":"ISO","accountId":2,"checksum":"b11099d68763f87ee90eab7af1d4dd1e","hvm":true,"displayText":"iso","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary","_role":"Image"}},"name":"210-2-726db663-1f18-3551-9358-1124895169dc"}},"type":"ISO"},"vmName":"i-2-88-VM","wait":0}}]
> }
> 2013-06-13 10:27:36,488 DEBUG [agent.transport.Request]
> (AgentManager-Handler-6:null) Seq 4-1568017056: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"org.libvirt.LibvirtException:
> Domain not found: no domain with matching uuid
> '3670-3193-38c2-a567-ff66dfeb8e66'","wait":0}}] }
> 2013-06-13 10:27:36,489 DEBUG [agent.transport.Request]
> (Job-Executor-35:job-279) Seq 4-1568017056: Received: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 10, { Answer } }
> 2013-06-13 10:27:36,489 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-35:job-279) Details from executing class
> org.apache.cloudstack.storage.command.AttachCommand:
> org.libvirt.LibvirtException: Domain not found: no domain with matching uuid
> '3670-3193-38c2-a567-ff66dfeb8e66'
> 2013-06-13 10:27:36,494 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-35:job-279) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.iso.AttachIsoCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach iso
> at
> com.cloud.template.TemplateManagerImpl.attachIso(TemplateManagerImpl.java:975)
> at
> com.cloud.utils.component.ComponentInsta
[jira] [Assigned] (CLOUDSTACK-3238) creating template from snapshot fails in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su reassigned CLOUDSTACK-3238:
-
Assignee: edison su
> creating template from snapshot fails in vmware
> ---
>
> Key: CLOUDSTACK-3238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3238
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
>Affects Versions: 4.2.0
> Environment: vmware advanced zone with cluster level primary storage
>Reporter: shweta agarwal
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloud.out, management-server.zip
>
>
> Repro steps:
> Create a VM
> create a snapshot of root disk of the VM
> Create a template from the backed up snapshot
> Bug:
> hittting exception:
> 2013-06-27 17:16:10,912 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) submit async job-371, details: AsyncJobVO {id:371,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 228, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"u7fuCDtJanfTR6ObPknZNoA9z6c\u003d","ctxUserId":"2","httpmethod":"GET","osTypeId":"9e1b6a5c-d98f-11e2-95e7-0682fe17","isPublic":"false","response":"json","id":"228","displayText":"admin","snapshotid":"045d12f4-257b-4c28-b975-1b594fd9b2a6","passwordEnabled":"false","name":"admin","_":"1372333569675","ctxAccountId":"2","ctxStartEventId":"1426"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7159676928023,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-06-27 17:16:10,915 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.146.0.12 -- GET
> command=createTemplate&response=json&sessionkey=u7fuCDtJanfTR6ObPknZNoA9z6c%3D&snapshotid=045d12f4-257b-4c28-b975-1b594fd9b2a6&name=admin&displayText=admin&osTypeId=9e1b6a5c-d98f-11e2-95e7-0682fe17&isPublic=false&passwordEnabled=false&_=1372333569675
> 2013-06-27 17:16:10,980 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-371
> 2013-06-27 17:16:11,186 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-56:job-371) Failed to create
> templatejava.lang.NullPointerException
> 2013-06-27 17:16:11,265 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.lang.NullPointerException
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1770)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-06-27 17:16:11,268 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-56:job-371) Complete async job-371, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Failed to create
> templatejava.lang.NullPointerException
> 2013-06-27 17:16:11,270 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-422:null) Seq 1-646158771: Response Received:
> 2013-06-27 17:16:11,271 DEBUG [agent.transport.Request]
> (StatsCollector-2:null) Seq 1-646158771: Received: { Ans: , MgmtId:
> 7159676928023, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-06-27 17:16:11,283 DEBUG [agent.manager.DirectAgentAttache] (DirectA
> Attaching MS log and ssvm logs for the same
--
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
[jira] [Resolved] (CLOUDSTACK-3146) Extract Template command fails with Unsupported Command: storage.CreateEntityDownloadURLCommand on SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-3146. -- Resolution: Cannot Reproduce > Extract Template command fails with Unsupported Command: > storage.CreateEntityDownloadURLCommand on SSVM > --- > > Key: CLOUDSTACK-3146 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3146 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > > The extraction of templates is failing with the following exception: > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,326 ERROR > [datastore.driver.CloudStackImageStoreDriverImpl] (Job-Executor-21:job-153) > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c > 8be3d2095.vhd on ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,343 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.template.ExtractTemplateCm > d > Jun 23 11:55:37 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to create a link for > entity at template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.datastore.driver.CloudStackImageStoreDriverImpl.createEntityExtractUrl(CloudStackImageStoreDriverImpl.java:72) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.ImageStoreImpl.createEntityExtractUrl(ImageStoreImpl.java:194) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:495) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:415) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:129) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 11:55:37 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,346 DEBUG > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Complete async > job-153, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand -- 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
[jira] [Commented] (CLOUDSTACK-3146) Extract Template command fails with Unsupported Command: storage.CreateEntityDownloadURLCommand on SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695615#comment-13695615 ] Min Chen commented on CLOUDSTACK-3146: -- This automated test passed on xenserver BVT, and results are inconsistent in KVM and XCP BVT (respectively passed once and failed once), seems like either an environment issue or testcase issue. Manually I could not reproduce this. Resolve this issue for now. Prasanna, please reopen this bug when you see this issue again and attach management server log and systemvm log along with this. > Extract Template command fails with Unsupported Command: > storage.CreateEntityDownloadURLCommand on SSVM > --- > > Key: CLOUDSTACK-3146 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3146 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > > The extraction of templates is failing with the following exception: > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,326 ERROR > [datastore.driver.CloudStackImageStoreDriverImpl] (Job-Executor-21:job-153) > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c > 8be3d2095.vhd on ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,343 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.template.ExtractTemplateCm > d > Jun 23 11:55:37 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to create a link for > entity at template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.datastore.driver.CloudStackImageStoreDriverImpl.createEntityExtractUrl(CloudStackImageStoreDriverImpl.java:72) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.ImageStoreImpl.createEntityExtractUrl(ImageStoreImpl.java:194) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:495) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:415) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:129) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 11:55:37 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,346 DEBUG > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Complete async > job-153, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand -- 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
[jira] [Assigned] (CLOUDSTACK-3144) [Automation] Deletion of templates failing. Fails to find image store housing template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-3144: Assignee: Min Chen > [Automation] Deletion of templates failing. Fails to find image store housing > template > -- > > Key: CLOUDSTACK-3144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: 427.tar.bz2, dbdump.tar.bz2 > > > Deletion of templates during account GC fails with the following exception > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,698 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: EVSCLU due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[205-VHD-2ed8c0aee-7437-3c19-b3ac-cec513d806c0 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 12:22:07 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,701 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: Public template-CS42CN due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[206-VHD-247c4a699-73e3-32e7-b69e-8ea4858ef389 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:22:07 cloudstack-centos63 at > java
[jira] [Commented] (CLOUDSTACK-3278) In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695611#comment-13695611 ] ASF subversion and git services commented on CLOUDSTACK-3278: - Commit b330f2aa909d7ddc387863e0806f71964f6d5f80 in branch refs/heads/4.1 from [~htrippaers] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b330f2a ] CLOUDSTACK-3278 Add the 410 to 411 upgrade to the PremiumDatabaseUpgradeChecker > In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1 > > > Key: CLOUDSTACK-3278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.1 > Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build >Reporter: Ryan Lei >Assignee: Hugo Trippaers >Priority: Blocker > Fix For: 4.1.1 > > > Use git 4.1 branch to build non-OSS from source with the following commands: > (1) Put the necessary jars in deps/ > (2) Run deps/install-non-oss.sh with success > (3) $ mvn clean install -DskipTests=true -Dnonoss > (4) $ mvn -P developer -pl developer -Ddeploydb > (5) $ mvn -pl :cloud-client-ui jetty:run > Then I get these DB version errors which made jetty quit: > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker encryptionSecretKeyChecker > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker databaseIntegrityChecker > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to > check for database integrity. > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database > integrity check > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker managementServerNode > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker premiumDatabaseUpgradeChecker > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to > check for database upgrade. > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 > Code Version = 4.1.1-SNAPSHOT > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must > be performed from 4.0.0 to 4.1.1-SNAPSHOT > ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade > version is actually at 4.1.0 but our management server code version is at > 4.1.1-SNAPSHOT > ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check > failed. Refuse to startup > In MySQL, the 'version' table has only one entry whose value is 4.0.0. > Manually modifying the value to 4.1.1 led to other exceptions. Looks like > CloudStack "forgets" to upgrade the database. > However, the OSS build works fine. Jetty does run Upgrade40to41 and > Upgrade410to411 in the log. The 'version' table has three entries. > mysql> select * from version; > ++-+-+--+ > | id | version | updated | step | > ++-+-+--+ > | 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete | > | 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete | > | 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete | > ++-+-+--+ > The non-OSS build with the 4.1.0 source code release works fine, too. -- 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
[jira] [Resolved] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-2385.
-
Resolution: Fixed
Patch committed by Devdeep to master in commit #
78922589bbdc7914b9d4ce3b97a9fcf03d4b7b57
> template download fails with Unexpected failure in Vmware.
> --
>
> Key: CLOUDSTACK-2385
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip, templatediff1
>
>
> I registered a template with the parameters extractable=yes,Public=yes and
> Featured=yes.
> Then later I tried to download the template from the UI.
> It shows an error message in the UI as below:"PrepareExtractTemplate: Failed
> to create OVA for template extraction"
> and in the management server log below are the error messages observed.
> "2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===START=== 10.146.0.136 -- GET
> command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
> 2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 206, cmd:
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"21e135aa-4df9-4818-b89c-99c64de5ee70","sessionkey":"xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d","ctxUserId":"2","zoneid":"58e1ce4d-fb5c-48c4-948f-408c969deae0","httpmethod":"GET","_":"1367993227024","ctxAccountId":"2","ctxStartEventId":"322","mode":"HTTP_DOWNLOAD"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===END=== 10.146.0.136 -- GET
> command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
> 2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-26:job-78) Executing
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
> 2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
> (Job-Executor-26:job-78) Failed to create OVA for template
> Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
> non-existing.
> 2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-26:job-78) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate:
> Failed to create OVA for template extraction.
> at
> com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
> at
> com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 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-05-08 17:03:14,907 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-26:job-78) Complete async job-78, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: PrepareExtractTemplate: Failed to
> create OVA for template
[jira] [Updated] (CLOUDSTACK-3144) [Automation] Deletion of templates failing. Fails to find image store housing template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3144: --- Attachment: dbdump.tar.bz2 db dump from latest xenserver run where the delete template fails > [Automation] Deletion of templates failing. Fails to find image store housing > template > -- > > Key: CLOUDSTACK-3144 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3144 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > Attachments: 427.tar.bz2, dbdump.tar.bz2 > > > Deletion of templates during account GC fails with the following exception > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,698 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: EVSCLU due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[205-VHD-2ed8c0aee-7437-3c19-b3ac-cec513d806c0 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 12:22:07 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 12:22:07 cloudstack-centos63 local0: 2013-06-23 19:22:07,701 WARN > [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to delete > template while removing account: Public template-CS42CN due to: > Jun 23 12:22:07 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to find image store > to delete template Tmpl[206-VHD-247c4a699-73e3-32e7-b69e-8ea4858ef389 > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:208) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:750) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jun 23 12:22:07 cloudstack-centos63 at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:22:07 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolEx
[jira] [Commented] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695603#comment-13695603
]
ASF subversion and git services commented on CLOUDSTACK-2385:
-
Commit 78922589bbdc7914b9d4ce3b97a9fcf03d4b7b57 in branch refs/heads/master
from [~vijayendrabvs]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7892258 ]
CLOUDSTACK-2385: template download fails with Unexpected failure in Vmware.
Description:
Putting in fix to allow download of guest VM templates that are available
across zones.
> template download fails with Unexpected failure in Vmware.
> --
>
> Key: CLOUDSTACK-2385
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Assignee: Venkata Siva Vijayendra Bhamidipati
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip, templatediff1
>
>
> I registered a template with the parameters extractable=yes,Public=yes and
> Featured=yes.
> Then later I tried to download the template from the UI.
> It shows an error message in the UI as below:"PrepareExtractTemplate: Failed
> to create OVA for template extraction"
> and in the management server log below are the error messages observed.
> "2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===START=== 10.146.0.136 -- GET
> command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
> 2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 206, cmd:
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"21e135aa-4df9-4818-b89c-99c64de5ee70","sessionkey":"xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d","ctxUserId":"2","zoneid":"58e1ce4d-fb5c-48c4-948f-408c969deae0","httpmethod":"GET","_":"1367993227024","ctxAccountId":"2","ctxStartEventId":"322","mode":"HTTP_DOWNLOAD"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===END=== 10.146.0.136 -- GET
> command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
> 2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-26:job-78) Executing
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
> 2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
> (Job-Executor-26:job-78) Failed to create OVA for template
> Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
> non-existing.
> 2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-26:job-78) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate:
> Failed to create OVA for template extraction.
> at
> com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
> at
> com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>
[jira] [Assigned] (CLOUDSTACK-3278) In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers reassigned CLOUDSTACK-3278: -- Assignee: Hugo Trippaers > In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1 > > > Key: CLOUDSTACK-3278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.1 > Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build >Reporter: Ryan Lei >Assignee: Hugo Trippaers >Priority: Blocker > Fix For: 4.1.1 > > > Use git 4.1 branch to build non-OSS from source with the following commands: > (1) Put the necessary jars in deps/ > (2) Run deps/install-non-oss.sh with success > (3) $ mvn clean install -DskipTests=true -Dnonoss > (4) $ mvn -P developer -pl developer -Ddeploydb > (5) $ mvn -pl :cloud-client-ui jetty:run > Then I get these DB version errors which made jetty quit: > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker encryptionSecretKeyChecker > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker databaseIntegrityChecker > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to > check for database integrity. > INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database > integrity check > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker managementServerNode > INFO [utils.component.ComponentContext] (Timer-2:) Running > SystemIntegrityChecker premiumDatabaseUpgradeChecker > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to > check for database upgrade. > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 > Code Version = 4.1.1-SNAPSHOT > INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must > be performed from 4.0.0 to 4.1.1-SNAPSHOT > ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade > version is actually at 4.1.0 but our management server code version is at > 4.1.1-SNAPSHOT > ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check > failed. Refuse to startup > In MySQL, the 'version' table has only one entry whose value is 4.0.0. > Manually modifying the value to 4.1.1 led to other exceptions. Looks like > CloudStack "forgets" to upgrade the database. > However, the OSS build works fine. Jetty does run Upgrade40to41 and > Upgrade410to411 in the log. The 'version' table has three entries. > mysql> select * from version; > ++-+-+--+ > | id | version | updated | step | > ++-+-+--+ > | 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete | > | 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete | > | 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete | > ++-+-+--+ > The non-OSS build with the 4.1.0 source code release works fine, too. -- 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
[jira] [Commented] (CLOUDSTACK-3255) [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not being passed from UI - inside a VPC
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695598#comment-13695598
]
Sowmya Krishnan commented on CLOUDSTACK-3255:
-
http://10.102.192.203:8080/client/api?command=createAutoScaleVmProfile&response=json&sessionkey=B0ShS30gucmISfNnb0A9xaADNc8%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372441380451
{ "autoscalevmprofileresponse" :
{"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"Unable to
execute API command autoscalevmprofile due to missing parameter zoneid"} }
> [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not
> being passed from UI - inside a VPC
> ---
>
> Key: CLOUDSTACK-3255
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.2.0
> Environment: latest master branch
> Hypervisor: Xen server
>Reporter: Sowmya Krishnan
>Priority: Critical
> Fix For: 4.2.0
>
>
> Autoscale is practically broken from UI since zone id is not being passed
> while creating auto scale vm profile.
> This is found while configuring Auto scale for a network tier inside a VPC.
> For a non-VPC isolated network, autoscale configuration is working fine.
> Since there are lot of configurations in autoscale and it's easier done
> through the UI, this is critical.
> Steps:
> =
> Create a VPC network with external LB
> Create a network tier within the VPC with external LB offering provided by
> Netscaler.
> Acquire a public IP and configure autoscale with the IP
> Input all required configurations for autoscale
> Result:
> Fails while creating auto scale VM profile due to missing zone id parameter.
> Zone id has always been a required param for createAutoScaleVMProfile
> Following are the logs
> 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
> ===START=== 10.252.121.25 -- GET
> command=createAutoScaleVmProfile&response=jso
> n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg
> raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca
> leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719
> 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null)
> Unable to execute API command autoscalevmprofile due to missing parameter
> zoneid
> 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null)
> ===END=== 10.252.121.25 -- GET
> command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719
> The same works fine while configuring in a non-VPC isolated network
--
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
[jira] [Assigned] (CLOUDSTACK-3255) [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not being passed from UI - inside a VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3255: Assignee: Jessica Wang > [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not > being passed from UI - inside a VPC > --- > > Key: CLOUDSTACK-3255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: latest master branch > Hypervisor: Xen server >Reporter: Sowmya Krishnan >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > Autoscale is practically broken from UI since zone id is not being passed > while creating auto scale vm profile. > This is found while configuring Auto scale for a network tier inside a VPC. > For a non-VPC isolated network, autoscale configuration is working fine. > Since there are lot of configurations in autoscale and it's easier done > through the UI, this is critical. > Steps: > = > Create a VPC network with external LB > Create a network tier within the VPC with external LB offering provided by > Netscaler. > Acquire a public IP and configure autoscale with the IP > Input all required configurations for autoscale > Result: > Fails while creating auto scale VM profile due to missing zone id parameter. > Zone id has always been a required param for createAutoScaleVMProfile > Following are the logs > 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===START=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=jso > n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg > raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca > leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null) > Unable to execute API command autoscalevmprofile due to missing parameter > zoneid > 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > The same works fine while configuring in a non-VPC isolated network -- 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
[jira] [Resolved] (CLOUDSTACK-3175) DetachVolume command fails with Internal Server Error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-3175. -- Resolution: Fixed Based on latest BVT test report on master, this has been fixed. http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/lastCompletedBuild/suite=test_volumes/testReport/ > DetachVolume command fails with Internal Server Error > - > > Key: CLOUDSTACK-3175 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3175 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: 433.tar.bz2 > > > The detach volume command fails with the following exception during resize > and other volume operations. > Jun 24 19:02:19 cloudstack-centos63 local0: 2013-06-25 02:02:19,529 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-112:job-219) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd > Jun 24 19:02:19 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume: > TestDiskServ from VM: 6cfa189d-5b8c-45d3-84c6-2849f7a01ddf; Failed dettach > volume: 43411042-0287-48aa-9909-70dcd0bba273, due to The server failed to > handle your request, due to an internal error. The given message may give > details useful for debugging the problem. > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1939) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 24 19:02:19 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 24 19:02:19 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > This was seen on master (af91a8ac8de4ce73bafd8caf9b2cc1bd73bdb444) -- 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
[jira] [Assigned] (CLOUDSTACK-3175) DetachVolume command fails with Internal Server Error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-3175: Assignee: Min Chen > DetachVolume command fails with Internal Server Error > - > > Key: CLOUDSTACK-3175 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3175 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: 433.tar.bz2 > > > The detach volume command fails with the following exception during resize > and other volume operations. > Jun 24 19:02:19 cloudstack-centos63 local0: 2013-06-25 02:02:19,529 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-112:job-219) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd > Jun 24 19:02:19 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume: > TestDiskServ from VM: 6cfa189d-5b8c-45d3-84c6-2849f7a01ddf; Failed dettach > volume: 43411042-0287-48aa-9909-70dcd0bba273, due to The server failed to > handle your request, due to an internal error. The given message may give > details useful for debugging the problem. > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1939) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 24 19:02:19 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 24 19:02:19 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > This was seen on master (af91a8ac8de4ce73bafd8caf9b2cc1bd73bdb444) -- 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
[jira] [Assigned] (CLOUDSTACK-3260) [Automation] Volume attach and detach failed with null pointer exception in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su reassigned CLOUDSTACK-3260:
-
Assignee: edison su
> [Automation] Volume attach and detach failed with null pointer exception in
> vmware
> --
>
> Key: CLOUDSTACK-3260
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3260
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
> Environment: Vmware
> Build from master_stable build
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3260.rar
>
>
> Regression test case
> ntegration.component.test_volumes.TestAttachDetachVolume.test_01_volume_attach_detach
> failed with null pointer exception
> 2013-06-27 20:12:45,487 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-500:null) Seq 1-94963056: Executing request
> 2013-06-27 20:12:45,487 INFO [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) Executing resource CreateCommand:
> {"volId":217,"pool":{
> "id":1,"uuid":"4faf04c2-6dd8-3025-b43f-65d32cc49d02","host":"10.223.110.232","path":"/export/home/automation/SC-CLOUD-QA03/primary1","port":2049,"type"
> :"NetworkFilesystem"},"diskCharacteristics":{"size":1073741824,"tags":[],"type":"DATADISK","name":"TestDiskServ","useLocalStorage":false,"recreatable":
> false,"diskOfferingId":107,"volumeId":217},"executeInSequence":false,"wait":0}
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO]
> (DirectAgent-500:10.223.250.130) find VM e5ed7f8bea2c499b94c74c9ff35ae23c on
> host
> 2013-06-27 20:12:46,060 DEBUG [vmware.mo.HostMO]
> (DirectAgent-500:10.223.250.130) load VM cache on host
> 2013-06-27 20:12:46,066 INFO [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) Destroy dummy VM after volume creation
> 2013-06-27 20:12:46,066 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-500:10.223.250.130) CreateCommand failed due to Exception:
> java.lang.NullPo
> interException
> Message: null
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4765)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 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:722)
> 2013-06-27 20:12:46,067 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-500:null) Seq 1-94963056: Response Received:
> 2013-06-27 20:12:46,067 DEBUG [agent.transport.Request]
> (DirectAgent-500:null) Seq 1-94963056: Processing: { Ans: , MgmtId:
> 90928106758026, via: 1, Ver: v1, Flags: 10,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> java.lang.Exception\nMessage: java.lang.NullPointerException\nStack:
> java.lang.Exception: java.lang.NullPointerException\n\tat
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4777)\n\tat
>
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:378)\n\tat
>
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)\n\tat
>
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)\n\tat
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)\n\tat
> java.util.concurrent.FutureTask.run(FutureTask.java:166)\n\tat
> java.util.concurrent.Sched:
> 1. Deploy a vm and create 5 data disk
> 2. Attach all the created Volume to the vm.
> 3. Detach all the volumes attached.
> 4. Reboot the VM. VM should be successfully rebooted
> 5. Stop the VM. Stop VM should be successful
> 6. Start The VM. Start VM should be successful
--
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
[jira] [Assigned] (CLOUDSTACK-3220) Object_Store_Refactor - No Download Template link when saved to AWS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3220: Assignee: Jessica Wang > Object_Store_Refactor - No Download Template link when saved to AWS > --- > > Key: CLOUDSTACK-3220 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3220 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: chrome on linux > devcloud > Cloudian and Amazon S3 object stores >Reporter: Thomas O'Dowd >Assignee: Jessica Wang > Attachments: NoDownloadTemplateLink.png > > > 1. Remove NFS secondary storage > 2. Add Amazon S3 secondary storage > 3. Upload a template > 4. Verify template is in the S3 bucket (using external tool - s3cmd or other) > 5. Navigate to the template in the GUI. > 6. hover over the quickview > At step 6, I expect a button to download the template and a button to delete > the template. I can only see the delete button though. There is no log output > to suggest why or what might be different. > However, when I use the Cloudian S3 object store in step 2 instead of AWS, > the same gui offers me a download template button. > I've tried this a few times with Amazon storage with the same results. I'm > going to delete my database now and try again with Cloudian just to verify > that I'm not seeing things. -- 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
[jira] [Resolved] (CLOUDSTACK-3220) Object_Store_Refactor - No Download Template link when saved to AWS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-3220. -- Resolution: Incomplete Thomas, Please provide database dump. Jessica > Object_Store_Refactor - No Download Template link when saved to AWS > --- > > Key: CLOUDSTACK-3220 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3220 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: chrome on linux > devcloud > Cloudian and Amazon S3 object stores >Reporter: Thomas O'Dowd >Assignee: Jessica Wang > Attachments: NoDownloadTemplateLink.png > > > 1. Remove NFS secondary storage > 2. Add Amazon S3 secondary storage > 3. Upload a template > 4. Verify template is in the S3 bucket (using external tool - s3cmd or other) > 5. Navigate to the template in the GUI. > 6. hover over the quickview > At step 6, I expect a button to download the template and a button to delete > the template. I can only see the delete button though. There is no log output > to suggest why or what might be different. > However, when I use the Cloudian S3 object store in step 2 instead of AWS, > the same gui offers me a download template button. > I've tried this a few times with Amazon storage with the same results. I'm > going to delete my database now and try again with Cloudian just to verify > that I'm not seeing things. -- 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
[jira] [Created] (CLOUDSTACK-3278) In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1
Ryan Lei created CLOUDSTACK-3278: Summary: In non-OSS build, jetty:run does not upgrade the database to 4.1.0 and 4.1.1 Key: CLOUDSTACK-3278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3278 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.1.1 Environment: git 4.1, CentOS 6.3, Tomcat 6.0.33, non-OSS build Reporter: Ryan Lei Priority: Blocker Fix For: 4.1.1 Use git 4.1 branch to build non-OSS from source with the following commands: (1) Put the necessary jars in deps/ (2) Run deps/install-non-oss.sh with success (3) $ mvn clean install -DskipTests=true -Dnonoss (4) $ mvn -P developer -pl developer -Ddeploydb (5) $ mvn -pl :cloud-client-ui jetty:run Then I get these DB version errors which made jetty quit: INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker encryptionSecretKeyChecker INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker databaseIntegrityChecker INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Grabbing lock to check for database integrity. INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-2:) Performing database integrity check INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker managementServerNode INFO [utils.component.ComponentContext] (Timer-2:) Running SystemIntegrityChecker premiumDatabaseUpgradeChecker INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Grabbing lock to check for database upgrade. INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) DB version = 4.0.0 Code Version = 4.1.1-SNAPSHOT INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) Database upgrade must be performed from 4.0.0 to 4.1.1-SNAPSHOT ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-2:) The end upgrade version is actually at 4.1.0 but our management server code version is at 4.1.1-SNAPSHOT ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check failed. Refuse to startup In MySQL, the 'version' table has only one entry whose value is 4.0.0. Manually modifying the value to 4.1.1 led to other exceptions. Looks like CloudStack "forgets" to upgrade the database. However, the OSS build works fine. Jetty does run Upgrade40to41 and Upgrade410to411 in the log. The 'version' table has three entries. mysql> select * from version; ++-+-+--+ | id | version | updated | step | ++-+-+--+ | 1 | 4.0.0 | 2013-06-28 21:58:27 | Complete | | 2 | 4.1.0 | 2013-06-28 13:59:18 | Complete | | 3 | 4.1.1 | 2013-06-28 13:59:18 | Complete | ++-+-+--+ The non-OSS build with the 4.1.0 source code release works fine, too. -- 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
[jira] [Commented] (CLOUDSTACK-3168) BVT - Network test cases failed with ssh connection error
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695567#comment-13695567
]
Rayees Namathponnan commented on CLOUDSTACK-3168:
-
Traceback (most recent call last):
File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
testMethod()
File "/data/Repo2/qa/cloudstack/test/integration/smoke/test_network.py", line
1002, in test_02_create_lb_rule_non_nat
(e, self.non_src_nat_ip.ipaddress.ipaddress))
File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
raise self.failureException(msg)
AssertionError: 'NoneType' object is not callable: SSH failed for VM with IP
Address: {networkid : u'2d6e5aac-da67-4fce-9531-e2ccfcb1aa40',
physicalnetworkid : u'fc1cb3ff-04f3-4110-85c6-17a6394f489f', account :
u'test-73G4HJ', domainid : u'9ce93368-de8e-11e2-b7dd-52b2d980df8a', issourcenat
: False, isstaticnat : False, tags : [], associatednetworkname :
u'test-73G4HJ-network', domain : u'ROOT', vlanid :
u'4bdc89d7-baf9-4331-9709-e9f763c312c4', zoneid :
u'89617260-90a1-44f3-ae14-793f6ffcf45f', vlanname : u'510', state :
u'Allocating', associatednetworkid : u'5fe45db7-607b-4ce7-9a30-8b1c298b4496',
zonename : u'Adv-VMware-Zone1', forvirtualnetwork : True, allocated :
u'2013-06-26T15:06:05-0700', issystem : False, ipaddress : u'10.223.243.22', id
: u'aa7578ee-add6-4a6c-9d74-d427c18638be', isportable : False}: SSH failed for
VM with IP Address: 10.223.243.22
> BVT - Network test cases failed with ssh connection error
> --
>
> Key: CLOUDSTACK-3168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3168
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.2.0
> Environment: Automation env
>Reporter: Rayees Namathponnan
>Assignee: Girish Shilamkar
> Fix For: 4.2.0
>
>
> Below two tets cases failing with ssh connection error
> smoke.test_network.TestLoadBalancingRule.test_02_create_lb_rule_non_nat
> test_network.TestPortForwarding.test_02_port_fwd_on_non_src_nat
--
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
[jira] [Assigned] (CLOUDSTACK-3145) StorageManager-Scavenger NPEs when cleaning up templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-3145: Assignee: Min Chen > StorageManager-Scavenger NPEs when cleaning up templates > > > Key: CLOUDSTACK-3145 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3145 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > > This is possibly related to the issue seen in CLOUDSTACK-3144. In this case > the storage cleanup thread is set to run every 5 minutes and after the > template deletion fails during account gc. The following NPE is notieced from > the storagemanager scavenger: > Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,384 WARN > [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) problem > cleaning up templates in secondary storage store > nfs://nfs.fmt.vmops.com:/export/automation/acs/secondary > Jun 23 12:18:52 java.lang.NullPointerException > Jun 23 12:18:52 java.lang.NullPointerException > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.TemplateObject.getInstallPath(TemplateObject.java:325) > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.to.TemplateObjectTO.(TemplateObjectTO.java:59) > Jun 23 12:18:52 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.TemplateObject.getTO(TemplateObject.java:312) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1134) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1025) > Jun 23 12:18:52 cloudstack-centos63 at > com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1328) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 12:18:52 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 12:18:52 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,386 DEBUG > [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) > Secondary storage garbage collector found 0 snapshots to cleanup on secondary > storage host: n > fs://nfs.fmt.vmops.com:/export/automation/acs/secondary -- 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
[jira] [Assigned] (CLOUDSTACK-3146) Extract Template command fails with Unsupported Command: storage.CreateEntityDownloadURLCommand on SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-3146: Assignee: Min Chen > Extract Template command fails with Unsupported Command: > storage.CreateEntityDownloadURLCommand on SSVM > --- > > Key: CLOUDSTACK-3146 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3146 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > > The extraction of templates is failing with the following exception: > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,326 ERROR > [datastore.driver.CloudStackImageStoreDriverImpl] (Job-Executor-21:job-153) > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c > 8be3d2095.vhd on ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,343 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.template.ExtractTemplateCm > d > Jun 23 11:55:37 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Unable to create a link for > entity at template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.datastore.driver.CloudStackImageStoreDriverImpl.createEntityExtractUrl(CloudStackImageStoreDriverImpl.java:72) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.storage.image.store.ImageStoreImpl.createEntityExtractUrl(ImageStoreImpl.java:194) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:495) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:415) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 23 11:55:37 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:129) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 23 11:55:37 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 23 11:55:37 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 23 11:55:37 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > Jun 23 11:55:37 cloudstack-centos63 local0: 2013-06-23 18:55:37,346 DEBUG > [cloud.async.AsyncJobManagerImpl] (Job-Executor-21:job-153) Complete async > job-153, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: > Unable to create a link for entity at > template/tmpl/22/206/8eed53a7-5645-4868-a39f-a9c8be3d2095.vhd on > ssvm,unsupported > command:com.cloud.agent.api.storage.CreateEntityDownloadURLCommand -- 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
[jira] [Commented] (CLOUDSTACK-2636) PVLAN UI: physical network> Guest network > Add IP range FAIL with error 'Gateway netmask and zoneid have to be passed in for virtual and direct untagged netw
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695465#comment-13695465
]
Bharat Kumar commented on CLOUDSTACK-2636:
--
Changed the api to accept only ip range in case when user intends to add the
range to the existing subnet.
commit ca13586331d215b0be269fea010536106d7fa67c
> PVLAN UI: physical network> Guest network > Add IP range FAIL with error
> 'Gateway netmask and zoneid have to be passed in for virtual and direct
> untagged networks
> ---
>
> Key: CLOUDSTACK-2636
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2636
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: MS ubuntu 13..04 KVM ACS 4.2 PVLAN
> hostubuntu 13..04 KVM ACS 4.2 PVLAN
>Reporter: angeline shen
>Assignee: Bharat Kumar
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack -
> Mozilla Firefox.png
>
>
> 1. advance zone. create shared network with VLAN ID, private VLAN ID, IPV4
> gateway, netmask,
>start IP, end IP
> 2. physical network> guest network> select network> view IP range> delete IP
> range
> add IP range>
> UI only allow IPV4 start IP , IPV4 end IP, IPV6 start IP, IPV6 end
> IP to be specified
> After above are specified, UI returns error:
> Gateway, netmask and zoneID have to be passed in for virtual and direct
> untagged networks
> Result:UI should also pass gateway, netmask and zoneID in the API call
> client call:
> http://10.223.195.113:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=dae3b32a-312b-4d79-a3af-2753563e127e&startip=10.223.161.100&endip=10.223.161.123&response=json&sessionkey=B6%2Bom%2B7iUDa%2BVdCTmIeNFW5UjWs%3D&_=1369267057369
> server response:
> { "createvlaniprangeresponse" :
> {"errorcode":431,"cserrorcode":4350,"errortext":"Gateway, netmask and zoneId
> have to be passed in for virtual and direct untagged networks"} }
--
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
[jira] [Resolved] (CLOUDSTACK-2636) PVLAN UI: physical network> Guest network > Add IP range FAIL with error 'Gateway netmask and zoneid have to be passed in for virtual and direct untagged netwo
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar resolved CLOUDSTACK-2636.
--
Resolution: Fixed
ca13586331d215b0be269fea010536106d7fa67c
> PVLAN UI: physical network> Guest network > Add IP range FAIL with error
> 'Gateway netmask and zoneid have to be passed in for virtual and direct
> untagged networks
> ---
>
> Key: CLOUDSTACK-2636
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2636
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: MS ubuntu 13..04 KVM ACS 4.2 PVLAN
> hostubuntu 13..04 KVM ACS 4.2 PVLAN
>Reporter: angeline shen
>Assignee: Bharat Kumar
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack -
> Mozilla Firefox.png
>
>
> 1. advance zone. create shared network with VLAN ID, private VLAN ID, IPV4
> gateway, netmask,
>start IP, end IP
> 2. physical network> guest network> select network> view IP range> delete IP
> range
> add IP range>
> UI only allow IPV4 start IP , IPV4 end IP, IPV6 start IP, IPV6 end
> IP to be specified
> After above are specified, UI returns error:
> Gateway, netmask and zoneID have to be passed in for virtual and direct
> untagged networks
> Result:UI should also pass gateway, netmask and zoneID in the API call
> client call:
> http://10.223.195.113:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=dae3b32a-312b-4d79-a3af-2753563e127e&startip=10.223.161.100&endip=10.223.161.123&response=json&sessionkey=B6%2Bom%2B7iUDa%2BVdCTmIeNFW5UjWs%3D&_=1369267057369
> server response:
> { "createvlaniprangeresponse" :
> {"errorcode":431,"cserrorcode":4350,"errortext":"Gateway, netmask and zoneId
> have to be passed in for virtual and direct untagged networks"} }
--
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
[jira] [Created] (CLOUDSTACK-3277) TODO/Non-Implemented Methods in PrimaryDataStoreEntityImpl
John Burwell created CLOUDSTACK-3277: Summary: TODO/Non-Implemented Methods in PrimaryDataStoreEntityImpl Key: CLOUDSTACK-3277 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3277 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: dev Reporter: John Burwell Priority: Blocker org.apache.cloudstack.storage.datastore.PrimaryDataStoreEntityImpl has numerous TODO comments with dummy getter/setter implementations that do no properly return the internal state of the object as expected. -- 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
[jira] [Resolved] (CLOUDSTACK-3106) Delete all the ips except for the ip alias.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3106. -- Resolution: Fixed 6b0df2566db34eb87c9603e6effcad2ad2b366c6 > Delete all the ips except for the ip alias. > --- > > Key: CLOUDSTACK-3106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3106 > 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: Bharat Kumar >Assignee: Bharat Kumar > Fix For: 4.2.0 > > -- 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
[jira] [Resolved] (CLOUDSTACK-2963) Build failure due to validateIpRange test failure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2963. -- Resolution: Fixed > Build failure due to validateIpRange test failure > -- > > Key: CLOUDSTACK-2963 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2963 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Bharat Kumar >Assignee: Bharat Kumar > -- 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
[jira] [Resolved] (CLOUDSTACK-2980) Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2980. -- Resolution: Fixed 7f2f25d640b47c8e72381bfc318a71ca2bfd > Adding a VLAN range that overlaps with two existing ranges results in > inconsistent DB entries > - > > Key: CLOUDSTACK-2980 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2980 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Under PhysicalNetwork - Guest, Add 2 VLAN ranges - 360-369;380-385 > Then adding one new VLAN range, 367-383 results in the following 2 issues, > 1. The new range displayed in the UI is 360-383;380-385 > 2. In the DB 'op_dc_vnet_alloc' table every VLAN in the range 370-379 is > missing. This is because we are trying to add VLANs from 370-383 and since > the entries 380-383 are duplicates the DB insert throws an exception. -- 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
[jira] [Resolved] (CLOUDSTACK-2732) [Multiple_IP_Ranges] Deleting guest IP range is not throwing any error message to user while the ip addresses are being used
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar resolved CLOUDSTACK-2732.
--
Resolution: Fixed
974245991c4c3fe51e63fe18b19853f5f8a0c6fa
> [Multiple_IP_Ranges] Deleting guest IP range is not throwing any error
> message to user while the ip addresses are being used
>
>
> Key: CLOUDSTACK-2732
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2732
> 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
> Environment: latest build from master
> Zone: Advanced with SG
> Hypervisor: KVM
>Reporter: Sanjeev N
>Assignee: Bharat Kumar
> Fix For: 4.2.0
>
>
> Deleting guest IP range is not throwing any error message to user while the
> ip addresses are being used
> Steps to Reproduce:
>
> 1.Bring up CS with SG enabled advanced zone with kvm hypervisor
> 2.Exhaust all the guest ip ranges from the primary ip range
> 3.Add another ip range in the existing CIDR
> 4.Deploy guest vm
> 5.Try to delete the ip range added at step3
> Expected Result:
> ==
> Deleting ip range when the ip addresses are being used, should throw a valid
> error message to user
> Actual Result:
> ===
> No error message popped up for the user
> Observations:
> ===
> API fired:
> http://10.147.59.126:8080/client/api?command=deleteVlanIpRange&id=de89f23e-8a17-4b4e-8b9c-8c89c11ec5a1&response=json&sessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D&_=1369826364206
> { "deletevlaniprangeresponse" :
> {"uuidList":[],"errorcode":530,"cserrorcode":} }
> Also observed NPE:
> 2013-05-29 12:48:27,646 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
> ===START=== 10.146.0.15 -- GET
> command=deleteVlanIpRange&id=de89f23e-8a17-4b4e-8b9c-8c89c11ec5a1&response=json&sessionkey=ySm8CvuVNkVVRASycbmxD0Lfby4%3D&_=1369826364206
> 2013-05-29 12:48:27,781 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-6:null) Ping from 3
> 2013-05-29 12:48:27,789 ERROR [cloud.api.ApiServer] (catalina-exec-19:null)
> unhandled exception executing api command: deleteVlanIpRange
> java.lang.NullPointerException
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanAndPublicIpRange(ConfigurationManagerImpl.java:2951)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanIpRange(ConfigurationManagerImpl.java:3476)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vlan.DeleteVlanIpRangeCmd.execute(DeleteVlanIpRangeCmd.java:69)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370)
> 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: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:2268)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker
[jira] [Resolved] (CLOUDSTACK-2150) DB table entries of phisical network is not proper.Shows Duplicate entries.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2150. -- Resolution: Fixed 7f2f25d640b47c8e72381bfc318a71ca2bfd > DB table entries of phisical network is not proper.Shows Duplicate entries. > - > > Key: CLOUDSTACK-2150 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2150 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Created a network with the vlan range 921-925;then added a Vlan range from > 930-934; > The db table entries shows correctly. > Then added the IP range from 921-934; then the db entries show the same range > twice ,as shown below. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-934;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) > Then deleted the range from 926 -934;then one entry is deleted in the table > but the second entry still shows 921-934.The below table explains the same. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-925;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) -- 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
[jira] [Updated] (CLOUDSTACK-2997) HAProxy maxconn is not configurable
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-2997: - Status: Ready To Review (was: In Progress) > HAProxy maxconn is not configurable > --- > > Key: CLOUDSTACK-2997 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2997 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 > Environment: Master, Xen >Reporter: Parth Jagirdar >Assignee: Bharat Kumar >Priority: Critical > > In core//src/com/cloud/network/HAProxyConfigurator.java, maxconn is hardcoded > to 4096. According to the HAProxy page, it is safe to assume 20k connections > per GB of RAM. This parameter can be changed by the > patches/systemvm/debian/config/root/reconfigLB.sh to be based on the actual > RAM of the VR. > During testing following observations were made.. > - /etc/haproxy/haproxy.cfg doesnt have maxconn as global variable. > - patches/systemvm/debian/config/root/reconfigLB.sh doesnt configure > HAProxy.cfg as per VR service offering and available RAM; -- 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
[jira] [Resolved] (CLOUDSTACK-3119) Shared network removal doesn't cleanup corresponding IP ranges
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3119. -- Resolution: Fixed 974245991c4c3fe51e63fe18b19853f5f8a0c6fa > Shared network removal doesn't cleanup corresponding IP ranges > -- > > Key: CLOUDSTACK-3119 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3119 > 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: Alena Prokharchyk >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > 1) Create Shared network from the UI; define ip4 range. > 2) Delete the network from the UI. > Bug: the network was marked as removed, but ip range remained intact: > mysql> select id, name, removed from networks where id=208; > +-++-+ > | id | name | removed | > +-++-+ > | 208 | shared account | 2013-06-21 16:37:48 | > +-++-+ > 1 row in set (0.00 sec) > mysql> select *From vlan where network_id=208; > ++--+-+--+--+-++++-+-+--+---+ > | id | uuid | vlan_id | vlan_gateway | > vlan_netmask | description | vlan_type | data_center_id | > network_id | physical_network_id | ip6_gateway | ip6_cidr | ip6_range | > ++--+-+--+--+-++++-+-+--+---+ > | 2 | 9dbd8fd9-8899-4d66-af8e-51c5f0b35905 | 22 | 172.22.0.1 | > 255.255.0.0 | 172.22.0.10-172.22.0.19 | DirectAttached | 1 | > 208 | 200 | NULL| NULL | NULL | > ++--+-+--+--+-++++-+-+--+---+ > 1 row in set (0.00 sec) > Next time someone wants to create the network with the same range, the > creation will fail due to ip duplicates -- 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
[jira] [Resolved] (CLOUDSTACK-3109) NPE while deleting the vlan IP Range of the shared network.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar resolved CLOUDSTACK-3109.
--
Resolution: Fixed
4d5c6c8381679ee3fb4ac918ca04eddf09812ab5
> NPE while deleting the vlan IP Range of the shared network.
> ---
>
> Key: CLOUDSTACK-3109
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3109
> 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
>Reporter: manasaveloori
>Assignee: Bharat Kumar
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps:
> 1.Have a CS with advanced zone.
> 2.Create a Shared guest network.(Infrastructure->Zone->physical
> N/W->Guest N/w->add N/w)
> 3.Assign the shared network to some VM.
> 4.Now try to delete the vlan IP range of the shared network.
> (Infrastructure->Zone->physical N/W->Guest N/w-> ->view
> Ip range).
> Observation:
> Observed NPE while deleting the Vlan IP range.Observed this only when the
> created shared network is assigned to some VM.
> User should be prompted that the IP range is in use and cannot be deleted.
> 2013-06-21 16:54:10,390 ERROR [cloud.api.ApiServer] (catalina-exec-6:null)
> unhandled exception executing api command: deleteVlanIpRange
> java.lang.NullPointerException
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanAndPublicIpRange(ConfigurationManagerImpl.java:3008)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.configuration.ConfigurationManagerImpl.deleteVlanIpRange(ConfigurationManagerImpl.java:3533)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vlan.DeleteVlanIpRangeCmd.execute(DeleteVlanIpRangeCmd.java:69)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> 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: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:2268)
> 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-06-21 16:54:10,394 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null)
> ===END=== 10.252.192.69 -- GET
> command=deleteVlanIpRange&id=39b0cd6d-b2e6-4518-9a6b-11d9188de0ff&response=json&sessionkey=fEUYFA7%2B5eZOpYyC0OVDvHQ%2FjlE%3D&_=1371794398171
> 2013-06-21 16:54:11,004 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-5:null) SeqA 3-19101: Processing Seq 3-19101: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
--
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/sof
[jira] [Commented] (CLOUDSTACK-2835) VR Deployement from admin registered tamplate is failing because registered template type is user.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695438#comment-13695438 ] ASF subversion and git services commented on CLOUDSTACK-2835: - Commit 75d860b3ac03e7bec2d8849859584654bfb7d801 in branch refs/heads/master-6-17-stable from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75d860b ] CLOUDSTACK-2835: VR Deployement from admin registered template is failing because registered template type is user. Additional parameter "isrouter" in register/update template API for the root admin. True if registered template is of type ROUTING. Signed-off-by: Jayapal > VR Deployement from admin registered tamplate is failing because registered > template type is user. > --- > > Key: CLOUDSTACK-2835 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2835 > 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: prashant kumar mishra >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > Attachments: Logs.rar > > > Step to reproduce > -- > -- > 1-Set Global parameter "router.template.xen" to some string say "newtmpl" . > 2-Register a system vm template with name "newtmpl" > 3-Deploy a vm with new network > Expected > --- > New router vm should come with newly registered template > Actual > > Router vm is not coming up with error "2013-06-04 07:39:20,431 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > XenServer won't support system vm, skip it" > Logs > > > 2013-06-04 07:39:20,328 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) lock account 2 is acquired > 2013-06-04 07:39:20,362 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock account 2 > 2013-06-04 07:39:20,368 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Asking VirtualRouter to implemenet Ntwk[204|Guest|8] > 2013-06-04 07:39:20,373 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Lock is acquired for network id 204 as a part of router startup in > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] > 2013-06-04 07:39:20,396 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Guest network Ntwk[204|Guest|8] > 2013-06-04 07:39:20,397 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Control network > 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Found existing network configuration for offering > [Network Offering [3-Control-System-Control-Network]: Ntwk[202|Control|3] > 2013-06-04 07:39:20,401 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock for Acct[1-system] > 2013-06-04 07:39:20,402 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Adding nic for Virtual Router in Public network > 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Found existing network configuration for offering > [Network Offering [1-Public-System-Public-Network]: Ntwk[200|Public|1] > 2013-06-04 07:39:20,407 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Releasing lock for Acct[1-system] > 2013-06-04 07:39:20,418 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Creating the router 4 in datacenter > com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$9e67d269@1 > 2013-06-04 07:39:20,418 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Allocating the domR with the hypervisor type XenServer > 2013-06-04 07:39:20,431 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > XenServer won't support system vm, skip it > 2013-06-04 07:39:20,433 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-13) > Lock is released for network id 204 as a part of router startup in > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3|ROOT-->Pool(1))] > 2013-06-04 07:39:20,437 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-1:job-13) Cleaning up because we're unable to
[jira] [Commented] (CLOUDSTACK-2794) Global parameter "router.template.id"should be removed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695437#comment-13695437 ] ASF subversion and git services commented on CLOUDSTACK-2794: - Commit 98b47ab4667e57e110faa88a71ce2f78a2161a8b in branch refs/heads/master-6-17-stable from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=98b47ab ] CLOUDSTACK-2794: Global parameter "router.template.id" should be removed The parameter was not in use. We use zone/global coonfigutaion parameters router.template.xenserver/vmware/hyperv/kvm/lxc to deploy router Signed-off-by: Jayapal > Global parameter "router.template.id"should be removed > --- > > Key: CLOUDSTACK-2794 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2794 > 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: prashant kumar mishra >Assignee: Harikrishna Patnala >Priority: Minor > Fix For: 4.2.0 > > > Since template is being select depend on parameter > router.template.xen,router.template.kvm,router.template.vmware. > "router.template.id" should be removed -- 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
[jira] [Commented] (CLOUDSTACK-3245) non admin user not able to register template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695436#comment-13695436 ] ASF subversion and git services commented on CLOUDSTACK-3245: - Commit 11a28aae455ba070a8afa105a51a758a78762f9e in branch refs/heads/master-6-17-stable from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11a28aa ] CLOUDSTACK-3245: non admin user not able to register template Signed-off-by: Jayapal > non admin user not able to register template > > > Key: CLOUDSTACK-3245 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3245 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > > During registering template Admin only API parameter is set defaulted to > false in the API layer if it is not set which causing user to fail > registering template. -- 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
[jira] [Commented] (CLOUDSTACK-3042) handle Scaling up of vm memory/CPU based on the presence of XS tools in the template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695440#comment-13695440 ] ASF subversion and git services commented on CLOUDSTACK-3042: - Commit d8690837ded1e7219ece5889b8302b5d2a85d730 in branch refs/heads/master-6-17-stable from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d869083 ] CLOUDSTACK-2987 Ensure XStools to be there in template inorder to enable dynamic scaling of vm CLOUDSTACK-3042 - handle Scaling up of vm memory/CPU based on the presence of XS tools in the template This also takes care of updation of VM after XS tools are installed in the vm and set memory values accordingly to support dynamic scaling after stop start of VM Signed-off-by: Jayapal > handle Scaling up of vm memory/CPU based on the presence of XS tools in the > template > > > Key: CLOUDSTACK-3042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3042 > 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: Harikrishna Patnala >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.2.0 > > > This should also take care of updation of VM after XS tools are installed in > the vm and set memory values accordingly to support dynamic scaling after > stop start of VM -- 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
[jira] [Commented] (CLOUDSTACK-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695439#comment-13695439 ] ASF subversion and git services commented on CLOUDSTACK-2987: - Commit d8690837ded1e7219ece5889b8302b5d2a85d730 in branch refs/heads/master-6-17-stable from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d869083 ] CLOUDSTACK-2987 Ensure XStools to be there in template inorder to enable dynamic scaling of vm CLOUDSTACK-3042 - handle Scaling up of vm memory/CPU based on the presence of XS tools in the template This also takes care of updation of VM after XS tools are installed in the vm and set memory values accordingly to support dynamic scaling after stop start of VM Signed-off-by: Jayapal > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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: Harikrishna Patnala >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.2.0 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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
[jira] [Created] (CLOUDSTACK-3276) Explore the use of Liquibase and DbMaintain for doing database upgrade change management
Prasanna Santhanam created CLOUDSTACK-3276: -- Summary: Explore the use of Liquibase and DbMaintain for doing database upgrade change management Key: CLOUDSTACK-3276 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3276 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Fix For: Future More info: http://markmail.org/message/exoz7zed6n6lpbdd -- 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
[jira] [Created] (CLOUDSTACK-3275) Object_Store : Provide a mechanism to track multipart image upload progress
Prasanna Santhanam created CLOUDSTACK-3275: -- Summary: Object_Store : Provide a mechanism to track multipart image upload progress Key: CLOUDSTACK-3275 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3275 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Fix For: Future This would be nice to track the progress of the downloads to an image store similar to how the DownloadProgressCommand used to work for secondary store backed by NFS. On IRC you asked the following question but quit before I could answer: tpodowd: it's a problem not to be able to see the progress of the download. does s3 have a mechanism to provide callback for progress? yes and no... For uploads you can do it by splitting your upload into parts and doing a multipart upload. Right now, its using 5M parts so after each 5M part is uploaded you could update progress. You probably know how many 5M parts you'll upload so % is easy. For downloads objects can be either small or huge. There is no concept of downloading parts per-say but you could download using the Range header... Ie, you can request the 1st 5M of an object in your first GET, the next 5M in the 2nd GET etc until you have all the object. In this way you can also download in parallel and report progress after each get completes. You know the size of the object because you can do a HEAD on it so a % is also do-able. So yes it's possible both ways but perhaps more hassle. Hope that helps. Tom. -- 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
[jira] [Updated] (CLOUDSTACK-3273) Object_Store_refactor - ClassCastException when adding image store via API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3273: --- Description: I am using marvin to create a zone with secondary storage that is of type object store backed by s3. When adding a data store from marvin I see the following ClassCastException: API call is included in the stacktrace below: 2013-06-28 18:38:55,556 DEBUG [cloud.api.ApiServlet] (1403723582@qtp-797541818-2:null) ===END=== 127.0.0.1 -- GET details%5B2%5D.key=usehttps&details%5B3%5D.value=SANITIZED&details%5B7%5D.key=connectiontimeout&details%5B6%5D.value=s3.amazonaws.com&signature=v6db1QgFCLLg8x%2FpbaavA5L5fbA%3D&details%5B4%5D.key=bucket&details%5B1%5D.value=acstest-objectstore&apiKey=TK6vqGpTNemzgrHbJRZi5YLZg04jqRPvrCZja_Ku62w6jrUahyxKItS5r4CWzvgiyq_1s-W8bUOTkYXkbvsRxA&details%5B8%5D.value=objectstore&details%5B5%5D.value=&details%5B7%5D.value=30&response=json&details%5B8%5D.key=__name__&details%5B2%5D.value=true&details%5B6%5D.key=endpoint&details%5B0%5D.value=0&details%5B4%5D.value=acstest.cloudstack.org&details%5B1%5D.key=name&details%5B5%5D.key=secretkey&details%5B3%5D.key=accesskey&provider=S3&command=addImageStore&details%5B0%5D.key=maxerrorretry 2013-06-28 18:38:55,560 DEBUG [cloud.api.ApiServlet] (1403723582@qtp-797541818-2:null) ===START=== 127.0.0.1 -- GET apiKey=TK6vqGpTNemzgrHbJRZi5YLZg04jqRPvrCZja_Ku62w6jrUahyxKItS5r4CWzvgiyq_1s-W8bUOTkYXkbvsRxA&url=nfs%3A%2F%2F192.168.56.10%2Fopt%2Fstorage%2Fsecondary&details%5B0%5D.value=nfs%3A%2F%2F192.168.56.10%2Fopt%2Fstorage%2Fsecondary&signature=v%2Fi%2FVS%2F0W%2FHPErooqnoiCnUU12U%3D&details%5B1%5D.key=__name__&zoneid=892f9f48-37fb-4dc4-b8be-03b8e46bebee&details%5B1%5D.value=cachestorage&command=createCacheStore&provider=NFS&response=json&details%5B0%5D.key=url 2013-06-28 18:38:55,579 INFO [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] (1403723582@qtp-797541818-2:null) Trying to add a new host at nfs://192.168.56.10/opt/storage/secondary in data center 1 2013-06-28 18:38:55,587 DEBUG [cloud.storage.StorageManagerImpl] (1403723582@qtp-797541818-2:null) Failed to add data store java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String at org.apache.cloudstack.storage.image.datastore.ImageStoreHelper.createImageStore(ImageStoreHelper.java:98) at org.apache.cloudstack.storage.datastore.lifecycle.CloudStackImageStoreLifeCycleImpl.initialize(CloudStackImageStoreLifeCycleImpl.java:121) at com.cloud.storage.StorageManagerImpl.createCacheStore(StorageManagerImpl.java:1872) at org.apache.cloudstack.api.command.admin.storage.CreateCacheStoreCmd.execute(CreateCacheStoreCmd.java:108) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) 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) 2013-06-28 18:38:55,588 WARN [admin.storage.AddImageStoreCmd] (1403723582@qtp-797541818-2:null) Exception: com.cloud.utils.exception.CloudRuntimeException: Failed to add data store at com.cloud.storage.StorageManagerImpl.createCacheStore(StorageManagerImpl.java:1875)
[jira] [Updated] (CLOUDSTACK-3273) Object_Store_refactor - ClassCastException when adding image store via API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-3273: --- Priority: Critical (was: Major) > Object_Store_refactor - ClassCastException when adding image store via API > -- > > Key: CLOUDSTACK-3273 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3273 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > I am using marvin to create a zone with secondary storage that is of type > object store backed by s3. When adding a data store from marvin I see the > following ClassCastException: API call is included in the stacktrace below: > 2013-06-28 18:38:55,556 DEBUG [cloud.api.ApiServlet] > (1403723582@qtp-797541818-2:null) ===END=== 127.0.0.1 -- GET > details%5B2%5D.key=usehttps&details%5B3%5D.value=SANITIZED&details%5B7%5D.key=connectiontimeout&details%5B6%5D.value=s3.amazonaws.com&signature=v6db1QgFCLLg8x%2FpbaavA5L5fbA%3D&details%5B4%5D.key=bucket&details%5B1%5D.value=acstest-objectstore&apiKey=TK6vqGpTNemzgrHbJRZi5YLZg04jqRPvrCZja_Ku62w6jrUahyxKItS5r4CWzvgiyq_1s-W8bUOTkYXkbvsRxA&details%5B8%5D.value=objectstore&details%5B5%5D.value=&details%5B7%5D.value=30&response=json&details%5B8%5D.key=__name__&details%5B2%5D.value=true&details%5B6%5D.key=endpoint&details%5B0%5D.value=0&details%5B4%5D.value=acstest.cloudstack.org&details%5B1%5D.key=name&details%5B5%5D.key=secretkey&details%5B3%5D.key=accesskey&provider=S3&command=addImageStore&details%5B0%5D.key=maxerrorretry > 2013-06-28 18:38:55,560 DEBUG [cloud.api.ApiServlet] > (1403723582@qtp-797541818-2:null) ===START=== 127.0.0.1 -- GET > apiKey=TK6vqGpTNemzgrHbJRZi5YLZg04jqRPvrCZja_Ku62w6jrUahyxKItS5r4CWzvgiyq_1s-W8bUOTkYXkbvsRxA&url=nfs%3A%2F%2F192.168.56.10%2Fopt%2Fstorage%2Fsecondary&details%5B0%5D.value=nfs%3A%2F%2F192.168.56.10%2Fopt%2Fstorage%2Fsecondary&signature=v%2Fi%2FVS%2F0W%2FHPErooqnoiCnUU12U%3D&details%5B1%5D.key=__name__&zoneid=892f9f48-37fb-4dc4-b8be-03b8e46bebee&details%5B1%5D.value=cachestorage&command=createCacheStore&provider=NFS&response=json&details%5B0%5D.key=url > 2013-06-28 18:38:55,579 INFO > [datastore.lifecycle.CloudStackImageStoreLifeCycleImpl] > (1403723582@qtp-797541818-2:null) Trying to add a new host at > nfs://192.168.56.10/opt/storage/secondary in data center 1 > 2013-06-28 18:38:55,587 DEBUG [cloud.storage.StorageManagerImpl] > (1403723582@qtp-797541818-2:null) Failed to add data store > java.lang.ClassCastException: java.lang.Integer cannot be cast to > java.lang.String > at > org.apache.cloudstack.storage.image.datastore.ImageStoreHelper.createImageStore(ImageStoreHelper.java:98) > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackImageStoreLifeCycleImpl.initialize(CloudStackImageStoreLifeCycleImpl.java:121) > at > com.cloud.storage.StorageManagerImpl.createCacheStore(StorageManagerImpl.java:1872) > at > org.apache.cloudstack.api.command.admin.storage.CreateCacheStoreCmd.execute(CreateCacheStoreCmd.java:108) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > 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) >
