[jira] [Commented] (CLOUDSTACK-4538) Need to update the vmware clusters with the global overporvisioning factors after upgrade to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753387#comment-13753387 ] ASF subversion and git services commented on CLOUDSTACK-4538: - Commit da6f048dd23b957e5b4d6569a6d1aed7840fb1f6 in branch refs/heads/master from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=da6f048 ] CLOUDSTACK-4538 Should update the vmware clusters with the global overporvisioning factors after upgrade to 4.2. Signed off by : Nitin Mehta > Need to update the vmware clusters with the global overporvisioning factors > after upgrade to 4.2. > - > > Key: CLOUDSTACK-4538 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4538 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >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] [Commented] (CLOUDSTACK-4538) Need to update the vmware clusters with the global overporvisioning factors after upgrade to 4.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753385#comment-13753385 ] ASF subversion and git services commented on CLOUDSTACK-4538: - Commit 4a7d7324d0f71888365c0b8f235b30909c9cbceb in branch refs/heads/4.2-forward from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4a7d732 ] CLOUDSTACK-4538 Should update the vmware clusters with the global overporvisioning factors after upgrade to 4.2. Signed off by : Nitin Mehta > Need to update the vmware clusters with the global overporvisioning factors > after upgrade to 4.2. > - > > Key: CLOUDSTACK-4538 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4538 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >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] [Commented] (CLOUDSTACK-4517) [upgrade][Vmware]Deployment of VM using template registered before upgrade is failing.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753373#comment-13753373 ] Nitin Mehta commented on CLOUDSTACK-4517: - Manasa please make sure you register 3-4 template pre upgrade. > [upgrade][Vmware]Deployment of VM using template registered before upgrade is > failing. > -- > > Key: CLOUDSTACK-4517 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4517 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade, VMware >Affects Versions: 4.2.0 > Environment: upgraded from 3.07 to 4.2 >Reporter: manasaveloori >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.zip, mysqldumpAfterUp.dmp, > mysqldumpBeforeUp.dmp > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Register a template > id: 10 > store_id: 2 > template_id: 204 > created: 2013-08-27 12:13:34 > last_updated: 2013-08-27 16:05:45 > job_id: e7c32b26-3e06-4a9e-a9d0-cd6452595659 > download_pct: 100 > size: 107374182400 > store_role: Image >physical_size: 707778560 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/27/13 6:54 AM > local_path: > /mnt/SecStorage/0e8da06e-0788-3efb-86a6-b0705a2205d3/template/tmpl/2/204/dnld4711105428993449674tmp_ > install_path: > template/tmpl/2/204/dec94d02-8c40-34e8-9a1d-99906a95df2a.ova > url: http://10.147.28.7/templates/vmware/Centos6_2.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > 5 rows in set (0.00 sec) > 3.Upgrade the build to 4.2. > 4.Deploy a VM using the template registered before upgrade. > Observation: > Observed the following exception: > 2013-08-27 23:08:37,892 ERROR [storage.resource.VmwareStorageProcessor] > (DirectAgent-101:10.147.40.28) clone volume from base image failed due to > Exception: javax.xml.ws.WebServiceException > Message: java.net.SocketTimeoutException: Read timed out > javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed > out > at > com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:201) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83) > at > com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:78) > at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587) > at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546) > at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531) > at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428) > at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211) > at > com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) > at $Proxy90.waitForUpdates(Unknown Source) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:428) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:371) > at > com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:594) > at > com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:293) > at > com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:384) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73) > at > com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49) > at > com.cloud.hypervisor.vmware.resource.V
[jira] [Commented] (CLOUDSTACK-4517) [upgrade][Vmware]Deployment of VM using template registered before upgrade is failing.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753358#comment-13753358 ] Nitin Mehta commented on CLOUDSTACK-4517: - Talked to Manasa. She said that this wasnt a problem for builtin templates. She is retrying the setup now > [upgrade][Vmware]Deployment of VM using template registered before upgrade is > failing. > -- > > Key: CLOUDSTACK-4517 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4517 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade, VMware >Affects Versions: 4.2.0 > Environment: upgraded from 3.07 to 4.2 >Reporter: manasaveloori >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.zip, mysqldumpAfterUp.dmp, > mysqldumpBeforeUp.dmp > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Register a template > id: 10 > store_id: 2 > template_id: 204 > created: 2013-08-27 12:13:34 > last_updated: 2013-08-27 16:05:45 > job_id: e7c32b26-3e06-4a9e-a9d0-cd6452595659 > download_pct: 100 > size: 107374182400 > store_role: Image >physical_size: 707778560 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/27/13 6:54 AM > local_path: > /mnt/SecStorage/0e8da06e-0788-3efb-86a6-b0705a2205d3/template/tmpl/2/204/dnld4711105428993449674tmp_ > install_path: > template/tmpl/2/204/dec94d02-8c40-34e8-9a1d-99906a95df2a.ova > url: http://10.147.28.7/templates/vmware/Centos6_2.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > 5 rows in set (0.00 sec) > 3.Upgrade the build to 4.2. > 4.Deploy a VM using the template registered before upgrade. > Observation: > Observed the following exception: > 2013-08-27 23:08:37,892 ERROR [storage.resource.VmwareStorageProcessor] > (DirectAgent-101:10.147.40.28) clone volume from base image failed due to > Exception: javax.xml.ws.WebServiceException > Message: java.net.SocketTimeoutException: Read timed out > javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed > out > at > com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:201) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83) > at > com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:78) > at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587) > at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546) > at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531) > at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428) > at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211) > at > com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) > at $Proxy90.waitForUpdates(Unknown Source) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:428) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:371) > at > com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:594) > at > com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:293) > at > com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:384) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73) > at > com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49) >
[jira] [Commented] (CLOUDSTACK-4542) [Automation] Failed to apply DHCP entry in VR and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753357#comment-13753357
]
Jayapal Reddy commented on CLOUDSTACK-4542:
---
Hi Rayees,
When ever if you observe com.cloud.exception.ResourceUnavailableException:
Resource [DataCenter:1] is unreachable: Unable to apply dhcp entry on router
log that mean there is some wrong with the script or router is not reachable.
The exact error will be logged in agent log.
Can you please add agent logs when the dhcp_entry.sh is called. From the logs
we can figure out script issues.
> [Automation] Failed to apply DHCP entry in VR and deployment failed
>
>
> Key: CLOUDSTACK-4542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4542
> 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: 4.2-forward
> Automation environment on KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue found in automation run, observed while running the test case
> integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_02_deploy_vms_delete_network
> Router failed to apply DHCP entry then router deployment reported as failed
> Observed below error in MS log, attached log search for "r-183-QA"
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 2-654837610: Processing: { Ans: , MgmtId:
> 29066118877352, via: 2, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect to
> host 169.254.1.219 port 3922: Connection timed out","wait":0}}] }
> 2013-08-27 22:56:30,877 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-4:null) Seq 2-654837611: Sending now. is current
> sequence.
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Seq
> 2-654837610: Received: { Ans: , MgmtId: 29066118877352, via: 2, Ver: v1,
> Flags: 110, { Answer } }
> 2013-08-27 22:56:30,878 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2919)
> at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:898)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2070)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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] [Commented] (CLOUDSTACK-4505) expungeDestroyedVirtualMachine API call
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753351#comment-13753351 ] Sanjay Tripathi commented on CLOUDSTACK-4505: - With the addition of this API, user will have to make two API to destroy a VM completely. So, to destroy a VM completely with single API command, we can add a boolean parameter in the existing "destroyVirtualMachine" API to destroy and expunge without waiting for expunge thread. > expungeDestroyedVirtualMachine API call > --- > > Key: CLOUDSTACK-4505 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4505 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: Future >Reporter: David Matteson > > We want to provide users a long recovery time before expunging their VMs > automatically. Recovery is a great feature. But the problem is that users > cannot deploy a new VM with the same hostname or IP address as a Destroyed VM > which has not yet been expunged. > So it would be great to have an API call that lets users say "No I really > don't want to recover that VM, please delete it so I can deploy a new one." > expungeDestroyedVirtualMachine would be called with a single vmid to specify > which Destroyed VM should be cleared, and of course it would only work on a > VM which is in Destroyed state already. -- 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-4542) [Automation] Failed to apply DHCP entry in VR and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753347#comment-13753347
]
Rayees Namathponnan commented on CLOUDSTACK-4542:
-
Its an intermediate issue, reducing priority
> [Automation] Failed to apply DHCP entry in VR and deployment failed
>
>
> Key: CLOUDSTACK-4542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4542
> 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: 4.2-forward
> Automation environment on KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue found in automation run, observed while running the test case
> integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_02_deploy_vms_delete_network
> Router failed to apply DHCP entry then router deployment reported as failed
> Observed below error in MS log, attached log search for "r-183-QA"
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 2-654837610: Processing: { Ans: , MgmtId:
> 29066118877352, via: 2, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect to
> host 169.254.1.219 port 3922: Connection timed out","wait":0}}] }
> 2013-08-27 22:56:30,877 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-4:null) Seq 2-654837611: Sending now. is current
> sequence.
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Seq
> 2-654837610: Received: { Ans: , MgmtId: 29066118877352, via: 2, Ver: v1,
> Flags: 110, { Answer } }
> 2013-08-27 22:56:30,878 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2919)
> at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:898)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2070)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-27 22:56:30,882 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Cleaning
> up resources for the vm VM[User|df06b516-d40a-4dfa-9b77-4612bed9660e] in
> Starting state
> 2013-08-27 22:56:30,883 DEBUG [agent.transport.Req
[jira] [Updated] (CLOUDSTACK-4543) [Automation] Failed to configure VPC router then reported as deployment failure
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-4543:
Priority: Major (was: Critical)
> [Automation] Failed to configure VPC router then reported as deployment
> failure
> ---
>
> Key: CLOUDSTACK-4543
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4543
> 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: KVM
> 4.2.1-stable branch
>Reporter: Rayees Namathponnan
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue observed during automation run, VPC router deployment failed
> during network configuration the failed with error
> [{"com.cloud.agent.api.SetupGuestNetworkAnswer":{"result":false,"details":"Creating
> guest network failed due to ","wait":0}}] }
> Here the log from Management server
> 2013-08-28 05:09:27,760 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Network
> id=473 is shutdown successfully, cleaning up corresponding resources now.
> 2013-08-28 05:09:27,762 DEBUG [network.guru.GuestNetworkGuru]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ])
> Releasing vnet for the network id=473
> 2013-08-28 05:09:27,773 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network Ntwk[473|Guest|125] as a part of network shutdown
> 2013-08-28 05:09:27,774 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network id 473 as a part of network implement
> 2013-08-28 05:09:27,774 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Failed
> to start instance VM[User|267a2467-9d94-4667-9624-60e139fd2d1d]
> com.cloud.utils.exception.CloudRuntimeException: Failed to add VPC router
> VM[DomainRouter|r-507-QA] to guest network Ntwk[473|Guest|125]
> at
> com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtualRouterElement.java:178)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2034)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-28 05:09:27,782 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Cleaning
> up resources for the vm VM[User|267a2467-9d94-4667-9624-60e139fd2d1d] in
> Starting state
> Log from Agent
> 2013-08-28 05:06:48,127 DEBUG [cloud.agent
[jira] [Updated] (CLOUDSTACK-4542) [Automation] Failed to apply DHCP entry in VR and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-4542:
Priority: Major (was: Critical)
> [Automation] Failed to apply DHCP entry in VR and deployment failed
>
>
> Key: CLOUDSTACK-4542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4542
> 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: 4.2-forward
> Automation environment on KVM
>Reporter: Rayees Namathponnan
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue found in automation run, observed while running the test case
> integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_02_deploy_vms_delete_network
> Router failed to apply DHCP entry then router deployment reported as failed
> Observed below error in MS log, attached log search for "r-183-QA"
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 2-654837610: Processing: { Ans: , MgmtId:
> 29066118877352, via: 2, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect to
> host 169.254.1.219 port 3922: Connection timed out","wait":0}}] }
> 2013-08-27 22:56:30,877 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-4:null) Seq 2-654837611: Sending now. is current
> sequence.
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Seq
> 2-654837610: Received: { Ans: , MgmtId: 29066118877352, via: 2, Ver: v1,
> Flags: 110, { Answer } }
> 2013-08-27 22:56:30,878 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2919)
> at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:898)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2070)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-27 22:56:30,882 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Cleaning
> up resources for the vm VM[User|df06b516-d40a-4dfa-9b77-4612bed9660e] in
> Starting state
> 2013-08-27 22:56:30,883 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ])
[jira] [Commented] (CLOUDSTACK-4543) [Automation] Failed to configure VPC router then reported as deployment failure
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753348#comment-13753348
]
Rayees Namathponnan commented on CLOUDSTACK-4543:
-
Its an intermediate issue, reducing priority
> [Automation] Failed to configure VPC router then reported as deployment
> failure
> ---
>
> Key: CLOUDSTACK-4543
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4543
> 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: KVM
> 4.2.1-stable branch
>Reporter: Rayees Namathponnan
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue observed during automation run, VPC router deployment failed
> during network configuration the failed with error
> [{"com.cloud.agent.api.SetupGuestNetworkAnswer":{"result":false,"details":"Creating
> guest network failed due to ","wait":0}}] }
> Here the log from Management server
> 2013-08-28 05:09:27,760 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Network
> id=473 is shutdown successfully, cleaning up corresponding resources now.
> 2013-08-28 05:09:27,762 DEBUG [network.guru.GuestNetworkGuru]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ])
> Releasing vnet for the network id=473
> 2013-08-28 05:09:27,773 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network Ntwk[473|Guest|125] as a part of network shutdown
> 2013-08-28 05:09:27,774 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network id 473 as a part of network implement
> 2013-08-28 05:09:27,774 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Failed
> to start instance VM[User|267a2467-9d94-4667-9624-60e139fd2d1d]
> com.cloud.utils.exception.CloudRuntimeException: Failed to add VPC router
> VM[DomainRouter|r-507-QA] to guest network Ntwk[473|Guest|125]
> at
> com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtualRouterElement.java:178)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2034)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-28 05:09:27,782 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Cleaning
> up resources for the vm VM[User|267a2467-9d94-4667-9624-60e139fd2d1d] in
>
[jira] [Commented] (CLOUDSTACK-4542) [Automation] Failed to apply DHCP entry in VR and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753344#comment-13753344
]
Jayapal Reddy commented on CLOUDSTACK-4542:
---
It can be router is not reachable or some thing failed in script.
> [Automation] Failed to apply DHCP entry in VR and deployment failed
>
>
> Key: CLOUDSTACK-4542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4542
> 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: 4.2-forward
> Automation environment on KVM
>Reporter: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue found in automation run, observed while running the test case
> integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_02_deploy_vms_delete_network
> Router failed to apply DHCP entry then router deployment reported as failed
> Observed below error in MS log, attached log search for "r-183-QA"
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 2-654837610: Processing: { Ans: , MgmtId:
> 29066118877352, via: 2, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect to
> host 169.254.1.219 port 3922: Connection timed out","wait":0}}] }
> 2013-08-27 22:56:30,877 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-4:null) Seq 2-654837611: Sending now. is current
> sequence.
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Seq
> 2-654837610: Received: { Ans: , MgmtId: 29066118877352, via: 2, Ver: v1,
> Flags: 110, { Answer } }
> 2013-08-27 22:56:30,878 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2919)
> at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:898)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2070)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-27 22:56:30,882 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Cleaning
> up resources for the vm VM[User|df06b516-d40a-4dfa-9b77-4612bed9660e] in
> Starting state
> 2013-08-27
[jira] [Commented] (CLOUDSTACK-4547) admin login/password incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753343#comment-13753343 ] Sanjay Tripathi commented on CLOUDSTACK-4547: - Can you verify that you are facing this issue even after management server logs displays "Admin user enabled". > admin login/password incorrect > --- > > Key: CLOUDSTACK-4547 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4547 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.1 > Environment: Cent OS 6.4 with Apache Cloud Stack 4.1.1 >Reporter: Amit Kumar > Labels: patch > Original Estimate: 12h > Remaining Estimate: 12h > > I had install Apache Cloud Stack 4.1.1 - 20 Times but still getting the > same error "admin login/password incorrect" using default login & password > as per official Apache doc. admin/password. > Please help me out -- 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-4303) [Automation] test_egress_fw_rules test cases failed to except script and tests failed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Shilamkar resolved CLOUDSTACK-4303. -- Resolution: Fixed > [Automation] test_egress_fw_rules test cases failed to except script and > tests failed > -- > > Key: CLOUDSTACK-4303 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4303 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Infra, Network Controller >Reporter: Rayees Namathponnan >Assignee: Ashutosk Kelkar >Priority: Critical > > Test cases from integration.component.test_egress_fw_rules.TestEgressFWRules > fails > test cases expecting script @ /tmp/expect_scrip, this should be handled in > test case, > Stacktrace > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_egress_fw_rules.py", > line 51, in test_wrap_exception_log > raise e > Script result is ['bash: /tmp/expect_script.exp: /usr/bin/expect: bad > interpreter: No such file or directory'] is not matching with ['100'] > >> begin captured logging << > testclient.testcase.TestEgressFWRules: DEBUG: Creating network with network > offering: 0bd6212f-b34c-4f7a-a84f-0c172bee6ac8 > testclient.testcase.TestEgressFWRules: DEBUG: Created network with ID: > ef2626c2-6849-43e7-8418-0c89ed528d62 > testclient.testcase.TestEgressFWRules: DEBUG: Deploying instance in the > account: test-SSFX20 > testclient.testcase.TestEgressFWRules: DEBUG: Deployed instance in account: > test-SSFX20 > testclient.testcase.TestEgressFWRules: DEBUG: expect_script>> > #!/usr/bin/expect > spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o > LogLevel=quiet -i /root/.ssh/id_rsa.cloud -p 3922 root@169.254.3.141 > expect "root@r-342-QA:~#" > send "ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o > LogLevel=quiet root@10.1.1.215 ping -c 1 www.google.com; exit $? > " > expect "root@10.1.1.215's password: " > send "password > " > interact >
[jira] [Commented] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753329#comment-13753329 ] Kelven Yang commented on CLOUDSTACK-4546: - I looked at the log and checked the NFS directory template/tmpl/1/7/ec126276-4909-33fe-9044-ba52f1e1d1b6.ova in the secondary storage is corrupted. > [Vmware] - Unable to deploy guest VM > > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.
[jira] [Resolved] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4546. - Resolution: Invalid > [Vmware] - Unable to deploy guest VM > > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-08-28 17:02:09,710 DEBUG [cl
[jira] [Updated] (CLOUDSTACK-4549) ceph:deployvm from template created from snapshot is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sadhu suresh updated CLOUDSTACK-4549:
-
Attachment: management-server.rar
management log
> ceph:deployvm from template created from snapshot is failing
>
>
> Key: CLOUDSTACK-4549
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4549
> 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: sadhu suresh
>Priority: Critical
> Attachments: management-server.rar
>
>
> VM deployment form template which is created form snapshot is failing where
> as VM deployment with uploaded template successful.
> created template form snapshot is storing in raw
> format(https://10-147-49-100.realhostip.com/userdata/0c826645-ec82-40f1-a1b0-38fc9ba1c76f.raw)..
> not sure are we converting again to QCwo2
> when we try to deploy a VM
> steps:
> 1.create a ceph instance(configure compute offering with RBD and deploy a vm)
> 2.Once it successful,select the root partition and perform snapshot
> 3.once snapshot successful,create a template from snapshot
> 4 try to create vm uning above VM
> actual result:
> deploy vm failing with exception
> -29 15:21:43,756 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service
> SecurityGroup is not supported in the network id=204
> 2013-08-29 15:21:43,762 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-14:job-42 =
> [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Applying userdata and password
> entry in network Ntwk[204|Guest|8]
> 2013-08-29 15:21:43,800 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq
> 1-2089159931: Sending { Cmd , MgmtId: 7175246184473, via: 1, Ver: v1, Flags:
> 100111,
> [{"com.cloud.agent.api.routing.SavePasswordCommand":{"password":"fnirq_cnffjbeq","vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}},{"com.cloud.agent.api.routing.VmDataCommand":{"vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}}]
> }
> 2013-08-29 15:21:44,168 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 1-2089159931: Processing: { Ans: ,
> MgmtId: 7175246184473, via: 1, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}]
> }
> 2013-08-29 15:21:44,169 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-14:null) Seq 1-2089159931: No more commands found
> 2013-08-29 15:21:44,169 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq
> 1-2089159931: Received: { Ans: , MgmtId: 7175246184473, via: 1, Ver: v1,
> Flags: 110, { Answer, Answer } }
> 2013-08-29 15:21:44,179 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service
> SecurityGroup is not supported in the network id=204
> 2013-08-29 15:21:44,182 DEBUG [cloud.storage.VolumeManagerImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Checking
> if we need to prepare 1 volumes for
> VM[User|6e798618-8e4d-4305-94a1-642e5f3aad08]
> 2013-08-29 15:21:44,207 DEBUG [storage.image.TemplateDataFactoryImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template
> 202 is already in store:1, type:Image
> 2013-08-29 15:21:44,219 DEBUG [storage.datastore.PrimaryDataStoreImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Not found
> (templateId:202poolId:5) in template_spool_ref, persisting it
> 2013-08-29 15:21:44,234 DEBUG [storage.image.TemplateDataFactoryImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template
> 202 is already in store:5, type:Primary
> 2013-08-29 15:21:44,237 DEBUG [storage.volume.VolumeServiceImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Found
> template 246c1e4ac-9fc0-3122-bcfb-77deff789f61 in storage pool 5 with
> VMTemplateStoragePool id: 5
> 2013-08-29 15:21:44,433 DEBUG [storage.volume.VolumeServiceImpl]
> (Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Acquire
> lock on VMTemplateStoragePool 5 with timeout 3600 seconds
> 2013-08-29 15:21:44,438
[jira] [Commented] (CLOUDSTACK-4225) [Automation] integration.component.test_snapshots failing with error 'TestSnapshots' object has no attribute 'template'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753321#comment-13753321 ] Rayees Namathponnan commented on CLOUDSTACK-4225: - Actually test case changed, nothing in test environment; test case started failing after below check-in https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=69f6f49ae1bb6655107245f8327f7fe1afa33f9f > [Automation] integration.component.test_snapshots failing with error > 'TestSnapshots' object has no attribute 'template' > - > > Key: CLOUDSTACK-4225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4225 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Test >Affects Versions: 4.2.0 > Environment: Automation >Reporter: Rayees Namathponnan >Priority: Critical > Fix For: 4.2.0 > > > Test cases failed with below error > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - > Stacktrace > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 354, in test_02_snapshot_data_disk > self.assertTrue(self.is_snapshot_on_nfs(snapshot_uuid)) > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 265, in is_snapshot_on_nfs > (self.config.mgtSvr[0].mgtSvrIp, e)) > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - -- 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-4225) [Automation] integration.component.test_snapshots failing with error 'TestSnapshots' object has no attribute 'template'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-4225: Assignee: (was: Rayees Namathponnan) > [Automation] integration.component.test_snapshots failing with error > 'TestSnapshots' object has no attribute 'template' > - > > Key: CLOUDSTACK-4225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4225 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Test >Affects Versions: 4.2.0 > Environment: Automation >Reporter: Rayees Namathponnan >Priority: Critical > Fix For: 4.2.0 > > > Test cases failed with below error > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - > Stacktrace > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 354, in test_02_snapshot_data_disk > self.assertTrue(self.is_snapshot_on_nfs(snapshot_uuid)) > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 265, in is_snapshot_on_nfs > (self.config.mgtSvr[0].mgtSvrIp, e)) > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - -- 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753316#comment-13753316 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 00d427d4625d2f246a8b9b40c3ad325e8c18c14b in branch refs/heads/4.2 from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=00d427d ] CLOUDSTACK-883. DOC. How to integrate your 3rd-party plugin with the UI. Contains brief third-party plugin code tutorial. (cherry picked from commit 5036e4f9f9b3b06a1268657c6c0fcc1e1ec5e83a) Signed-off-by: animesh > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753315#comment-13753315 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 9a1ca73f309e2e10e4457c29bbefb51668a81669 in branch refs/heads/4.2 from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9a1ca73 ] CLOUDSTACK-883. DOC. Small fix to comment in UI plugins section. (cherry picked from commit 4fe0fcf2631271ec0dc5686358bb624a6fd4f02a) Signed-off-by: animesh > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753314#comment-13753314 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit abd34611069d8a5a846b98b007211e6f8619e339 in branch refs/heads/4.2 from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=abd3461 ] CLOUDSTACK-883. DOC. Fix license header in UI plugins section. (cherry picked from commit 56ebf3b9b83a087b60d8de51f0276387a04c15a4) Signed-off-by: animesh > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753318#comment-13753318 ] ASF subversion and git services commented on CLOUDSTACK-864: Commit f0b2f13e5401ee16fce0e7ed2dee53dcf100adb2 in branch refs/heads/4.2 from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0b2f13 ] CLOUDSTACK-864. DOC. Small typo fix for Talluri's review comment. (cherry picked from commit 9172cc96e9ffcd80a91fc83389cd1564d9696b3c) Signed-off-by: animesh > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Srikanteswararao Talluri > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753317#comment-13753317 ] ASF subversion and git services commented on CLOUDSTACK-815: Commit 301c82f8821b6ee6b418232fda46fcfe66631ae5 in branch refs/heads/4.2 from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=301c82f ] CLOUDSTACK-815. DOC. Fix Regions documentation for reviewer comments. (cherry picked from commit 55583c0f97cecb2e4a44d5020e52209d609cb0cd) Signed-off-by: animesh > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sangeetha Hariharan > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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-4225) [Automation] integration.component.test_snapshots failing with error 'TestSnapshots' object has no attribute 'template'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam reassigned CLOUDSTACK-4225: -- Assignee: Rayees Namathponnan (was: Prasanna Santhanam) This is the same problem as CLOUDSTACK-4511. Something is changing your original KVM deployment config during your test run. > [Automation] integration.component.test_snapshots failing with error > 'TestSnapshots' object has no attribute 'template' > - > > Key: CLOUDSTACK-4225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4225 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Test >Affects Versions: 4.2.0 > Environment: Automation >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Critical > Fix For: 4.2.0 > > > Test cases failed with below error > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - > Stacktrace > File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run > testMethod() > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 354, in test_02_snapshot_data_disk > self.assertTrue(self.is_snapshot_on_nfs(snapshot_uuid)) > File > "/Repo_30X/ipcl/cloudstack/test/integration/component/test_snapshots.py", > line 265, in is_snapshot_on_nfs > (self.config.mgtSvr[0].mgtSvrIp, e)) > 'TestSnapshots' object has no attribute 'config' > >> begin captured logging << > testclient.testcase.TestSnapshots: DEBUG: Creating a Snapshot from data > volume: 53efb886-b2f8-4420-af47-cb8017eb8f54 > - >> end captured logging << - -- 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-4405) (Upgrade) Migrate failed between existing hosts and new hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753310#comment-13753310 ] Prasanna Santhanam commented on CLOUDSTACK-4405: Note to include the cloudstack-agent-upgrade in release docs. Added doc bug CLOUDSTACK-4450 which needs information after verification of this bug. > (Upgrade) Migrate failed between existing hosts and new hosts > - > > Key: CLOUDSTACK-4405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 > Environment: CS 4.1 >Reporter: Wei Zhou >Assignee: edison su >Priority: Blocker > Fix For: 4.1.1, 4.2.0, 4.2.1 > > > There are two hosts (cs-kvm001, cs-kvm002) in old 2.2.14 environment . > After upgrade from 2.2.14 to 4.1, I added two new hosts (cs-kvm003, > cs-kvm004). > The migration between cs-kvm001 and cs-kvm002, or cs-kvm003 and cs-kvm004 > succeed. > However, the migration from cs-kvm001/002 to the new hosts (cs-kvm003, > cs-kvm004) failed. > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) nic=[Nic:Guest-10.11.110.231-vlan://110] > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) creating a vlan dev and bridge for guest > traffic per traffic label cloudbr0 > 2013-08-19 16:57:31,051 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Executing: /bin/bash -c brctl show | grep > cloudVirBr110 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Exit value is 1 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) > 2013-08-19 16:57:31,063 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 110 -p > em1 -b brem1-110 -o add > 2013-08-19 16:57:31,121 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Execution is successful. > 2013-08-19 16:57:31,122 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Set name-type for VLAN subsystem. Should be > visible in /proc/net/vlan/config > This is because the bridge name on old hosts are cloudVirBr110, and brem1-110 > on new hosts. -- 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] [Comment Edited] (CLOUDSTACK-4405) (Upgrade) Migrate failed between existing hosts and new hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753310#comment-13753310 ] Prasanna Santhanam edited comment on CLOUDSTACK-4405 at 8/29/13 5:17 AM: - Note to include the cloudstack-agent-upgrade in release docs. Added doc bug CLOUDSTACK-4550 which needs information after verification of this bug. was (Author: tsp): Note to include the cloudstack-agent-upgrade in release docs. Added doc bug CLOUDSTACK-4450 which needs information after verification of this bug. > (Upgrade) Migrate failed between existing hosts and new hosts > - > > Key: CLOUDSTACK-4405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 > Environment: CS 4.1 >Reporter: Wei Zhou >Assignee: edison su >Priority: Blocker > Fix For: 4.1.1, 4.2.0, 4.2.1 > > > There are two hosts (cs-kvm001, cs-kvm002) in old 2.2.14 environment . > After upgrade from 2.2.14 to 4.1, I added two new hosts (cs-kvm003, > cs-kvm004). > The migration between cs-kvm001 and cs-kvm002, or cs-kvm003 and cs-kvm004 > succeed. > However, the migration from cs-kvm001/002 to the new hosts (cs-kvm003, > cs-kvm004) failed. > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) nic=[Nic:Guest-10.11.110.231-vlan://110] > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) creating a vlan dev and bridge for guest > traffic per traffic label cloudbr0 > 2013-08-19 16:57:31,051 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Executing: /bin/bash -c brctl show | grep > cloudVirBr110 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Exit value is 1 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) > 2013-08-19 16:57:31,063 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 110 -p > em1 -b brem1-110 -o add > 2013-08-19 16:57:31,121 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Execution is successful. > 2013-08-19 16:57:31,122 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Set name-type for VLAN subsystem. Should be > visible in /proc/net/vlan/config > This is because the bridge name on old hosts are cloudVirBr110, and brem1-110 > on new hosts. -- 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-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-4550: --- Component/s: Doc > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, KVM, Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename > the bridges to allow migration to work between host added before upgrade to > those added after upgrade > This can be done by running the cloudstack-agent-upgrade script -- 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-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-4550: --- Component/s: KVM > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename > the bridges to allow migration to work between host added before upgrade to > those added after upgrade > This can be done by running the cloudstack-agent-upgrade script -- 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-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
Prasanna Santhanam created CLOUDSTACK-4550: -- Summary: [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work Key: CLOUDSTACK-4550 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Prasanna Santhanam Priority: Critical See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as part of upgrade in release notes once the fix for the bug is verified to work After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename the bridges to allow migration to work between host added before upgrade to those added after upgrade This can be done by running the cloudstack-agent-upgrade script -- 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-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-4550: --- Component/s: Upgrade > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename > the bridges to allow migration to work between host added before upgrade to > those added after upgrade > This can be done by running the cloudstack-agent-upgrade script -- 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-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam updated CLOUDSTACK-4550: --- Affects Version/s: 4.2.0 > [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have > migration work > -- > > Key: CLOUDSTACK-4550 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550 > 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 > > See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as > part of upgrade in release notes once the fix for the bug is verified to work > After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN rename > the bridges to allow migration to work between host added before upgrade to > those added after upgrade > This can be done by running the cloudstack-agent-upgrade script -- 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-4534) [object_store_refactor] Deleting uploaded volume is not deleting the volume from backend
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-4534: --- Priority: Major (was: Critical) > [object_store_refactor] Deleting uploaded volume is not deleting the volume > from backend > > > Key: CLOUDSTACK-4534 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4534 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, Volumes >Affects Versions: 4.2.1 > Environment: git rev-parse HEAD~5 > 1f46bc3fb09aead2cf1744d358fea7adba7df6e1 > Cluster: VMWare > Storage: NFS >Reporter: Sanjeev N > Fix For: 4.2.1 > > Attachments: cloud.dmp, management-server.rar > > > Deleting uploaded volume is not deleting the volume from backend and not > marking removed field in volumes table. > Steps to Reproduce: > > 1.Bring up CS with vmware cluster using NFS for both primary and secondary > storage > 2.Upload one volume using uploadVolume API > 3.When the volume is in "Uploaded" state try to delete the volume > Result: > == > from volume_store_ref volume entry got deleted but volume was not deleted > from secondary storage and removed filed was not set in volumes table. > Observations: > === > Log snippet from management server log file as follows: > 2013-08-28 03:18:08,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) > ===START=== 10.146.0.131 -- GET > command=deleteVolume&id=e9ee6c0d-d149-4771-a494-6efda849b2ce&response=json&sessionkey=vNQ7kc2GdEuxzKje8MQ2xSAqbAQ%3D&_=1377674288184 > 2013-08-28 03:18:08,414 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-20:null) Access granted to Acct[2-admin] to Domain:1/ by > AffinityGroupAccessChecker_EnhancerByCloudStack_86df51a8 > 2013-08-28 03:18:08,421 INFO [cloud.resourcelimit.ResourceLimitManagerImpl] > (catalina-exec-20:null) Discrepency in the resource count (original > count=77179526656 correct count = 78867689472) for type secondary_storage for > account ID 2 is fixed during resource count recalculation. > 2013-08-28 03:18:08,446 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) > ===END=== 10.146.0.131 -- GET > command=deleteVolume&id=e9ee6c0d-d149-4771-a494-6efda849b2ce&response=json&sessionkey=vNQ7kc2GdEuxzKje8MQ2xSAqbAQ%3D&_=1377674288184 > 2013-08-28 03:18:32,766 DEBUG [cloud.storage.StorageManagerImpl] > (StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 > templates to clean up in storage pool: pri_esx_306 > 2013-08-28 03:18:32,772 DEBUG [cloud.storage.StorageManagerImpl] > (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 > templates to cleanup on template_store_ref for store: > 37f6be5b-0899-48b4-9fd8-1fe483f47c0e > 2013-08-28 03:18:32,774 DEBUG [cloud.storage.StorageManagerImpl] > (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 > snapshots to cleanup on snapshot_store_ref for store: > 37f6be5b-0899-48b4-9fd8-1fe483f47c0e > 2013-08-28 03:18:32,776 DEBUG [cloud.storage.StorageManagerImpl] > (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 1 > volumes to cleanup on volume_store_ref for store: > 37f6be5b-0899-48b4-9fd8-1fe483f47c0e > 2013-08-28 03:18:32,777 DEBUG [cloud.storage.StorageManagerImpl] > (StorageManager-Scavenger-1:null) Deleting volume store DB entry: > VolumeDataStore[2-20-2volumes/2/20/7e5778fd-c4bf-35b3-9e7a-9ab8500ab469.ova] > Volume in the backend: > [root@Rhel63-Sanjeev 20]# pwd > /tmp/nfs/sec_306/volumes/2/20 > [root@Rhel63-Sanjeev 20]# ls -l > total 898008 > -rwxrwxrwx+ 1 root root 459320832 Aug 27 13:57 > 7e5778fd-c4bf-35b3-9e7a-9ab8500ab469.ova > -rwxrwxrwx+ 1 root root 459312128 Sep 17 2010 CentOS5.3-x86_64-disk1.vmdk > -rwxrwxrwx+ 1 root root 147 Sep 17 2010 CentOS5.3-x86_64.mf > -rwxrwxrwx+ 1 root root 5340 Sep 17 2010 CentOS5.3-x86_64.ovf > -rwxrwxrwx+ 1 root root 340 Aug 27 13:58 volume.properties > [root@Rhel63-Sanjeev 20]# > Attaching management server log file and cloud db. -- 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-4492) [object_store_ref] Attaching volume to a vm is failing after upgrade if the volume was uploaded before upgrade
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-4492:
---
Priority: Major (was: Critical)
> [object_store_ref] Attaching volume to a vm is failing after upgrade if the
> volume was uploaded before upgrade
> ---
>
> Key: CLOUDSTACK-4492
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4492
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, Volumes
>Affects Versions: 4.2.1
> Environment: Build is from commit
> :a6bf80216466ada185de7e04d3e64be4e25c11a7
> Upgrade from 3.0.6 to 4.2
>Reporter: Sanjeev N
>Assignee: edison su
> Fix For: 4.2.1
>
> Attachments: cloud.dmp, cloud.dmp, management-server.rar,
> management-server.rar
>
>
> Failing to attach a volume to a vm after upgrade if it was uploaded before
> upgrade.
> Steps to Reproduce:
>
> 1.Bring up CS with VMWare cluster using 3.0.6 GA build
> 2.upload volume using API:
> http://10.147.59.126:8096/client/api?command=uploadVolume&format=OVA&name=cent53-upload-BU&url=http://10.147.28.7/templates/vmware/CentOS5.3-x86_64.ova&zoneid=9076c21d-d0c4-4cee-9820-2a551b65616e&account=admin&domainid=1
> 3.Upgrade to 4.2
> 4.Deploy one vm with root disk
> 5.Try to attach the volume uploaded at step2 to vm created above
> Result:
> =
> Attaching volume failed with InvalidParameterValueException
> Observations:
> ===
> Uploaded volume has state set to "UploadOp" in volumes table. However
> AttachVolumeCmd is checking for volume state to be either in Allocated, Ready
> or in Uploaded state. So attaching is failing.
> Following is the log snippet:
> 2013-08-26 01:36:30,254 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===START=== 10.146.0.131 -- GET
> command=attachVolume&id=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7e&virtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982a&response=json&sessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D&_=1377495389690
> 2013-08-26 01:36:30,405 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-189 = [
> 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ], details: AsyncJobVO {id:189, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 20, cmd:
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","id":"55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7e","sessionkey":"u8uFWRNIgqqVZ+/BLCQbaSfZMCw\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"ce3c8eb5-05f9-445b-ab74-68751e8a982a","httpmethod":"GET","_":"1377495389690","ctxAccountId":"2","ctxStartEventId":"2015"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-08-26 01:36:30,408 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
> ===END=== 10.146.0.131 -- GET
> command=attachVolume&id=55cd0b1d-cf01-4fff-b6a1-d2d3f6d90d7e&virtualMachineId=ce3c8eb5-05f9-445b-ab74-68751e8a982a&response=json&sessionkey=u8uFWRNIgqqVZ%2B%2FBLCQbaSfZMCw%3D&_=1377495389690
> 2013-08-26 01:36:30,410 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ]
> 2013-08-26 01:36:30,468 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-157:job-189 = [ 0a33a5ee-9c58-4791-a0e5-cf6a070d9fc1 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.exception.InvalidParameterValueException: Volume state must be in
> Allocated, Ready or in Uploaded state
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1807)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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.c
[jira] [Updated] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4546: - Fix Version/s: (was: 4.2.0) > [Vmware] - Unable to deploy guest VM > > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > 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, 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-0
[jira] [Updated] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4546: - Affects Version/s: (was: 4.2.0) > [Vmware] - Unable to deploy guest VM > > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-08-2
[jira] [Updated] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-3765: - Assignee: frank zhang (was: Sudha Ponnaganti) > [packaging][document] unable to upgrade cp 4.2 build on centos5.5 > - > > Key: CLOUDSTACK-3765 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, Packaging >Affects Versions: 4.2.0 > Environment: Centos5.5 >Reporter: shweta agarwal >Assignee: frank zhang >Priority: Critical > Fix For: 4.2.0 > > Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf > > > When I am trying to install > http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz > > I am hitting JSVC dependency error > When I tried to install jsvc via rpm its also failing giving error > rpm -Uvh > http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > Retrieving > http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key > ID c105b9de > error: Failed dependencies: > rpmlib(FileDigests) <= 4.6.0-1 is needed by > jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64 > rpmlib(PayloadIsXz) <= 5.2-1 is needed by > jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64 > Centos 5.5 repo does not contain any jsvc package > Infact at rpmfind location also JSVC package only exists for centos6.4 > http://rpmfind.net/linux/rpm2html/search.php?query=jsvc -- 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-4517) [upgrade][Vmware]Deployment of VM using template registered before upgrade is failing.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-4517: -- Assignee: Nitin Mehta (was: Min Chen) > [upgrade][Vmware]Deployment of VM using template registered before upgrade is > failing. > -- > > Key: CLOUDSTACK-4517 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4517 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade, VMware >Affects Versions: 4.2.0 > Environment: upgraded from 3.07 to 4.2 >Reporter: manasaveloori >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.zip, mysqldumpAfterUp.dmp, > mysqldumpBeforeUp.dmp > > > Steps: > 1.Have CS with 3.0.7 build. > 2.Register a template > id: 10 > store_id: 2 > template_id: 204 > created: 2013-08-27 12:13:34 > last_updated: 2013-08-27 16:05:45 > job_id: e7c32b26-3e06-4a9e-a9d0-cd6452595659 > download_pct: 100 > size: 107374182400 > store_role: Image >physical_size: 707778560 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/27/13 6:54 AM > local_path: > /mnt/SecStorage/0e8da06e-0788-3efb-86a6-b0705a2205d3/template/tmpl/2/204/dnld4711105428993449674tmp_ > install_path: > template/tmpl/2/204/dec94d02-8c40-34e8-9a1d-99906a95df2a.ova > url: http://10.147.28.7/templates/vmware/Centos6_2.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > 5 rows in set (0.00 sec) > 3.Upgrade the build to 4.2. > 4.Deploy a VM using the template registered before upgrade. > Observation: > Observed the following exception: > 2013-08-27 23:08:37,892 ERROR [storage.resource.VmwareStorageProcessor] > (DirectAgent-101:10.147.40.28) clone volume from base image failed due to > Exception: javax.xml.ws.WebServiceException > Message: java.net.SocketTimeoutException: Read timed out > javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed > out > at > com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:201) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151) > at > com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83) > at > com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:78) > at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587) > at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546) > at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531) > at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428) > at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211) > at > com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) > at $Proxy90.waitForUpdates(Unknown Source) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:428) > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:371) > at > com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:594) > at > com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:293) > at > com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:384) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:73) > at > com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147) > at > com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:561) > at >
[jira] [Created] (CLOUDSTACK-4549) ceph:deployvm from template created from snapshot is failing
sadhu suresh created CLOUDSTACK-4549:
Summary: ceph:deployvm from template created from snapshot is
failing
Key: CLOUDSTACK-4549
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4549
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: sadhu suresh
Priority: Critical
VM deployment form template which is created form snapshot is failing where as
VM deployment with uploaded template successful.
created template form snapshot is storing in raw
format(https://10-147-49-100.realhostip.com/userdata/0c826645-ec82-40f1-a1b0-38fc9ba1c76f.raw)..
not sure are we converting again to QCwo2
when we try to deploy a VM
steps:
1.create a ceph instance(configure compute offering with RBD and deploy a vm)
2.Once it successful,select the root partition and perform snapshot
3.once snapshot successful,create a template from snapshot
4 try to create vm uning above VM
actual result:
deploy vm failing with exception
-29 15:21:43,756 DEBUG [cloud.network.NetworkModelImpl] (Job-Executor-14:job-42
= [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service SecurityGroup is not
supported in the network id=204
2013-08-29 15:21:43,762 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-14:job-42 = [
3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Applying userdata and password entry in
network Ntwk[204|Guest|8]
2013-08-29 15:21:43,800 DEBUG [agent.transport.Request] (Job-Executor-14:job-42
= [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq 1-2089159931: Sending { Cmd ,
MgmtId: 7175246184473, via: 1, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.routing.SavePasswordCommand":{"password":"fnirq_cnffjbeq","vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}},{"com.cloud.agent.api.routing.VmDataCommand":{"vmIpAddress":"10.1.1.140","vmName":"6e798618-8e4d-4305-94a1-642e5f3aad08","executeInSequence":true,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.2.248","router.name":"r-15-VM"},"wait":0}}]
}
2013-08-29 15:21:44,168 DEBUG [agent.transport.Request]
(AgentManager-Handler-14:null) Seq 1-2089159931: Processing: { Ans: , MgmtId:
7175246184473, via: 1, Ver: v1, Flags: 110,
[{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}]
}
2013-08-29 15:21:44,169 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-14:null) Seq 1-2089159931: No more commands found
2013-08-29 15:21:44,169 DEBUG [agent.transport.Request] (Job-Executor-14:job-42
= [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Seq 1-2089159931: Received: { Ans:
, MgmtId: 7175246184473, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-08-29 15:21:44,179 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Service
SecurityGroup is not supported in the network id=204
2013-08-29 15:21:44,182 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Checking if
we need to prepare 1 volumes for VM[User|6e798618-8e4d-4305-94a1-642e5f3aad08]
2013-08-29 15:21:44,207 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template
202 is already in store:1, type:Image
2013-08-29 15:21:44,219 DEBUG [storage.datastore.PrimaryDataStoreImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Not found
(templateId:202poolId:5) in template_spool_ref, persisting it
2013-08-29 15:21:44,234 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) template
202 is already in store:5, type:Primary
2013-08-29 15:21:44,237 DEBUG [storage.volume.VolumeServiceImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Found
template 246c1e4ac-9fc0-3122-bcfb-77deff789f61 in storage pool 5 with
VMTemplateStoragePool id: 5
2013-08-29 15:21:44,433 DEBUG [storage.volume.VolumeServiceImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) Acquire
lock on VMTemplateStoragePool 5 with timeout 3600 seconds
2013-08-29 15:21:44,438 INFO [storage.volume.VolumeServiceImpl]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) lock is
acquired for VMTemplateStoragePool 5
2013-08-29 15:21:44,466 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-14:job-42 = [ 3dcbbb22-d258-4859-bf3f-c8a620768e25 ]) copyAsync
inspecting src type TEMPLATE copyAsync inspecting dest type TEMPLATE
2013-08-29 15:21:44,547 DEBUG [agent.transp
[jira] [Closed] (CLOUDSTACK-4249) [KVM]ceph:showing wrong template size 755.64 TB(template created from snapshot)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-4249. verified in the new build and found to be OK.so closing this issue. > [KVM]ceph:showing wrong template size 755.64 TB(template created from > snapshot) > --- > > Key: CLOUDSTACK-4249 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4249 > 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: sadhu suresh >Assignee: Wido den Hollander >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.rar > > > 1.create a ceph instance(configure compute offering with RBD and deploy a vm) > 2.Once it successful,select the root partition and perform snapshot > 3.once snapshot successful,create a template from snapshot > 4.check the displayed size for new created template form snapshot > 5.also try to create vm uning above VM > Actual result: > vm deployment fails due to wrong template size. > Template size shows "755.64 TB" > one ID6ec00b45-7913-4095-944b-d0fa16adb84a > Description tempfromcs > HypervisorKVM > Type USER > Ready Yes > StatusDownload Complete > Size 755.64 TB > Extractable Yes > Password Enabled No > Dynamically Scalable No > PublicYes > Featured No > Cross Zones No > OS Type CentOS 5.3 (64-bit) > DomainROOT > Account admin > Created Mon, 12 Aug 2013 12:50:46 GMT > ** 12. row *** > id: 202 > unique_name: 2e9a6a5aa-7e78-33c8-ac61-25846b624569 > name: tempfromcs > uuid: 2c45fa1b-647c-40d2-b532-4b7cafadf2c3 > public: 1 > featured: 0 > type: USER > hvm: 1 > bits: 64 > url: NULL > format: QCOW2 > created: 2013-08-12 12:50:46 > removed: NULL > account_id: 2 > checksum: NULL > display_text: tempfromcs > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 0 > extractable: 1 > hypervisor_type: KVM > source_template_id: 0 > template_tag: NULL > sort_key: 0 > size: 830839581640192 >state: NULL > update_count: 0 > updated: NULL > dynamically_scalable: 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] [Updated] (CLOUDSTACK-4546) [Vmware] - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4546: - Summary: [Vmware] - Unable to deploy guest VM (was: [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM) > [Vmware] - Unable to deploy guest VM > > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > 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, 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.0, 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.Threa
[jira] [Commented] (CLOUDSTACK-4547) admin login/password incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753283#comment-13753283 ] Marcus Sorensen commented on CLOUDSTACK-4547: - This is sometimes seen when the mgmt server doesn't come up completely. You may want to look at your mgmt server logs and see if it looks healthy or if it got stuck. > admin login/password incorrect > --- > > Key: CLOUDSTACK-4547 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4547 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.1 > Environment: Cent OS 6.4 with Apache Cloud Stack 4.1.1 >Reporter: Amit Kumar > Labels: patch > Original Estimate: 12h > Remaining Estimate: 12h > > I had install Apache Cloud Stack 4.1.1 - 20 Times but still getting the > same error "admin login/password incorrect" using default login & password > as per official Apache doc. admin/password. > Please help me out -- 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-4548) How can I create a "bucket" like Amazon S3 in cloudstack?
Tony Luk created CLOUDSTACK-4548: Summary: How can I create a "bucket" like Amazon S3 in cloudstack? Key: CLOUDSTACK-4548 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4548 Project: CloudStack Issue Type: Wish Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0 Environment: My operating system is using Centos6.4 Reporter: Tony Luk How can I create a "bucket" like Amazon S3 in cloudstack so that user can backup/browse through website? Thanks. -- 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-4434) EN: Ubuntu: Direct input "- _ ", "? /", "keyboard /" ,"keyboard -" keys are not working well for the US keyboard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi resolved CLOUDSTACK-4434. Resolution: Fixed Fixed in 4.2-forward > EN: Ubuntu: Direct input "- _ ", "? /", "keyboard /" ,"keyboard -" keys are > not working well for the US keyboard. > - > > Key: CLOUDSTACK-4434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Affects Versions: 4.2.0 > Environment: Environment > Build#CloudPlatform-4.2-465(CloudPlatform-4.2-465-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS, CS-Mgr Servers. > Client & Browser: Ubuntu-Firefox23.0, Win7-Firefox23.0, Win7-Chrome, Win7-IE, > Mac-Safari >Reporter: Minying Bao >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.1 > > Attachments: EN_Ubuntu VM_Outputting Endless.jpg > > > Repro Steps > 1. Setup the CloudStack environments with build 4.2#465. > 2. Bring ubuntu VM. > 3. Access the VM via Console Proxy from the Ubuntu client machine connected > to US Keyboard. > 4. Hit all the keys with US keyboard. > Expected Result > All the keys should work fine. > Actual Result > First time, press the "- _ ", "? /", "keyboard /" ,"keyboard -" keys. > It seemed that the output for those keys will keep on outputting endless. > Even if we have stopped pressing the key. (Refer to attached screenshot.) > We could press "Enter" to stop the endless outputting. > Then, try to press the four keys again, the keys were not working at all. > Client/Browser Info. > Ubuntu-FF23.0 -> Fail > Win7-FF22.0 -> Fail > Win7-Chrome -> Fail > Win7-IE -> Fail > Mac-Safari -> Fail -- 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-4434) EN: Ubuntu: Direct input "- _ ", "? /", "keyboard /" ,"keyboard -" keys are not working well for the US keyboard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753185#comment-13753185 ] Animesh Chaturvedi commented on CLOUDSTACK-4434: As with any other fix, we need everything on master. Vijay can you put the patch on master as well > EN: Ubuntu: Direct input "- _ ", "? /", "keyboard /" ,"keyboard -" keys are > not working well for the US keyboard. > - > > Key: CLOUDSTACK-4434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Affects Versions: 4.2.0 > Environment: Environment > Build#CloudPlatform-4.2-465(CloudPlatform-4.2-465-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS, CS-Mgr Servers. > Client & Browser: Ubuntu-Firefox23.0, Win7-Firefox23.0, Win7-Chrome, Win7-IE, > Mac-Safari >Reporter: Minying Bao >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.1 > > Attachments: EN_Ubuntu VM_Outputting Endless.jpg > > > Repro Steps > 1. Setup the CloudStack environments with build 4.2#465. > 2. Bring ubuntu VM. > 3. Access the VM via Console Proxy from the Ubuntu client machine connected > to US Keyboard. > 4. Hit all the keys with US keyboard. > Expected Result > All the keys should work fine. > Actual Result > First time, press the "- _ ", "? /", "keyboard /" ,"keyboard -" keys. > It seemed that the output for those keys will keep on outputting endless. > Even if we have stopped pressing the key. (Refer to attached screenshot.) > We could press "Enter" to stop the endless outputting. > Then, try to press the four keys again, the keys were not working at all. > Client/Browser Info. > Ubuntu-FF23.0 -> Fail > Win7-FF22.0 -> Fail > Win7-Chrome -> Fail > Win7-IE -> Fail > Mac-Safari -> Fail -- 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-4519) hitting java.lang.RuntimeException during volume deletion of router vm in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753178#comment-13753178
]
ASF subversion and git services commented on CLOUDSTACK-4519:
-
Commit a316ffa27f84c261cace319829c3aaf52e6a in branch
refs/heads/4.2-forward from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a316ffa ]
CLOUDSTACK-4519: reimplementdestroy-volume to take consideration of on-disk
snapshot
> hitting java.lang.RuntimeException during volume deletion of router vm in
> vmware
>
>
> Key: CLOUDSTACK-4519
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4519
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade, VMware
>Affects Versions: 4.2.1
>Reporter: shweta agarwal
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp,
> management-server-router.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 .
> Having two advance zone
> 1 with EXI 4.1
> second with xen
> With vmware zone i stopped router vm
> and StorageManager-Scavenger tried to delete volume to rotuer vm and hit
> follwoing exception
> MS log snippet :
> 2013-08-27 14:11:01,148 ERROR [storage.resource.VmwareStorageProcessor]
> (DirectAgent-28:10.147.40.27) delete volume failed due to Exception:
> java.lang.RuntimeException
> Message: Cannot delete file [d9a91dba343e38dcbbe169a3f57fd335]
> r-24-VM/ROOT-24-flat.vmdk
> java.lang.RuntimeException: Cannot delete file
> [d9a91dba343e38dcbbe169a3f57fd335] r-24-VM/ROOT-24-flat.vmdk
> at
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
> at
> com.cloud.hypervisor.vmware.mo.DatastoreMO.deleteFile(DatastoreMO.java:175)
> at
> com.cloud.storage.resource.VmwareStorageLayoutHelper.deleteVolumeVmdkFiles(VmwareStorageLayoutHelper.java:237)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.deleteVolume(VmwareStorageProcessor.java:1548)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:114)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:53)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:561)
> 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:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-08-27 14:11:01,149 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-28:null) Seq 5-982581483: Response Received:
> 2013-08-27 14:11:01,149 DEBUG [agent.transport.Request] (DirectAgent-28:null)
> Seq 5-982581483: Processing: { Ans: , MgmtId: 7217726095403, via: 5, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"delete volume
> failed due to Exception: java.lang.RuntimeException\nMessage: Cannot delete
> file [d9a91dba343e38dcbbe169a3f57fd335]
> r-24-VM/ROOT-24-flat.vmdk\n","wait":0}}] }
> 2013-08-27 14:11:01,150 DEBUG [agent.transport.Request]
> (StorageManager-Scavenger-1:null) Seq 5-982581483: Received: { Ans: ,
> MgmtId: 7217726095403, via: 5, Ver: v1, Flags: 10, { Answer } }
--
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-4519) hitting java.lang.RuntimeException during volume deletion of router vm in vmware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelven Yang resolved CLOUDSTACK-4519.
-
Resolution: Fixed
> hitting java.lang.RuntimeException during volume deletion of router vm in
> vmware
>
>
> Key: CLOUDSTACK-4519
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4519
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade, VMware
>Affects Versions: 4.2.1
>Reporter: shweta agarwal
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp,
> management-server-router.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 .
> Having two advance zone
> 1 with EXI 4.1
> second with xen
> With vmware zone i stopped router vm
> and StorageManager-Scavenger tried to delete volume to rotuer vm and hit
> follwoing exception
> MS log snippet :
> 2013-08-27 14:11:01,148 ERROR [storage.resource.VmwareStorageProcessor]
> (DirectAgent-28:10.147.40.27) delete volume failed due to Exception:
> java.lang.RuntimeException
> Message: Cannot delete file [d9a91dba343e38dcbbe169a3f57fd335]
> r-24-VM/ROOT-24-flat.vmdk
> java.lang.RuntimeException: Cannot delete file
> [d9a91dba343e38dcbbe169a3f57fd335] r-24-VM/ROOT-24-flat.vmdk
> at
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
> at
> com.cloud.hypervisor.vmware.mo.DatastoreMO.deleteFile(DatastoreMO.java:175)
> at
> com.cloud.storage.resource.VmwareStorageLayoutHelper.deleteVolumeVmdkFiles(VmwareStorageLayoutHelper.java:237)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.deleteVolume(VmwareStorageProcessor.java:1548)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:114)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:53)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:561)
> 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:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-08-27 14:11:01,149 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-28:null) Seq 5-982581483: Response Received:
> 2013-08-27 14:11:01,149 DEBUG [agent.transport.Request] (DirectAgent-28:null)
> Seq 5-982581483: Processing: { Ans: , MgmtId: 7217726095403, via: 5, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"delete volume
> failed due to Exception: java.lang.RuntimeException\nMessage: Cannot delete
> file [d9a91dba343e38dcbbe169a3f57fd335]
> r-24-VM/ROOT-24-flat.vmdk\n","wait":0}}] }
> 2013-08-27 14:11:01,150 DEBUG [agent.transport.Request]
> (StorageManager-Scavenger-1:null) Seq 5-982581483: Received: { Ans: ,
> MgmtId: 7217726095403, via: 5, Ver: v1, Flags: 10, { Answer } }
--
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-4458) [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelven Yang resolved CLOUDSTACK-4458. - Resolution: Fixed > [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot > exception > > > Key: CLOUDSTACK-4458 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4458 > 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: Rayees Namathponnan >Assignee: Kelven Yang >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox.png > > > == > Steps to Reproduce the Bug: > == > 1. Deploy a VM using the default CentOS Template > 2. Create and attach a volume to the deployed VM as its data disk. > 3. Create File System on it and generate few files on the data disk. > 4. Stop the VM. > 5. Take the Snapshot of the Data disk. > = > Observation on Management Server Logs: > = > 2013-08-22 11:37:53,960 DEBUG [storage.snapshot.SnapshotManagerImpl] > (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Failed to > create snapshot > com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: > Exception: java.lang.RuntimeException > Message: File > []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was > not found > at > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281) > at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137) > at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:256) > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1004) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) > at > com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) > at > org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-08-22 11:37:53,970 DEBUG [storage.volume.VolumeServiceImpl] > (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Take > snapshot: 28 failed > com.cloud.utils.exception.CloudRuntimeException: Failed to create snapshot > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1029) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) > at > com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) > at > org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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) > Caused by: com.cloud.utils.exception.CloudRuntimeException: backup snapshot > exception: Exception: java.lang.RuntimeException > Message: File > []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was > not found > at > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.ja
[jira] [Commented] (CLOUDSTACK-4458) [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753177#comment-13753177 ] ASF subversion and git services commented on CLOUDSTACK-4458: - Commit 995e193be2a1aad8ffe0eeb03357e23fb5c63769 in branch refs/heads/4.2-forward from [~kelveny] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=995e193 ] CLOUDSTACK-4458: Volume attach/detach command needs to sent to hypervisor resource even when target VM is in Stopped state > [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot > exception > > > Key: CLOUDSTACK-4458 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4458 > 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: Rayees Namathponnan >Assignee: Kelven Yang >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox.png > > > == > Steps to Reproduce the Bug: > == > 1. Deploy a VM using the default CentOS Template > 2. Create and attach a volume to the deployed VM as its data disk. > 3. Create File System on it and generate few files on the data disk. > 4. Stop the VM. > 5. Take the Snapshot of the Data disk. > = > Observation on Management Server Logs: > = > 2013-08-22 11:37:53,960 DEBUG [storage.snapshot.SnapshotManagerImpl] > (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Failed to > create snapshot > com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: > Exception: java.lang.RuntimeException > Message: File > []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was > not found > at > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281) > at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137) > at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:256) > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1004) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) > at > com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) > at > org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-08-22 11:37:53,970 DEBUG [storage.volume.VolumeServiceImpl] > (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Take > snapshot: 28 failed > com.cloud.utils.exception.CloudRuntimeException: Failed to create snapshot > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1029) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280) > at > com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703) > at > org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.lan
[jira] [Resolved] (CLOUDSTACK-4513) [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to come
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi resolved CLOUDSTACK-4513. Resolution: Invalid Resolving as invalid as per Vijay's comments based on setup issue > [Vmware] new mapping vmware datacenter cloudstack zone - Host in second > cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated > failed to come up > --- > > Key: CLOUDSTACK-4513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4513 > 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: MS10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.log.gz, management-server.log.gz, > Screenshot-CloudPlatform™ - Mozilla Firefox-1.png, Screenshot-CloudPlatform™ > - Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-9.png, > Screenshot-CloudPlatform™ - Mozilla Firefox.png > > > 1. > Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 > 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H310.223.51.4 has SSVM CPVM and VMs i-2-8i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. > These remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > -- 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-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753173#comment-13753173 ] ASF subversion and git services commented on CLOUDSTACK-4539: - Commit e6247e712588903b77313b50750e9a0e7d0cf2af in branch refs/heads/master from [~vijayendrabvs] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e6247e7 ] CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone Description: Do not overwrite value of vmware.create.full.clone flag in the cloud db if it already exists. This will preserve the configured clone creation behaviour across upgrades. > [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default > nature of vms are full clone > --- > > Key: CLOUDSTACK-4539 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 > 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: prashant kumar mishra >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > > In upgraded setup vm should get deployed as linked clone ,default value of > global parameter vmware.create.full.clone should be false in upgraded setup. -- 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-4546) [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4546: - Fix Version/s: 4.2.1 > [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy > guest VM > -- > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > 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, 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.0, 4.2.1 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.r
[jira] [Updated] (CLOUDSTACK-4546) [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4546: - Affects Version/s: 4.2.1 > [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy > guest VM > -- > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > 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, 4.2.1 > Environment: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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(
[jira] [Resolved] (CLOUDSTACK-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Siva Vijayendra Bhamidipati resolved CLOUDSTACK-4539. - Resolution: Fixed > [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default > nature of vms are full clone > --- > > Key: CLOUDSTACK-4539 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 > 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: prashant kumar mishra >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > > In upgraded setup vm should get deployed as linked clone ,default value of > global parameter vmware.create.full.clone should be false in upgraded setup. -- 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-4539) [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753168#comment-13753168 ] ASF subversion and git services commented on CLOUDSTACK-4539: - Commit a30a33c14d38a30840be19619c9aff65ed14cf2f in branch refs/heads/4.2-forward from [~vijayendrabvs] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a30a33c ] CLOUDSTACK-4539: [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default nature of vms are full clone Description: Do not overwrite value of vmware.create.full.clone flag in the cloud db if it already exists. This will preserve the configured clone creation behaviour across upgrades. > [VMWARE] vmware.create.full.clone is set to true in upgraded setup;default > nature of vms are full clone > --- > > Key: CLOUDSTACK-4539 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4539 > 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: prashant kumar mishra >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > > In upgraded setup vm should get deployed as linked clone ,default value of > global parameter vmware.create.full.clone should be false in upgraded setup. -- 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-4547) admin login/password incorrect
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753141#comment-13753141
]
Amit Kumar commented on CLOUDSTACK-4547:
Thanks for your response & yes i had tried both Caps & Small { admin / Password
}
> admin login/password incorrect
> ---
>
> Key: CLOUDSTACK-4547
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4547
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.1.1
> Environment: Cent OS 6.4 with Apache Cloud Stack 4.1.1
>Reporter: Amit Kumar
> Labels: patch
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> I had install Apache Cloud Stack 4.1.1 - 20 Times but still getting the
> same error "admin login/password incorrect" using default login & password
> as per official Apache doc. admin/password.
> Please help me out
--
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-4547) admin login/password incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753132#comment-13753132 ] Jonathan Creasy commented on CLOUDSTACK-4547: - Did you try "Admin" as the username? https://issues.apache.org/jira/browse/CLOUDSTACK-4359 > admin login/password incorrect > --- > > Key: CLOUDSTACK-4547 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4547 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.1 > Environment: Cent OS 6.4 with Apache Cloud Stack 4.1.1 >Reporter: Amit Kumar > Labels: patch > Original Estimate: 12h > Remaining Estimate: 12h > > I had install Apache Cloud Stack 4.1.1 - 20 Times but still getting the > same error "admin login/password incorrect" using default login & password > as per official Apache doc. admin/password. > Please help me out -- 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-4541) MS:Template:Snapshot Templates created from Snapshot gets removed upon MS Restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen resolved CLOUDSTACK-4541. -- Resolution: Incomplete > MS:Template:Snapshot Templates created from Snapshot gets removed upon MS > Restart > - > > Key: CLOUDSTACK-4541 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4541 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Snapshot, Template >Affects Versions: 4.2.1 > Environment: VMWare >Reporter: Parth Jagirdar >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > Attachments: template.log > > > Create a template from a snapshot. > Deploy a VM using it to verify. > Restart MS.. observer that template is marked as "Ready No". And template is > no longer available under Create Instance wizard. > logs attached. > Template names are : master template clone and new master 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-4541) MS:Template:Snapshot Templates created from Snapshot gets removed upon MS Restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753114#comment-13753114 ] Min Chen commented on CLOUDSTACK-4541: -- Please attach db dump before MS and after MS restart. > MS:Template:Snapshot Templates created from Snapshot gets removed upon MS > Restart > - > > Key: CLOUDSTACK-4541 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4541 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Snapshot, Template >Affects Versions: 4.2.1 > Environment: VMWare >Reporter: Parth Jagirdar >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > Attachments: template.log > > > Create a template from a snapshot. > Deploy a VM using it to verify. > Restart MS.. observer that template is marked as "Ready No". And template is > no longer available under Create Instance wizard. > logs attached. > Template names are : master template clone and new master 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] [Assigned] (CLOUDSTACK-4541) MS:Template:Snapshot Templates created from Snapshot gets removed upon MS Restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Chen reassigned CLOUDSTACK-4541: Assignee: Min Chen > MS:Template:Snapshot Templates created from Snapshot gets removed upon MS > Restart > - > > Key: CLOUDSTACK-4541 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4541 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Snapshot, Template >Affects Versions: 4.2.1 > Environment: VMWare >Reporter: Parth Jagirdar >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > Attachments: template.log > > > Create a template from a snapshot. > Deploy a VM using it to verify. > Restart MS.. observer that template is marked as "Ready No". And template is > no longer available under Create Instance wizard. > logs attached. > Template names are : master template clone and new master 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] [Created] (CLOUDSTACK-4547) admin login/password incorrect
Amit Kumar created CLOUDSTACK-4547: -- Summary: admin login/password incorrect Key: CLOUDSTACK-4547 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4547 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.1 Environment: Cent OS 6.4 with Apache Cloud Stack 4.1.1 Reporter: Amit Kumar I had install Apache Cloud Stack 4.1.1 - 20 Times but still getting the same error "admin login/password incorrect" using default login & password as per official Apache doc. admin/password. Please help me out -- 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-4542) [Automation] Failed to apply DHCP entry in VR and deployment failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753108#comment-13753108
]
Sheng Yang commented on CLOUDSTACK-4542:
It's connection timeout, more like environment issue.
I cannot reproduce it.
> [Automation] Failed to apply DHCP entry in VR and deployment failed
>
>
> Key: CLOUDSTACK-4542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4542
> 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: 4.2-forward
> Automation environment on KVM
>Reporter: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue found in automation run, observed while running the test case
> integration.component.test_vpc_vms_deployment.TestVMDeployVPC.test_02_deploy_vms_delete_network
> Router failed to apply DHCP entry then router deployment reported as failed
> Observed below error in MS log, attached log search for "r-183-QA"
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 2-654837610: Processing: { Ans: , MgmtId:
> 29066118877352, via: 2, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect to
> host 169.254.1.219 port 3922: Connection timed out","wait":0}}] }
> 2013-08-27 22:56:30,877 DEBUG [agent.manager.AgentAttache]
> (AgentManager-Handler-4:null) Seq 2-654837611: Sending now. is current
> sequence.
> 2013-08-27 22:56:30,877 DEBUG [agent.transport.Request]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Seq
> 2-654837610: Received: { Ans: , MgmtId: 29066118877352, via: 2, Ver: v1,
> Flags: 110, { Answer } }
> 2013-08-27 22:56:30,878 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply dhcp entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:2919)
> at
> com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:898)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2070)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-27 22:56:30,882 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-84:job-806 = [ 558e7c87-b3fb-444e-b5e9-85c3789a1318 ]) Cleaning
> up resources for the vm VM[User|df06b516-d40a-4dfa-9b77-4612bed9660e] in
> Starting state
> 2013
[jira] [Resolved] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] frank zhang resolved CLOUDSTACK-4533. - Resolution: Cannot Reproduce please reopen if you can reproduce and leave that environment to me > permission issue in usage server and it failed to start after upgrade from > 3.0.4 to 4.2 > --- > > Key: CLOUDSTACK-4533 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging, Upgrade, Usage >Affects Versions: 4.2.1 > Environment: >Reporter: shweta agarwal >Priority: Blocker > Fix For: 4.2.1 > > Attachments: cloudstack-usage.err, cloudstack-usage.out > > > did an upgrade from 3.0.4 to 4.2 and then start usage server. > Usage server failed to start > giving following exception : > log4j:ERROR setFile(null,true) call failed. > java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log > (Permission denied) > at java.io.FileOutputStream.openAppend(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:207) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) > at > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) > at > org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179) > at > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773) > at > org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901) > at > org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69) > at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89) > at com.cloud.usage.UsageServer.init(UsageServer.java:52) > 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:616) > at > org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207) > log4j:ERROR setFile(null,true) call failed. > java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log > (Permission denied) > at java.io.FileOutputStream.openAppend(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:207) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) > at > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) > at > org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179) > at > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755) > Attaching full logs. > > -- This message is automatically generated by
[jira] [Commented] (CLOUDSTACK-4543) [Automation] Failed to configure VPC router then reported as deployment failure
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753099#comment-13753099
]
Sheng Yang commented on CLOUDSTACK-4543:
I cannot reproduce the issue. It's really basic case for VPC, probably due to
some network connectivity issues?
> [Automation] Failed to configure VPC router then reported as deployment
> failure
> ---
>
> Key: CLOUDSTACK-4543
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4543
> 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: KVM
> 4.2.1-stable branch
>Reporter: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: KVM_Regression_28_Aug_Agent.rar,
> KVM_Regression_28_Aug_MS.rar
>
>
> This issue observed during automation run, VPC router deployment failed
> during network configuration the failed with error
> [{"com.cloud.agent.api.SetupGuestNetworkAnswer":{"result":false,"details":"Creating
> guest network failed due to ","wait":0}}] }
> Here the log from Management server
> 2013-08-28 05:09:27,760 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Network
> id=473 is shutdown successfully, cleaning up corresponding resources now.
> 2013-08-28 05:09:27,762 DEBUG [network.guru.GuestNetworkGuru]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ])
> Releasing vnet for the network id=473
> 2013-08-28 05:09:27,773 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network Ntwk[473|Guest|125] as a part of network shutdown
> 2013-08-28 05:09:27,774 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Lock is
> released for network id 473 as a part of network implement
> 2013-08-28 05:09:27,774 ERROR [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Failed
> to start instance VM[User|267a2467-9d94-4667-9624-60e139fd2d1d]
> com.cloud.utils.exception.CloudRuntimeException: Failed to add VPC router
> VM[DomainRouter|r-507-QA] to guest network Ntwk[473|Guest|125]
> at
> com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtualRouterElement.java:178)
> at
> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:2034)
> at
> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1939)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2120)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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-08-28 05:09:27,782 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-8:job-2160 = [ 58de3203-44b2-4384-aff3-b66a617425d3 ]) Cleani
[jira] [Commented] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753096#comment-13753096 ] frank zhang commented on CLOUDSTACK-4533: - did you change anything on the environment? I can not reproduce after logging in. The usage server is running well even if I delete the usage.log > permission issue in usage server and it failed to start after upgrade from > 3.0.4 to 4.2 > --- > > Key: CLOUDSTACK-4533 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging, Upgrade, Usage >Affects Versions: 4.2.1 > Environment: >Reporter: shweta agarwal >Priority: Blocker > Fix For: 4.2.1 > > Attachments: cloudstack-usage.err, cloudstack-usage.out > > > did an upgrade from 3.0.4 to 4.2 and then start usage server. > Usage server failed to start > giving following exception : > log4j:ERROR setFile(null,true) call failed. > java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log > (Permission denied) > at java.io.FileOutputStream.openAppend(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:207) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) > at > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) > at > org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179) > at > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773) > at > org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901) > at > org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69) > at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89) > at com.cloud.usage.UsageServer.init(UsageServer.java:52) > 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:616) > at > org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207) > log4j:ERROR setFile(null,true) call failed. > java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log > (Permission denied) > at java.io.FileOutputStream.openAppend(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:207) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) > at > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) > at > org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179) > at > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) > at > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176) > at > org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191) > at > org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523) > at > org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492) > at > org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755) > Attaching full logs. >
[jira] [Commented] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753090#comment-13753090 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 56ebf3b9b83a087b60d8de51f0276387a04c15a4 in branch refs/heads/4.2-forward from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=56ebf3b ] CLOUDSTACK-883. DOC. Fix license header in UI plugins section. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753088#comment-13753088 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit a4c10d00a4ab4b6081ee1ef15f2323cbf57c828c in branch refs/heads/master from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a4c10d0 ] CLOUDSTACK-883. DOC. Fix license header in UI plugins section. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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] [Updated] (CLOUDSTACK-4546) [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-4546: -- Attachment: management-server.log.gz > [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy > guest VM > -- > > Key: CLOUDSTACK-4546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 > 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: MS10.223.195.52build 554 > host ESXi 5.0 > Vcenter DC d1 c1host1 >Reporter: angeline shen >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.gz > > > 1. advance zone. After guest VM template downloaded, unable to deploy guest > VM: > 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] > (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found > 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing > lock for VMTemplateStoragePool 5 > 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 > = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the > key template_spool_ref5 and thread id 1874961927 > 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to > exception:Exception: javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to > contact resource. > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is > unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to > primary storage due to exception:Exception: > javax.xml.ws.soap.SOAPFaultException > Message: > Error returned by expat parser: not well-formed (invalid token) > while parsing serialized value of type string > at line 1, column 189 > while parsing call information for method CreateImportSpec > at line 1, column 110 > while parsing SOAP body > at line 1, column 102 > while parsing SOAP envelope > at line 1, column 38 > while parsing HTTP request for method createImportSpec > on object of type vim.OvfManager > at line 1, column 0 > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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(T
[jira] [Commented] (CLOUDSTACK-4541) MS:Template:Snapshot Templates created from Snapshot gets removed upon MS Restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753087#comment-13753087 ] Min Chen commented on CLOUDSTACK-4541: -- This is the same issue as https://issues.apache.org/jira/browse/CLOUDSTACK-4468, shweta has verified and closed that bug. > MS:Template:Snapshot Templates created from Snapshot gets removed upon MS > Restart > - > > Key: CLOUDSTACK-4541 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4541 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Snapshot, Template >Affects Versions: 4.2.1 > Environment: VMWare >Reporter: Parth Jagirdar >Priority: Critical > Fix For: 4.2.0, 4.2.1 > > Attachments: template.log > > > Create a template from a snapshot. > Deploy a VM using it to verify. > Restart MS.. observer that template is marked as "Ready No". And template is > no longer available under Create Instance wizard. > logs attached. > Template names are : master template clone and new master 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-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753084#comment-13753084 ] Jessica Tomechak commented on CLOUDSTACK-774: - Can't have time to convert the attached .doc to XML. Can we stick it in the wiki, or generate a PDF from it and post it as a standalone guide? > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang >Assignee: Jessica Tomechak > Fix For: 4.2.0 > > Attachments: CLOUDSTACK-774-baremetal-support.patch, > CLOUDSTACK-774-baremetal-support.patch.md5sum, > CLOUDSTACK-774-baremetal-support.patch.sig > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning > Release Planning: > Dev List Discussion: http://markmail.org/message/m6tg5nzfgqiwhzre > Functional Spec: https://cwiki.apache.org/CLOUDSTACK/baremetal-kickstart.html > Feature Branch: master > progress: 90% -- 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-4546) [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM
angeline shen created CLOUDSTACK-4546: - Summary: [Vmware] new mapping vmware datacenter cloudstack zone - Unable to deploy guest VM Key: CLOUDSTACK-4546 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4546 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: MS10.223.195.52build 554 host ESXi 5.0 Vcenter DC d1 c1host1 Reporter: angeline shen Priority: Blocker Fix For: 4.2.0 1. advance zone. After guest VM template downloaded, unable to deploy guest VM: 2013-08-28 17:02:09,697 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-9:null) Seq 2-390135955: No more commands found 2013-08-28 17:02:09,706 INFO [storage.volume.VolumeServiceImpl] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) releasing lock for VMTemplateStoragePool 5 2013-08-28 17:02:09,706 WARN [utils.db.Merovingian2] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Was unable to find lock for the key template_spool_ref5 and thread id 1874961927 2013-08-28 17:02:09,706 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to exception:Exception: javax.xml.ws.soap.SOAPFaultException Message: Error returned by expat parser: not well-formed (invalid token) while parsing serialized value of type string at line 1, column 189 while parsing call information for method CreateImportSpec at line 1, column 110 while parsing SOAP body at line 1, column 102 while parsing SOAP envelope at line 1, column 38 while parsing HTTP request for method createImportSpec on object of type vim.OvfManager at line 1, column 0 2013-08-28 17:02:09,706 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Unable to contact resource. com.cloud.exception.StorageUnavailableException: Resource [StoragePool:3] is unreachable: Unable to create Vol[7|vm=6|ROOT]:Unable to copy template to primary storage due to exception:Exception: javax.xml.ws.soap.SOAPFaultException Message: Error returned by expat parser: not well-formed (invalid token) while parsing serialized value of type string at line 1, column 189 while parsing call information for method CreateImportSpec at line 1, column 110 while parsing SOAP body at line 1, column 102 while parsing SOAP envelope at line 1, column 38 while parsing HTTP request for method createImportSpec on object of type vim.OvfManager at line 1, column 0 at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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-08-28 17:02:09,710 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Cleaning up resources for the vm VM[User|0f23e751-453f-4bfa-b1f3-f9cf9bc62ef7] in Starting state 2013-08-28 17:02:09,712 DEBUG [agent.transport.Request] (Job-Executor-16:job-16 = [ fadabfa8-3d60-4d6f-9016-4e430107faff ]) Seq 1-2118517001: Sendin
[jira] [Commented] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753078#comment-13753078 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit df11512e622a53bb9a0c8ee29c0758ef67edbb61 in branch refs/heads/master from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=df11512 ] CLOUDSTACK-883. DOC. Small fix to comment in UI plugins section. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753072#comment-13753072 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 4fe0fcf2631271ec0dc5686358bb624a6fd4f02a in branch refs/heads/4.2-forward from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4fe0fcf ] CLOUDSTACK-883. DOC. Small fix to comment in UI plugins section. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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] [Created] (CLOUDSTACK-4545) VMWare:Template:Cloning: Master templte used by linked clones should not be available for deletion
Parth Jagirdar created CLOUDSTACK-4545: -- Summary: VMWare:Template:Cloning: Master templte used by linked clones should not be available for deletion Key: CLOUDSTACK-4545 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4545 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template, VMware Affects Versions: 4.2.1 Environment: VMWare Reporter: Parth Jagirdar Priority: Critical Currently if we spawn Linked clone VM's; We can still delete the template used by clones from cloudstack. This master template is on primary storage and upon issuing delete it will be cleaned eventually (from secondary and primary. In this case We are likely to hit run-time exception and may affect all running VM's (Linked Clones) if template is removed. In Full clone scenario, we are less likely to encounter the exception and VM's may not be affected at all. In any case, We need a way such that when CM clones are actively using the template we should mark that Master template as not available for deletion. Same mechanism should be reflected on UI and templates used by VM's should display delete button as grayed out with appropriate message like VM's are actively using this 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] [Updated] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-883: Assignee: Sudha Ponnaganti (was: Jessica Tomechak) > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: 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] [Updated] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Tomechak updated CLOUDSTACK-883: Status: Ready To Review (was: In Progress) > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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-4528) [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753067#comment-13753067 ] ASF subversion and git services commented on CLOUDSTACK-4528: - Commit af175d8c65728dc3c7f29241e936decdec67e936 in branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=af175d8 ] CLOUDSTACK-4528 [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL Change: - Also add a check in migrateSystemVM API to check that source and destination host are in the same cluster > [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host > migration across cluster FAIL > -- > > Key: CLOUDSTACK-4528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4528 > 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: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Prachi Damle >Priority: Critical > Fix For: Future > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-4.png > > > 1. Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > 5. Virtual r-9-VMr-7-VM > r-7-VM on host 10.223.51.2 in cluster 1. Try to host migrate to host > 10.223.51.4 in cluster 2 FAIL: > 2013-08-27 14:19:18,815 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Migrating > VM[DomainRouter|r-7-VM] to > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(3)-Host(6)-Storage()] > 2013-08-27 14:19:18,819 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Source > and destination host are not in same cluster, unable to migrate to host: 6 > 2013-08-27 14:19:18,827 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd > com.cloud.utils.exception.CloudRuntimeException: Source and destination host > are not in same cluster, unable to migrate to host: 6 > at > com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1464) > at > com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3982) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd.execute(MigrateSystemVMCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.Thread
[jira] [Commented] (CLOUDSTACK-4528) [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753068#comment-13753068 ] ASF subversion and git services commented on CLOUDSTACK-4528: - Commit 92eb84c3e0785b5773259aad202a1cde2c51b385 in branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=92eb84c ] CLOUDSTACK-4528: [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL Changes: - listHosts within same cluster for migration of system and router VMs > [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host > migration across cluster FAIL > -- > > Key: CLOUDSTACK-4528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4528 > 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: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Prachi Damle >Priority: Critical > Fix For: Future > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-4.png > > > 1. Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > 5. Virtual r-9-VMr-7-VM > r-7-VM on host 10.223.51.2 in cluster 1. Try to host migrate to host > 10.223.51.4 in cluster 2 FAIL: > 2013-08-27 14:19:18,815 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Migrating > VM[DomainRouter|r-7-VM] to > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(3)-Host(6)-Storage()] > 2013-08-27 14:19:18,819 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Source > and destination host are not in same cluster, unable to migrate to host: 6 > 2013-08-27 14:19:18,827 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd > com.cloud.utils.exception.CloudRuntimeException: Source and destination host > are not in same cluster, unable to migrate to host: 6 > at > com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1464) > at > com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3982) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd.execute(MigrateSystemVMCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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(ThreadPoolExe
[jira] [Commented] (CLOUDSTACK-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753062#comment-13753062 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 75041b9c55e536eb0a0020f983ec750df4af8832 in branch refs/heads/master from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75041b9 ] CLOUDSTACK-883. DOC. How to integrate your 3rd-party plugin with the UI. Contains brief third-party plugin code tutorial. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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-883) Document 3rd party plugin feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753063#comment-13753063 ] ASF subversion and git services commented on CLOUDSTACK-883: Commit 5036e4f9f9b3b06a1268657c6c0fcc1e1ec5e83a in branch refs/heads/4.2-forward from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5036e4f ] CLOUDSTACK-883. DOC. How to integrate your 3rd-party plugin with the UI. Contains brief third-party plugin code tutorial. > Document 3rd party plugin feature > - > > Key: CLOUDSTACK-883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-883 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Jessica Tomechak > 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] [Assigned] (CLOUDSTACK-4524) [UI][Vmware] Listing of hosts for SSVM migration does not show host from other cluster. But listing of host for CPVM migration shows host from other cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-4524: Assignee: angeline shen Angeline, Please provide database dump. I'm unable to reproduce this bug in my environment without database dump. thank you. Jessica > [UI][Vmware] Listing of hosts for SSVM migration does not show host from > other cluster. But listing of host for CPVM migration shows host from other > cluster. > - > > Key: CLOUDSTACK-4524 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4524 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, UI >Affects Versions: 4.2.0 > Environment: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: angeline shen >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-6.png, Screenshot-CloudPlatform™ - Mozilla Firefox-7.png, > Screenshot-CloudPlatform™ - Mozilla Firefox-8.png > > > 1. > Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. H3 cancel maintenance mode. > CPVM v-11-VM able to go to running state. > Old SSVM s-10-VM remained in expunging and disconnected state > 5. SSVM s-14-VM on host 10.223.51.3 in cluster 1. > Try to migrate s-14-VM to host 10.223.51.4 in cluster 2. >But UI only shows option to migrate to host 10.223.51.3 in cluster 1. -- 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-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753041#comment-13753041 ] ASF subversion and git services commented on CLOUDSTACK-815: Commit f002b8e769a48962baccee233c84468d5c87d800 in branch refs/heads/master from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f002b8e ] CLOUDSTACK-815. DOC. Fix Regions documentation for reviewer comments. > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sangeetha Hariharan > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753038#comment-13753038 ] ASF subversion and git services commented on CLOUDSTACK-4089: - Commit 19341d66f45710ceae513a4013e3a03512000f21 in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=19341d6 ] CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > physical network > vmware_network_label: remove trailing comma if there is any. > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang > Fix For: Future > > Attachments: 2013-08-06-A.jpg, > addClusterCmd_wrongDuplicateParameterNames.jpg, dropPN.png, > edit-traffic-type-vmware.jpg > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- 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-815) Document AWS Style Regions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753039#comment-13753039 ] ASF subversion and git services commented on CLOUDSTACK-815: Commit 55583c0f97cecb2e4a44d5020e52209d609cb0cd in branch refs/heads/4.2-forward from [~jessica.tomec...@citrix.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=55583c0 ] CLOUDSTACK-815. DOC. Fix Regions documentation for reviewer comments. > Document AWS Style Regions > -- > > Key: CLOUDSTACK-815 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-815 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Sangeetha Hariharan > Fix For: 4.1.0, 4.2.0 > > > Document AWS Style Regions -- 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-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753035#comment-13753035 ] ASF subversion and git services commented on CLOUDSTACK-4089: - Commit cb12cf93544308cdac3ffd6062cc75e10cf16ab4 in branch refs/heads/4.2-forward from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cb12cf9 ] CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > physical network > vmware_network_label: remove trailing comma if there is any. > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang > Fix For: Future > > Attachments: 2013-08-06-A.jpg, > addClusterCmd_wrongDuplicateParameterNames.jpg, dropPN.png, > edit-traffic-type-vmware.jpg > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- 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-4089) Provide a drop down to specify VLAN,Switch type, Traffic label name while configuring Zone(VMWARE)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4089. -- Resolution: Fixed > Provide a drop down to specify VLAN,Switch type, Traffic label name while > configuring Zone(VMWARE) > -- > > Key: CLOUDSTACK-4089 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4089 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Jessica Wang > Fix For: Future > > Attachments: 2013-08-06-A.jpg, > addClusterCmd_wrongDuplicateParameterNames.jpg, dropPN.png, > edit-traffic-type-vmware.jpg > > > Observation: > Setup: VMWARE > 1. While configuring Zone, During Physical network creation , currently > there is a text field to specify VLAN Id for the traffic , Traffic label > name & Switch type (vmwaresvs,vmwaredvs,nexusdvs) > 2. It is text field and there is a possibility of missing some of the > parameters. > 3. While adding cluster we have an option to specify the traffic label name > and drop down to select the Switch type. > This is the request to provide a drop down to specify VLAN,Switch type, > Traffic label name while configuring Zone(VMWARE). This will avoid a lot of > confusion between Zone vs Cluster level configuration. > It also simplifies the configuration process. -- 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] [Comment Edited] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exceptio
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753033#comment-13753033
]
Animesh Chaturvedi edited comment on CLOUDSTACK-4540 at 8/28/13 11:38 PM:
--
Parallel deployment is turned off so marking for future
was (Author: animeshc):
Parallel deployment is turned off so asking for future
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception Message: Timed out in waiting SSH execution result"
> ---
>
> Key: CLOUDSTACK-4540
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4540
> 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: Build from 4.2-forward.
>Reporter: Sangeetha Hariharan
>Priority: Blocker
> Fix For: Future
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
> Deploy 30 Vms in parallel.
> 16 out of 30 vms deployed in parallel , failed due to "VmDataCommand failed
> due to Exception: java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Following exception seen in Management server logs:
> 2013-08-28 10:26:58,939 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-21:10.223.58.66) VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result
> java.lang.Exception: Timed out in waiting SSH execution result
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:166)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2470)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> 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-08-28 10:26:58,940 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-21:null) Seq 1-170983503: Response Received:
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request] (DirectAgent-21:null)
> Seq 1-170983503: Processing: { Ans: , MgmtId: 7083743249448, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.lang.Exception\nMessage: Timed out in waiting
> SSH execution result\n","wait":0}}] }
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Seq
> 1-170983503: Received: { Ans: , MgmtId: 7083743249448, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-08-28 10:26:58,979 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
>
[jira] [Commented] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exception Mes
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753033#comment-13753033
]
Animesh Chaturvedi commented on CLOUDSTACK-4540:
Parallel deployment is turned off
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception Message: Timed out in waiting SSH execution result"
> ---
>
> Key: CLOUDSTACK-4540
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4540
> 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: Build from 4.2-forward.
>Reporter: Sangeetha Hariharan
>Priority: Blocker
> Fix For: Future
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
> Deploy 30 Vms in parallel.
> 16 out of 30 vms deployed in parallel , failed due to "VmDataCommand failed
> due to Exception: java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Following exception seen in Management server logs:
> 2013-08-28 10:26:58,939 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-21:10.223.58.66) VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result
> java.lang.Exception: Timed out in waiting SSH execution result
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:166)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2470)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> 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-08-28 10:26:58,940 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-21:null) Seq 1-170983503: Response Received:
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request] (DirectAgent-21:null)
> Seq 1-170983503: Processing: { Ans: , MgmtId: 7083743249448, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.lang.Exception\nMessage: Timed out in waiting
> SSH execution result\n","wait":0}}] }
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Seq
> 1-170983503: Received: { Ans: , MgmtId: 7083743249448, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-08-28 10:26:58,979 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2076)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.jav
[jira] [Updated] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exception Messa
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-4540:
---
Fix Version/s: (was: 4.2.1)
Future
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception Message: Timed out in waiting SSH execution result"
> ---
>
> Key: CLOUDSTACK-4540
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4540
> 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: Build from 4.2-forward.
>Reporter: Sangeetha Hariharan
>Priority: Blocker
> Fix For: Future
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
> Deploy 30 Vms in parallel.
> 16 out of 30 vms deployed in parallel , failed due to "VmDataCommand failed
> due to Exception: java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Following exception seen in Management server logs:
> 2013-08-28 10:26:58,939 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-21:10.223.58.66) VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result
> java.lang.Exception: Timed out in waiting SSH execution result
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:166)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2470)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> 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-08-28 10:26:58,940 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-21:null) Seq 1-170983503: Response Received:
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request] (DirectAgent-21:null)
> Seq 1-170983503: Processing: { Ans: , MgmtId: 7083743249448, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.lang.Exception\nMessage: Timed out in waiting
> SSH execution result\n","wait":0}}] }
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Seq
> 1-170983503: Received: { Ans: , MgmtId: 7083743249448, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-08-28 10:26:58,979 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2076)
> at
> com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
> at
> com.cloud.network
[jira] [Comment Edited] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exceptio
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753033#comment-13753033
]
Animesh Chaturvedi edited comment on CLOUDSTACK-4540 at 8/28/13 11:37 PM:
--
Parallel deployment is turned off so asking for future
was (Author: animeshc):
Parallel deployment is turned off so arking for future
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception Message: Timed out in waiting SSH execution result"
> ---
>
> Key: CLOUDSTACK-4540
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4540
> 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: Build from 4.2-forward.
>Reporter: Sangeetha Hariharan
>Priority: Blocker
> Fix For: Future
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
> Deploy 30 Vms in parallel.
> 16 out of 30 vms deployed in parallel , failed due to "VmDataCommand failed
> due to Exception: java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Following exception seen in Management server logs:
> 2013-08-28 10:26:58,939 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-21:10.223.58.66) VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result
> java.lang.Exception: Timed out in waiting SSH execution result
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:166)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2470)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> 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-08-28 10:26:58,940 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-21:null) Seq 1-170983503: Response Received:
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request] (DirectAgent-21:null)
> Seq 1-170983503: Processing: { Ans: , MgmtId: 7083743249448, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.lang.Exception\nMessage: Timed out in waiting
> SSH execution result\n","wait":0}}] }
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Seq
> 1-170983503: Received: { Ans: , MgmtId: 7083743249448, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-08-28 10:26:58,979 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
>
[jira] [Comment Edited] (CLOUDSTACK-4540) Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails to get deployed due to "VmDataCommand failed due to Exception: java.lang.Exceptio
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753033#comment-13753033
]
Animesh Chaturvedi edited comment on CLOUDSTACK-4540 at 8/28/13 11:37 PM:
--
Parallel deployment is turned off so arking for future
was (Author: animeshc):
Parallel deployment is turned off
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception Message: Timed out in waiting SSH execution result"
> ---
>
> Key: CLOUDSTACK-4540
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4540
> 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: Build from 4.2-forward.
>Reporter: Sangeetha Hariharan
>Priority: Blocker
> Fix For: Future
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 Vms fails
> to get deployed due to "VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Set up - Advanced zone with 1 Vmware 5.0.0 Esxi host.
> Deploy 30 Vms in parallel.
> 16 out of 30 vms deployed in parallel , failed due to "VmDataCommand failed
> due to Exception: java.lang.Exception
> Message: Timed out in waiting SSH execution result"
> Following exception seen in Management server logs:
> 2013-08-28 10:26:58,939 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-21:10.223.58.66) VmDataCommand failed due to Exception:
> java.lang.Exception
> Message: Timed out in waiting SSH execution result
> java.lang.Exception: Timed out in waiting SSH execution result
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:166)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2470)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> 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-08-28 10:26:58,940 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-21:null) Seq 1-170983503: Response Received:
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request] (DirectAgent-21:null)
> Seq 1-170983503: Processing: { Ans: , MgmtId: 7083743249448, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.lang.Exception\nMessage: Timed out in waiting
> SSH execution result\n","wait":0}}] }
> 2013-08-28 10:26:58,941 DEBUG [agent.transport.Request]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Seq
> 1-170983503: Received: { Ans: , MgmtId: 7083743249448, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-08-28 10:26:58,979 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-29:job-398 = [ b3a34f25-37b2-4f33-b183-c0ea348d7af9 ]) Unable
> to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
> at
> com.cloud
[jira] [Closed] (CLOUDSTACK-4544) [Build CloudPlatform-4.2-553-rhel6.3.tar.gz] SSVM fail to come up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen closed CLOUDSTACK-4544. - Resolution: Fixed use build http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/4.2/CloudPlatform-4.2-554-rhel6.3.tar.gz > [Build CloudPlatform-4.2-553-rhel6.3.tar.gz] SSVM fail to come up > - > > Key: CLOUDSTACK-4544 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4544 > 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: MS Build CloudPlatform-4.2-553-rhel6.3.tar.gz > hostESXi 5.0 >Reporter: angeline shen >Assignee: frank zhang >Priority: Blocker > Fix For: 4.2.0 > > > 1. Create advance zone. SSVM fail to come up: > 2013-08-28 14:44:32,422 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-2:null) Seq 1-836894728: Executing request > 2013-08-28 14:44:32,462 INFO [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Template routing-8 is not setup yet, setup > template from secondary storage with uuid name: > cc9749fbd5443c07a2ed0dadf7cca2cb > 2013-08-28 14:44:32,498 INFO [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Executing copyTemplateFromSecondaryToPrimary. > secondaryStorage: nfs://10.223.110.232/export/home/angie/secondary/vm63, > templatePathAtSecondaryStorage: template/tmpl/1/8/, templateName: routing-8 > 2013-08-28 14:44:32,500 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Executing: sudo mount -t nfs > 10.223.110.232:/export/home/angie/secondary/vm63 > /var/cloudstack/mnt/VM/7343890761426.6bb8e611 > 2013-08-28 14:44:33,150 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers to update status. > 2013-08-28 14:44:33,152 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-08-28 14:44:33,158 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Execution is successful. > 2013-08-28 14:44:33,158 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Executing: sudo chmod 777 * -R > /var/cloudstack/mnt/VM/7343890761426.6bb8e611 > 2013-08-28 14:44:33,208 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers to update status. > 2013-08-28 14:44:33,212 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-08-28 14:44:33,307 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Exit value is 1 > 2013-08-28 14:44:33,307 DEBUG [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) chmod: cannot access `*': No such file or > directory > 2013-08-28 14:44:33,307 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Unable to set permissions for > /var/cloudstack/mnt/VM/7343890761426.6bb8e611 due to chmod: cannot access > `*': No such file or directory > 2013-08-28 14:44:33,308 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.223.51.3) Unable to create mount point for > nfs://10.223.110.232/export/home/angie/secondary/vm63 > 2013-08-28 14:44:33,308 INFO [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Secondary storage mount point: /mnt/sec > 2013-08-28 14:44:33,311 INFO [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Executing command: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8//routing-8.ova > 2013-08-28 14:44:33,311 DEBUG [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Executing: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8//routing-8.ova > 2013-08-28 14:44:33,330 WARN [storage.resource.VmwareStorageProcessor] > (DirectAgent-2:10.223.51.3) Exception: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8//routing-8.ova > java.io.IOException: Cannot run program "tar" (in directory > "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or > directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147) > at > com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222) > at > com.cloud.storage.resource.Sto
[jira] [Resolved] (CLOUDSTACK-4528) [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle resolved CLOUDSTACK-4528. -- Resolution: Fixed > [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host > migration across cluster FAIL > -- > > Key: CLOUDSTACK-4528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4528 > 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: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Prachi Damle >Priority: Critical > Fix For: Future > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-4.png > > > 1. Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > 5. Virtual r-9-VMr-7-VM > r-7-VM on host 10.223.51.2 in cluster 1. Try to host migrate to host > 10.223.51.4 in cluster 2 FAIL: > 2013-08-27 14:19:18,815 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Migrating > VM[DomainRouter|r-7-VM] to > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(3)-Host(6)-Storage()] > 2013-08-27 14:19:18,819 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Source > and destination host are not in same cluster, unable to migrate to host: 6 > 2013-08-27 14:19:18,827 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd > com.cloud.utils.exception.CloudRuntimeException: Source and destination host > are not in same cluster, unable to migrate to host: 6 > at > com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1464) > at > com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3982) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd.execute(MigrateSystemVMCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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-08-27 14:19:18,829 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Complete > async job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Source and destina
[jira] [Commented] (CLOUDSTACK-4528) [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752982#comment-13752982 ] ASF subversion and git services commented on CLOUDSTACK-4528: - Commit 52f4683099e03e16916dfdf741f2d5544491aaad in branch refs/heads/4.2-forward from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=52f4683 ] CLOUDSTACK-4528: [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL Changes: - listHosts within same cluster for migration of system and router VMs > [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host > migration across cluster FAIL > -- > > Key: CLOUDSTACK-4528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4528 > 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: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Prachi Damle >Priority: Critical > Fix For: Future > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-4.png > > > 1. Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > 5. Virtual r-9-VMr-7-VM > r-7-VM on host 10.223.51.2 in cluster 1. Try to host migrate to host > 10.223.51.4 in cluster 2 FAIL: > 2013-08-27 14:19:18,815 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Migrating > VM[DomainRouter|r-7-VM] to > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(3)-Host(6)-Storage()] > 2013-08-27 14:19:18,819 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Source > and destination host are not in same cluster, unable to migrate to host: 6 > 2013-08-27 14:19:18,827 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd > com.cloud.utils.exception.CloudRuntimeException: Source and destination host > are not in same cluster, unable to migrate to host: 6 > at > com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1464) > at > com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3982) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd.execute(MigrateSystemVMCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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(ThreadPo
[jira] [Commented] (CLOUDSTACK-4528) [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752981#comment-13752981 ] ASF subversion and git services commented on CLOUDSTACK-4528: - Commit b24e9a6dd5281b2163ce088e6f5b1fa730c33f7d in branch refs/heads/4.2-forward from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b24e9a6 ] CLOUDSTACK-4528 [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host migration across cluster FAIL Change: - Also add a check in migrateSystemVM API to check that source and destination host are in the same cluster > [Vmware] new mapping vmware datacenter cloudstack zone - Virtual Router host > migration across cluster FAIL > -- > > Key: CLOUDSTACK-4528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4528 > 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: MS 10.223.195.52 build 479 > host ESXi 5.0 >Reporter: angeline shen >Assignee: Prachi Damle >Priority: Critical > Fix For: Future > > Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - > Mozilla Firefox-2.png, Screenshot-CloudPlatform™ - Mozilla Firefox-4.png > > > 1. Vcenter CPP 4.2. > VC1 - DC1 - C1 - H1 zone1 - C1 - H1 10.223.51.2 > H2 H2 10.223.51.3 > PS2 cluster > primary storage > > C2 - H3 C2 - H3 10.223.51.4 > PS3 cluster > primary storage > PS1 zone > primary storage > PSZ4 zone > primary storage > 2. H3 10.223.51.4 has SSVM CPVM and VMs i-2-8 i-2-6 > VRs and other guest VMs were on Hosts H1 and H3 > 3. Put H3 in maintenance mode. > Result: > VMs i-2-6-VM and i-2-8-VM went into STOP state. Try to start both VMs. These > remain in > 'Starting' state . > New SSVM s-14-VM created.. Old SSVM s-10-VM remained in expunging and > disconnected state > CPVM v-11-VM remain in STOP and disconnected state. Cannot be started > 4. Host H3 cancel maintenance mode. > Old SSVM s-10-VM remained in expunging and disconnected state > CPVM v-11-VM go to running state > Old SSVM s-10-VM remained in expunging and disconnected state > VMs i-2-6-VM and i-2-8-VM were in STOP state. > Unable to restart both guest VMs - deployment failed > 5. Virtual r-9-VMr-7-VM > r-7-VM on host 10.223.51.2 in cluster 1. Try to host migrate to host > 10.223.51.4 in cluster 2 FAIL: > 2013-08-27 14:19:18,815 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Migrating > VM[DomainRouter|r-7-VM] to > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : Dest[Zone(1)-Pod(1)-Cluster(3)-Host(6)-Storage()] > 2013-08-27 14:19:18,819 INFO [cloud.vm.VirtualMachineManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) Source > and destination host are not in same cluster, unable to migrate to host: 6 > 2013-08-27 14:19:18,827 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-120 = [ f839a0d3-1b6a-431e-8b0f-f18d5590a972 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd > com.cloud.utils.exception.CloudRuntimeException: Source and destination host > are not in same cluster, unable to migrate to host: 6 > at > com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1464) > at > com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3982) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd.execute(MigrateSystemVMCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > 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.T
[jira] [Resolved] (CLOUDSTACK-4405) (Upgrade) Migrate failed between existing hosts and new hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] edison su resolved CLOUDSTACK-4405. --- Resolution: Fixed > (Upgrade) Migrate failed between existing hosts and new hosts > - > > Key: CLOUDSTACK-4405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 > Environment: CS 4.1 >Reporter: Wei Zhou >Assignee: edison su >Priority: Blocker > Fix For: 4.1.1, 4.2.0, 4.2.1 > > > There are two hosts (cs-kvm001, cs-kvm002) in old 2.2.14 environment . > After upgrade from 2.2.14 to 4.1, I added two new hosts (cs-kvm003, > cs-kvm004). > The migration between cs-kvm001 and cs-kvm002, or cs-kvm003 and cs-kvm004 > succeed. > However, the migration from cs-kvm001/002 to the new hosts (cs-kvm003, > cs-kvm004) failed. > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) nic=[Nic:Guest-10.11.110.231-vlan://110] > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) creating a vlan dev and bridge for guest > traffic per traffic label cloudbr0 > 2013-08-19 16:57:31,051 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Executing: /bin/bash -c brctl show | grep > cloudVirBr110 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Exit value is 1 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) > 2013-08-19 16:57:31,063 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 110 -p > em1 -b brem1-110 -o add > 2013-08-19 16:57:31,121 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Execution is successful. > 2013-08-19 16:57:31,122 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Set name-type for VLAN subsystem. Should be > visible in /proc/net/vlan/config > This is because the bridge name on old hosts are cloudVirBr110, and brem1-110 > on new hosts. -- 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-4405) (Upgrade) Migrate failed between existing hosts and new hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752975#comment-13752975 ] ASF subversion and git services commented on CLOUDSTACK-4405: - Commit 0ef6084d2c838a78eda29d258b1af98df96451b3 in branch refs/heads/4.2-forward from [~edison] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0ef6084 ] CLOUDSTACK-4405: add a tool: cloudstack-agent-upgrade to upgrade bridge name on kvm host > (Upgrade) Migrate failed between existing hosts and new hosts > - > > Key: CLOUDSTACK-4405 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4405 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 > Environment: CS 4.1 >Reporter: Wei Zhou >Assignee: edison su >Priority: Blocker > Fix For: 4.1.1, 4.2.0, 4.2.1 > > > There are two hosts (cs-kvm001, cs-kvm002) in old 2.2.14 environment . > After upgrade from 2.2.14 to 4.1, I added two new hosts (cs-kvm003, > cs-kvm004). > The migration between cs-kvm001 and cs-kvm002, or cs-kvm003 and cs-kvm004 > succeed. > However, the migration from cs-kvm001/002 to the new hosts (cs-kvm003, > cs-kvm004) failed. > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) nic=[Nic:Guest-10.11.110.231-vlan://110] > 2013-08-19 16:57:31,051 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) creating a vlan dev and bridge for guest > traffic per traffic label cloudbr0 > 2013-08-19 16:57:31,051 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Executing: /bin/bash -c brctl show | grep > cloudVirBr110 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) Exit value is 1 > 2013-08-19 16:57:31,063 DEBUG [utils.script.Script] > (agentRequest-Handler-1:null) > 2013-08-19 16:57:31,063 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 110 -p > em1 -b brem1-110 -o add > 2013-08-19 16:57:31,121 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Execution is successful. > 2013-08-19 16:57:31,122 DEBUG [kvm.resource.BridgeVifDriver] > (agentRequest-Handler-1:null) Set name-type for VLAN subsystem. Should be > visible in /proc/net/vlan/config > This is because the bridge name on old hosts are cloudVirBr110, and brem1-110 > on new hosts. -- 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-2289) Doc- Granular Global Param
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2289: - Assignee: prashant kumar mishra (was: Sudha Ponnaganti) > Doc- Granular Global Param > -- > > Key: CLOUDSTACK-2289 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2289 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: prashant kumar mishra > 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] [Updated] (CLOUDSTACK-2407) Document zone wide primary storage support for VMware deployments
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2407: - Assignee: Srikanteswararao Talluri (was: Sudha Ponnaganti) > Document zone wide primary storage support for VMware deployments > - > > Key: CLOUDSTACK-2407 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2407 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Srikanteswararao Talluri > 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] [Updated] (CLOUDSTACK-864) Document Zone-wide primary storage target
[ https://issues.apache.org/jira/browse/CLOUDSTACK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-864: Assignee: Srikanteswararao Talluri (was: Sudha Ponnaganti) > Document Zone-wide primary storage target > - > > Key: CLOUDSTACK-864 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-864 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Srikanteswararao Talluri > Fix For: 4.2.0 > > > Document Zone-wide primary storage target -- 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-900) Document enable storage xenmotion support in XenServer 6.1 feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-900: Assignee: Srikanteswararao Talluri (was: Sudha Ponnaganti) > Document enable storage xenmotion support in XenServer 6.1 feature > -- > > Key: CLOUDSTACK-900 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-900 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers >Assignee: Srikanteswararao Talluri > 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
