[jira] [Created] (CLOUDSTACK-8241) Moving the uplaod_volume dict to configurableData section so that volume upload URL can be changed according to the setup
Gaurav Aradhye created CLOUDSTACK-8241: -- Summary: Moving the uplaod_volume dict to configurableData section so that volume upload URL can be changed according to the setup Key: CLOUDSTACK-8241 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8241 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 The volume upload URL is hard coded right now and should be moved to configurableData section so that appropriate data can be filled before the running the relevant test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8240) component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode - Skip the test case because it is not possible to check the scenario through auto
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-8240: --- Status: Reviewable (was: In Progress) > component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode > - Skip the test case because it is not possible to check the scenario > through automation > --- > > Key: CLOUDSTACK-8240 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8240 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.5.0 > > > The test case fails because Vm is being deployed with memory so high (just > below the host capacity) that such high amount of memory can't be specified > in service offering. > The scenario is not testable, hence test case should be skipped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8240) component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode - Skip the test case because it is not possible to check the scenario through auto
Gaurav Aradhye created CLOUDSTACK-8240: -- Summary: component.test_vmware_drs.TestVMPlacement.test_vm_creation_in_fully_automated_mode - Skip the test case because it is not possible to check the scenario through automation Key: CLOUDSTACK-8240 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8240 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 The test case fails because Vm is being deployed with memory so high (just below the host capacity) that such high amount of memory can't be specified in service offering. The scenario is not testable, hence test case should be skipped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315328#comment-14315328 ] Star Guo edited comment on CLOUDSTACK-8237 at 2/11/15 1:10 AM: --- Hi, Are there any one meet this issue? Thanks. Best Regards, Star Guo -- This message was sent by Atlassian JIRA (v6.3.4#6332) was (Author: starg): Hi, Are there any one meet this issue? Thanks. Best Regards, Star Guo -邮件原件- 发件人: Star Guo (JIRA) [mailto:j...@apache.org] 发送时间: 2015年2月10日 20:45 收件人: cloudstack-iss...@incubator.apache.org 主题: [jira] [Created] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException Star Guo created CLOUDSTACK-8237: Summary: add nic with instance throw java.lang.NullPointerException Key: CLOUDSTACK-8237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8237 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.3 Environment: CentOS 7 which Java 1.7.0_75, Running simulator/ Reporter: Star Guo In simulator env, I create a serviceoffering with cpu&mem custom , and deploy an instance with this serviceoffering. After that, I add nic on this instance and throw this issus: WARN [c.c.u.d.Merovingian2] (API-Job-Executor-2:ctx-abcb085b job-26 ctx-c85611f5) Was unable to find lock for the key vm_instance6 and thread id 2089552368 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Add job-27 into job monitoring ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Invocation exception, caused by: java.lang.NullPointerException INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Rethrow exception java.lang.NullPointerException ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Unable to complete AsyncJobVO {id:27, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkAddVmToNetwork, cmdInfo: rO0ABXNyACFjb20uY2xvdWQudm0uVm1Xb3JrQWRkVm1Ub05ldHdvcmt6-m3bkApgrQIAAkwACW5ldHdvcmtJZHQAEExqYXZhL2xhbmcvTG9uZztMABJyZXF1c3RlZE5pY1Byb2ZpbGV0ABlMY29tL2Nsb3VkL3ZtL05pY1Byb2ZpbGU7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAGdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAzXNyABdjb20uY2xvdWQudm0uTmljUHJvZmlsZUVY7kYs6AbAAgAeWgAKZGVmYXVsdE5pY0oAAmlkWgAWaXNTZWN1cml0eUdyb3VwRW5hYmxlZEoACW5ldHdvcmtJZEoABHZtSWRMAA1icm9hZGNhc3RUeXBldAAwTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJEJyb2FkY2FzdERvbWFpblR5cGU7TAAMYnJvYWRjYXN0VXJpdAAOTGphdmEvbmV0L1VSSTtMAAhkZXZpY2VJZHQAE0xqYXZhL2xhbmcvSW50ZWdlcjtMAARkbnMxcQB-AARMAARkbnMycQB-AARMAAZmb3JtYXR0ACpMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkQWRkcmVzc0Zvcm1hdDtMAAdnYXRld2F5cQB-AARMAAppcDRBZGRyZXNzcQB-AARMAAppcDZBZGRyZXNzcQB-AARMAAdpcDZDaWRycQB-AARMAAdpcDZEbnMxcQB-AARMAAdpcDZEbnMycQB-AARMAAppcDZHYXRld2F5cQB-AARMAAxpc29sYXRpb25VcmlxAH4ADEwACm1hY0FkZHJlc3NxAH4ABEwABG1vZGV0ACFMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkTW9kZTtMAARuYW1lcQB-AARMAAduZXRtYXNrcQB-AARMAAtuZXR3b3JrUmF0ZXEAfgANTAANcmVxdWVzdGVkSXB2NHEAfgAETAANcmVxdWVzdGVkSXB2NnEAfgAETAANcmVzZXJ2YXRpb25JZHEAfgAETAAIc3RyYXRlZ3l0ACZMY29tL2Nsb3VkL3ZtL05pYyRSZXNlcnZhdGlvblN0cmF0ZWd5O0wAC3RyYWZmaWNUeXBldAAoTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJFRyYWZmaWNUeXBlO0wABHV1aWRxAH4ABHhwAABwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBw, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 8796758677527, completeMsid: null, lastUpdated: null, lastPolled: null, created: Tue Feb 10 07:20:35 EST 2015}, job origin:26 java.lang.NullPointerException at com.cloud.hypervisor.HypervisorGuruBase.toVirtualMachineTO(HypervisorGuruBase.java:125) at com.cloud.simulator.SimulatorGuru.implement(SimulatorGuru.java:46) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3467) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:5288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.
[jira] [Comment Edited] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315328#comment-14315328 ] Star Guo edited comment on CLOUDSTACK-8237 at 2/11/15 1:11 AM: --- Are there any one meet this issue? Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332) was (Author: starg): Hi, Are there any one meet this issue? Thanks. Best Regards, Star Guo -- This message was sent by Atlassian JIRA (v6.3.4#6332) > add nic with instance throw java.lang.NullPointerException > --- > > Key: CLOUDSTACK-8237 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8237 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.3 > Environment: CentOS 7 which Java 1.7.0_75, Running simulator/ >Reporter: Star Guo > > In simulator env, I create a serviceoffering with cpu&mem custom , and deploy > an instance with this serviceoffering. After that, I add nic on this instance > and throw this issus: > > WARN [c.c.u.d.Merovingian2] (API-Job-Executor-2:ctx-abcb085b job-26 > ctx-c85611f5) Was unable to find lock for the key vm_instance6 and thread id > 2089552368 > INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-2:ctx-754aeed8 > job-26/job-27) Add job-27 into job monitoring > ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 > job-26/job-27 ctx-26199438) Invocation exception, caused by: > java.lang.NullPointerException > INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 > job-26/job-27 ctx-26199438) Rethrow exception java.lang.NullPointerException > ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-2:ctx-754aeed8 > job-26/job-27) Unable to complete AsyncJobVO {id:27, userId: 2, accountId: 2, > instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkAddVmToNetwork, > cmdInfo: > rO0ABXNyACFjb20uY2xvdWQudm0uVm1Xb3JrQWRkVm1Ub05ldHdvcmt6-m3bkApgrQIAAkwACW5ldHdvcmtJZHQAEExqYXZhL2xhbmcvTG9uZztMABJyZXF1c3RlZE5pY1Byb2ZpbGV0ABlMY29tL2Nsb3VkL3ZtL05pY1Byb2ZpbGU7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAGdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAzXNyABdjb20uY2xvdWQudm0uTmljUHJvZmlsZUVY7kYs6AbAAgAeWgAKZGVmYXVsdE5pY0oAAmlkWgAWaXNTZWN1cml0eUdyb3VwRW5hYmxlZEoACW5ldHdvcmtJZEoABHZtSWRMAA1icm9hZGNhc3RUeXBldAAwTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJEJyb2FkY2FzdERvbWFpblR5cGU7TAAMYnJvYWRjYXN0VXJpdAAOTGphdmEvbmV0L1VSSTtMAAhkZXZpY2VJZHQAE0xqYXZhL2xhbmcvSW50ZWdlcjtMAARkbnMxcQB-AARMAARkbnMycQB-AARMAAZmb3JtYXR0ACpMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkQWRkcmVzc0Zvcm1hdDtMAAdnYXRld2F5cQB-AARMAAppcDRBZGRyZXNzcQB-AARMAAppcDZBZGRyZXNzcQB-AARMAAdpcDZDaWRycQB-AARMAAdpcDZEbnMxcQB-AARMAAdpcDZEbnMycQB-AARMAAppcDZHYXRld2F5cQB-AARMAAxpc29sYXRpb25VcmlxAH4ADEwACm1hY0FkZHJlc3NxAH4ABEwABG1vZGV0ACFMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkTW9kZTtMAARuYW1lcQB-AARMAAduZXRtYXNrcQB-AARMAAtuZXR3b3JrUmF0ZXEAfgANTAANcmVxdWVzdGVkSXB2NHEAfgAETAANcmVxdWVzdGVkSXB2NnEAfgAETAANcmVzZXJ2YXRpb25JZHEAfgAETAAIc3RyYXRlZ3l0ACZMY29tL2Nsb3VkL3ZtL05pYyRSZXNlcnZhdGlvblN0cmF0ZWd5O0wAC3RyYWZmaWNUeXBldAAoTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJFRyYWZmaWNUeXBlO0wABHV1aWRxAH4ABHhwAABwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBw, > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: > null, initMsid: 8796758677527, completeMsid: null, lastUpdated: null, > lastPolled: null, created: Tue Feb 10 07:20:35 EST 2015}, job origin:26 > java.lang.NullPointerException > at > com.cloud.hypervisor.HypervisorGuruBase.toVirtualMachineTO(HypervisorGuruBase.java:125) > at com.cloud.simulator.SimulatorGuru.implement(SimulatorGuru.java:46) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3467) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:5288) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > at > com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5346) > at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.jav
[jira] [Commented] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315328#comment-14315328 ] Star Guo commented on CLOUDSTACK-8237: -- Hi, Are there any one meet this issue? Thanks. Best Regards, Star Guo -邮件原件- 发件人: Star Guo (JIRA) [mailto:j...@apache.org] 发送时间: 2015年2月10日 20:45 收件人: cloudstack-iss...@incubator.apache.org 主题: [jira] [Created] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException Star Guo created CLOUDSTACK-8237: Summary: add nic with instance throw java.lang.NullPointerException Key: CLOUDSTACK-8237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8237 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.3 Environment: CentOS 7 which Java 1.7.0_75, Running simulator/ Reporter: Star Guo In simulator env, I create a serviceoffering with cpu&mem custom , and deploy an instance with this serviceoffering. After that, I add nic on this instance and throw this issus: WARN [c.c.u.d.Merovingian2] (API-Job-Executor-2:ctx-abcb085b job-26 ctx-c85611f5) Was unable to find lock for the key vm_instance6 and thread id 2089552368 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Add job-27 into job monitoring ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Invocation exception, caused by: java.lang.NullPointerException INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Rethrow exception java.lang.NullPointerException ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Unable to complete AsyncJobVO {id:27, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkAddVmToNetwork, cmdInfo: rO0ABXNyACFjb20uY2xvdWQudm0uVm1Xb3JrQWRkVm1Ub05ldHdvcmt6-m3bkApgrQIAAkwACW5ldHdvcmtJZHQAEExqYXZhL2xhbmcvTG9uZztMABJyZXF1c3RlZE5pY1Byb2ZpbGV0ABlMY29tL2Nsb3VkL3ZtL05pY1Byb2ZpbGU7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAGdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAzXNyABdjb20uY2xvdWQudm0uTmljUHJvZmlsZUVY7kYs6AbAAgAeWgAKZGVmYXVsdE5pY0oAAmlkWgAWaXNTZWN1cml0eUdyb3VwRW5hYmxlZEoACW5ldHdvcmtJZEoABHZtSWRMAA1icm9hZGNhc3RUeXBldAAwTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJEJyb2FkY2FzdERvbWFpblR5cGU7TAAMYnJvYWRjYXN0VXJpdAAOTGphdmEvbmV0L1VSSTtMAAhkZXZpY2VJZHQAE0xqYXZhL2xhbmcvSW50ZWdlcjtMAARkbnMxcQB-AARMAARkbnMycQB-AARMAAZmb3JtYXR0ACpMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkQWRkcmVzc0Zvcm1hdDtMAAdnYXRld2F5cQB-AARMAAppcDRBZGRyZXNzcQB-AARMAAppcDZBZGRyZXNzcQB-AARMAAdpcDZDaWRycQB-AARMAAdpcDZEbnMxcQB-AARMAAdpcDZEbnMycQB-AARMAAppcDZHYXRld2F5cQB-AARMAAxpc29sYXRpb25VcmlxAH4ADEwACm1hY0FkZHJlc3NxAH4ABEwABG1vZGV0ACFMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkTW9kZTtMAARuYW1lcQB-AARMAAduZXRtYXNrcQB-AARMAAtuZXR3b3JrUmF0ZXEAfgANTAANcmVxdWVzdGVkSXB2NHEAfgAETAANcmVxdWVzdGVkSXB2NnEAfgAETAANcmVzZXJ2YXRpb25JZHEAfgAETAAIc3RyYXRlZ3l0ACZMY29tL2Nsb3VkL3ZtL05pYyRSZXNlcnZhdGlvblN0cmF0ZWd5O0wAC3RyYWZmaWNUeXBldAAoTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJFRyYWZmaWNUeXBlO0wABHV1aWRxAH4ABHhwAABwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBw, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 8796758677527, completeMsid: null, lastUpdated: null, lastPolled: null, created: Tue Feb 10 07:20:35 EST 2015}, job origin:26 java.lang.NullPointerException at com.cloud.hypervisor.HypervisorGuruBase.toVirtualMachineTO(HypervisorGuruBase.java:125) at com.cloud.simulator.SimulatorGuru.implement(SimulatorGuru.java:46) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3467) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:5288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5346) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.fra
[jira] [Created] (CLOUDSTACK-8239) Add support for VirtIO-SCSI for KVM hypervisors
Andrei Mikhailovsky created CLOUDSTACK-8239: --- Summary: Add support for VirtIO-SCSI for KVM hypervisors Key: CLOUDSTACK-8239 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8239 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: KVM, Storage Controller Affects Versions: 4.6.0 Environment: KVM Reporter: Andrei Mikhailovsky Priority: Critical It would be nice to have support for virtio-scsi for KVM hypervisors. The reason for using virtio-scsi instead of virtio-blk would be increasing the number of devices you can attach to a vm, have ability to use discard and reclaim unused blocks from the backend storage like ceph rbd. There are also talks about having a greater performance advantage as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7449) "CloudRuntimeException: Can not see storage pool" after trying to add a new host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314904#comment-14314904 ] Dusan Batas commented on CLOUDSTACK-7449: - the set of patches applied to xenservers : XS62ESP1013 XS62ESP1002 XS62ESP1015 XS62E017 XS62E002 XS62E004 XS62E010 XS62ESP1 XS62E008 XS62E005 XS62ESP1014 XS62E015 XS62ESP1006 XS62ESP1011 XS62ESP1008 XS62ESP1004 XS62E007 XS62E013 XS62ESP1003 XS62E009 XS62E001 XS62E014 XS62E012 > "CloudRuntimeException: Can not see storage pool" after trying to add a new > host > > > Key: CLOUDSTACK-7449 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7449 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.4.1 > Environment: XenServer 6.2, CentOS 6.4 >Reporter: Dusan Batas > > - performed upgrade from 4.3 to 4.4 > - upgraded XenServer hosts from 6.0.2 to 6.2 > - adding a new host to cluster results with the error > INFO [c.c.n.s.SecurityGroupListener] (catalina-exec-4:ctx-7cb01020 > ctx-027ba5b4) Received a host startup notification > INFO [c.c.n.s.SecurityGroupListener] (catalina-exec-4:ctx-7cb01020 > ctx-027ba5b4) Scheduled network rules cleanup, interval=2524 > INFO [c.c.n.s.SecurityGroupListener] (catalina-exec-4:ctx-7cb01020 > ctx-027ba5b4) Received a host startup notification > INFO [c.c.v.VirtualMachinePowerStateSyncImpl] (catalina-exec-4:ctx-7cb01020 > ctx-027ba5b4) Reset VM power state sync for host: 78 > WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-3:ctx-ede0dd1c) > ModifyStoragePoolCommand add XenAPIException:Can not see storage pool: > 614cda04-67ce-3f18-9721-99b8473b1ff0 from on > host:e2cd9dda-8bfe-4cdf-831a-be7d5a26737f > host:e2cd9dda-8bfe-4cdf-831a-be7d5a26737f pool: 10.168.12.20/vol1/cluster > com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: > 614cda04-67ce-3f18-9721-99b8473b1ff0 from on > host:e2cd9dda-8bfe-4cdf-831a-be7d5a26737f > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.getStorageRepository(CitrixResourceBase.java:6848) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5166) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:476) > at > com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61) > at > com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102) > at > com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65) > at > com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > 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:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > WARN [o.a.c.alerts] (catalina-exec-4:ctx-7cb01020 ctx-027ba5b4) alertType:: > 7 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: Unable to > attach storage pool214 to the host78 > WARN [c.c.s.l.StoragePoolMonitor] (catalina-exec-4:ctx-7cb01020 > ctx-027ba5b4) Unable to connect host 78 to pool Pool[214|NetworkFilesystem] > due to com.cloud.utils.exception.CloudRuntimeException: Unable establish > connection from storage head to storage pool 214 due to > ModifyStoragePoolCommand add XenAPIException:Can not see storage pool: > 614cda04-67ce-3f18-9721-99b8473b1ff0 from on > host:e2cd9dda-8bfe-4cdf-831a-be7d5a26737
[jira] [Commented] (CLOUDSTACK-8227) Creating VDI support tool for cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314439#comment-14314439 ] Tilak Raj Singh commented on CLOUDSTACK-8227: - Hi Rajesh, Thanks for your interest in the idea. I have a demo system already setup where the guacamole webserver is situated on the management server (we can change the server location wherever required. The users home directory are mounted via ldap on the vms and the desktop provided to the end users is that of the VM instantiated through cloudstack. I can show you the current setup on my college lab via team viewer if you would like to have a look at it. There are a few issues which I wish to improve upon to increase the stability of the system. Let me know where can we discuss the project details, here on jira or on cloudstack user mail list or via personal mails. My email id is tila...@gmail.com. I also have skype. Let me know and perhaps we can arrange a chat there. Regards > Creating VDI support tool for cloudstack > > > Key: CLOUDSTACK-8227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8227 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Tilak Raj Singh > Labels: cloud, gsoc2015, java > > I wish to create a VDI support tool for cloudstack so that DesktopAsAService > can be provided using Cloudstack. I wish to use Guacamole Web Service > (http://guac-dev.org/) for the purpose which is based on VNC to do the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8238) retry ping not reached in xapi handling PingTask
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314295#comment-14314295 ] ASF subversion and git services commented on CLOUDSTACK-8238: - Commit a9c384fd174204609598ed7f48742921414b06c1 in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a9c384f ] CLOUDSTACK-8238 mocked test to make sure xapi code is called in test for pingtask > retry ping not reached in xapi handling PingTask > > > Key: CLOUDSTACK-8238 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8238 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.2 >Reporter: Daan Hoogland >Assignee: Daan Hoogland > Fix For: 4.4.3 > > > PingTask retry handling faulty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8238) retry ping not reached in xapi handling PingTask
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland resolved CLOUDSTACK-8238. --- Resolution: Fixed > retry ping not reached in xapi handling PingTask > > > Key: CLOUDSTACK-8238 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8238 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.2 >Reporter: Daan Hoogland >Assignee: Daan Hoogland > Fix For: 4.4.3 > > > PingTask retry handling faulty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8238) retry ping not reached in xapi handling PingTask
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314181#comment-14314181 ] ASF subversion and git services commented on CLOUDSTACK-8238: - Commit fbafc957dc4e9cdc83aceb2762c0b07296b1a3e6 in cloudstack's branch refs/heads/4.4 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fbafc95 ] CLOUDSTACK-8238 handling of retry ping improved > retry ping not reached in xapi handling PingTask > > > Key: CLOUDSTACK-8238 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8238 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.2 >Reporter: Daan Hoogland >Assignee: Daan Hoogland > Fix For: 4.4.3 > > > PingTask retry handling faulty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8238) retry ping not reached in xapi handling PingTask
Daan Hoogland created CLOUDSTACK-8238: - Summary: retry ping not reached in xapi handling PingTask Key: CLOUDSTACK-8238 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8238 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.2 Reporter: Daan Hoogland Assignee: Daan Hoogland Fix For: 4.4.3 PingTask retry handling faulty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8237) add nic with instance throw java.lang.NullPointerException
Star Guo created CLOUDSTACK-8237: Summary: add nic with instance throw java.lang.NullPointerException Key: CLOUDSTACK-8237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8237 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.3 Environment: CentOS 7 which Java 1.7.0_75, Running simulator/ Reporter: Star Guo In simulator env, I create a serviceoffering with cpu&mem custom , and deploy an instance with this serviceoffering. After that, I add nic on this instance and throw this issus: WARN [c.c.u.d.Merovingian2] (API-Job-Executor-2:ctx-abcb085b job-26 ctx-c85611f5) Was unable to find lock for the key vm_instance6 and thread id 2089552368 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Add job-27 into job monitoring ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Invocation exception, caused by: java.lang.NullPointerException INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27 ctx-26199438) Rethrow exception java.lang.NullPointerException ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-2:ctx-754aeed8 job-26/job-27) Unable to complete AsyncJobVO {id:27, userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkAddVmToNetwork, cmdInfo: rO0ABXNyACFjb20uY2xvdWQudm0uVm1Xb3JrQWRkVm1Ub05ldHdvcmt6-m3bkApgrQIAAkwACW5ldHdvcmtJZHQAEExqYXZhL2xhbmcvTG9uZztMABJyZXF1c3RlZE5pY1Byb2ZpbGV0ABlMY29tL2Nsb3VkL3ZtL05pY1Byb2ZpbGU7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAGdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAzXNyABdjb20uY2xvdWQudm0uTmljUHJvZmlsZUVY7kYs6AbAAgAeWgAKZGVmYXVsdE5pY0oAAmlkWgAWaXNTZWN1cml0eUdyb3VwRW5hYmxlZEoACW5ldHdvcmtJZEoABHZtSWRMAA1icm9hZGNhc3RUeXBldAAwTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJEJyb2FkY2FzdERvbWFpblR5cGU7TAAMYnJvYWRjYXN0VXJpdAAOTGphdmEvbmV0L1VSSTtMAAhkZXZpY2VJZHQAE0xqYXZhL2xhbmcvSW50ZWdlcjtMAARkbnMxcQB-AARMAARkbnMycQB-AARMAAZmb3JtYXR0ACpMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkQWRkcmVzc0Zvcm1hdDtMAAdnYXRld2F5cQB-AARMAAppcDRBZGRyZXNzcQB-AARMAAppcDZBZGRyZXNzcQB-AARMAAdpcDZDaWRycQB-AARMAAdpcDZEbnMxcQB-AARMAAdpcDZEbnMycQB-AARMAAppcDZHYXRld2F5cQB-AARMAAxpc29sYXRpb25VcmlxAH4ADEwACm1hY0FkZHJlc3NxAH4ABEwABG1vZGV0ACFMY29tL2Nsb3VkL25ldHdvcmsvTmV0d29ya3MkTW9kZTtMAARuYW1lcQB-AARMAAduZXRtYXNrcQB-AARMAAtuZXR3b3JrUmF0ZXEAfgANTAANcmVxdWVzdGVkSXB2NHEAfgAETAANcmVxdWVzdGVkSXB2NnEAfgAETAANcmVzZXJ2YXRpb25JZHEAfgAETAAIc3RyYXRlZ3l0ACZMY29tL2Nsb3VkL3ZtL05pYyRSZXNlcnZhdGlvblN0cmF0ZWd5O0wAC3RyYWZmaWNUeXBldAAoTGNvbS9jbG91ZC9uZXR3b3JrL05ldHdvcmtzJFRyYWZmaWNUeXBlO0wABHV1aWRxAH4ABHhwAABwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBw, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 8796758677527, completeMsid: null, lastUpdated: null, lastPolled: null, created: Tue Feb 10 07:20:35 EST 2015}, job origin:26 java.lang.NullPointerException at com.cloud.hypervisor.HypervisorGuruBase.toVirtualMachineTO(HypervisorGuruBase.java:125) at com.cloud.simulator.SimulatorGuru.implement(SimulatorGuru.java:46) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3467) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:5288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5346) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:501) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at
[jira] [Commented] (CLOUDSTACK-8227) Creating VDI support tool for cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313799#comment-14313799 ] Rajesh Battala commented on CLOUDSTACK-8227: I can Mentor you, if you are interested to implement this feature. > Creating VDI support tool for cloudstack > > > Key: CLOUDSTACK-8227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8227 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Tilak Raj Singh > Labels: cloud, gsoc2015, java > > I wish to create a VDI support tool for cloudstack so that DesktopAsAService > can be provided using Cloudstack. I wish to use Guacamole Web Service > (http://guac-dev.org/) for the purpose which is based on VNC to do the same -- This message was sent by Atlassian JIRA (v6.3.4#6332)