[jira] [Created] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled
prashant kumar mishra created CLOUDSTACK-2939: - Summary: CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled Key: CLOUDSTACK-2939 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: VMware ESXI-5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Attachment: screenshot-1.jpg CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled -- Key: CLOUDSTACK-2939 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: VMware ESXI-5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Attachments: screenshot-1.jpg Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2937) Scheduled snapshot events should be shown to users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680972#comment-13680972 ] ASF subversion and git services commented on CLOUDSTACK-2937: - Commit d21e0647244db9e76b11038e7b8c55e1aca3b6aa in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d21e064 ] CLOUDSTACK-2937 Scheduled snapshot events should be shown to users Scheduled snapshot events should be shown to users -- Key: CLOUDSTACK-2937 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2937 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Scheduled snapshot events are generated from root account rather than the initiator accounts. Hence these initiated users are missing all events related to their snapshots. IMPACT == Users who have scheduled their snapshots are missing all the snapshot events related to them as they are generated from root/system account. DETAILED DESCRIPTION == Recurring snapshots are intiaited by a user, but they are created by Root user on CS. Whenever a snapshot is created, alongwith, a notification/event is also created. Since Root user creates the snapshot, the event is associated with Root user and not with the user who initiated it. -- 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-2937) Scheduled snapshot events should be shown to users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-2937. - Resolution: Fixed Scheduled snapshot events should be shown to users -- Key: CLOUDSTACK-2937 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2937 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Scheduled snapshot events are generated from root account rather than the initiator accounts. Hence these initiated users are missing all events related to their snapshots. IMPACT == Users who have scheduled their snapshots are missing all the snapshot events related to them as they are generated from root/system account. DETAILED DESCRIPTION == Recurring snapshots are intiaited by a user, but they are created by Root user on CS. Whenever a snapshot is created, alongwith, a notification/event is also created. Since Root user creates the snapshot, the event is associated with Root user and not with the user who initiated it. -- 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-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Attachment: logs.rar CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled -- Key: CLOUDSTACK-2939 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: VMware ESXI-5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Attachments: logs.rar, screenshot-1.jpg Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2751) Automation: Automate midonet plugin functionality
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Cahill resolved CLOUDSTACK-2751. - Resolution: Won't Fix Closing as Won't Fix after discussing with Sudha. This ticket doesn't make sense for the MidoNet plugin, as the MidoNet agent code etc which would be required for a full automated test are not publicly available. Automation: Automate midonet plugin functionality - Key: CLOUDSTACK-2751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2751 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2749) QA: Write test plan and execute Testplan for midonet network integration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680978#comment-13680978 ] Dave Cahill commented on CLOUDSTACK-2749: - Test plan is here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/MidoNet+Test+Plan QA: Write test plan and execute Testplan for midonet network integration Key: CLOUDSTACK-2749 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2749 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Dave Cahill 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
Nitin Mehta created CLOUDSTACK-2940: --- Summary: Domain on SSVM is not being updated for download urls that come for CS. Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680983#comment-13680983 ] ASF subversion and git services commented on CLOUDSTACK-2940: - Commit e73aafc09ae3dc21dcbf8851f29c4b1977489fe6 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e73aafc ] CLOUDSTACK-2940 Allowing Replacement of realhostip.com with a customized domain for SSVM. Though the config variable was there we were always hardcoding to realhostip.com Reviewed-by: Abhi Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680981#comment-13680981 ] Nitin Mehta commented on CLOUDSTACK-2940: - The core of the issue is that the realhostip is hard coded for download urls and was not updated while fixing the bug. Steps to followed to verify the fix: 1. Install the build with out fix 2. Change the global setting secstorage.ssl.cert.domain to a custom domain name say, cloud.tsk 3. Try to download a template, this still provides the download URL with realhostip.com domain. 4. Now, upgrade to the build with fix. 5. Try to download a template, this provides the URL with changed domain name cloud.tsk. Following scenarios are tested: 1. Copy ISO template from one zone to another. 2. Download ISO, template and volume. Check whether the download URL is with changed domain name Above mentioned scenarios are passing. However to check whether the URL is actually working or not, we need to update SSL for the new domain cloud.tsk in this case. This is still in progress. Excerpt from the certificate error, while accessing the download URL. == 10-147-53-66.cloud.tsk uses an invalid security certificate. The certificate is only valid for the following names: *.realhostip.com , realhostip.com (Error code: ssl_error_bad_cert_domain) == Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2609) [MultipleIPsPerNic][SharedNetworks] nic_secondary_ips account/domainid is different when compared with primary ups
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-2609. --- Resolution: Fixed [MultipleIPsPerNic][SharedNetworks] nic_secondary_ips account/domainid is different when compared with primary ups -- Key: CLOUDSTACK-2609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2609 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636 Reporter: venkata swamybabu budumuru Assignee: Jayapal Reddy Fix For: 4.2.0 Attachments: logs.tgz Steps to reproduce : 1. Have latest CloudStack with advanced zone having KVM cluster with 1 host 2. Have at least one non-ROOT domain user 3. Create at least one share network with scope set domain of the above user 4. deploy a VM connected to the above shared networks 5. acquire at least one secondary ips for the above NICs Observations : (i) verify in the db cloud.nic_secondary_ips for account and domain id info. here is the snapshot of the db mysql select * from nic_secondary_ips; ++--+--+---+---+-++-++---+ | id | uuid | vmId | nicId | ip4_address | ip6_address | network_id | created | account_id | domain_id | ++--+--+---+---+-++-++---+ | 4 | 8402dfa2-94b2-4001-8c2c-b52d5c76bbad | 27 |69 | 10.147.44.235 | NULL|217 | 2013-05-21 19:49:40 | 1 | 1 | | 5 | 43954e3e-c5bf-4833-983c-9aec27a27e14 | 27 |70 | 10.147.54.235 | NULL|218 | 2013-05-21 19:54:24 | 1 | 1 | ++--+--+---+---+-++-++---+ (ii) Here is the snapshot of user_ip_address that contains the primary ip address info mysql select * from user_ip_address where id=42\G *** 1. row *** id: 42 uuid: a744755a-f5cd-4959-b338-1c36eaa56c32 account_id: 4 domain_id: 2 public_ip_address: 10.147.54.231 data_center_id: 3 source_nat: 0 allocated: 2013-05-21 17:49:41 vlan_db_id: 5 one_to_one_nat: 0 vm_id: NULL state: Allocated mac_address: 32 source_network_id: 218 network_id: NULL physical_network_id: 202 is_system: 0 vpc_id: NULL dnat_vmip: NULL 1 row in set (0.00 sec) (iii) In case of user_ip_address, it contains the account and domain id of the user who deployed the vm but, in case of secondary IPs, it contains the account and domain id as 1. Attaching all the required logs along with db dump to the bug. -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-2940. - Resolution: Fixed Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Description: Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm My observation -- 1-CPU limit is set to unlimited when i do scaleup from a SO (cpu cap enable) to a SO (cpu cap enable) . was: Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled -- Key: CLOUDSTACK-2939 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, VMware Affects Versions: 4.2.0 Environment: VMware ESXI-5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Attachments: logs.rar, screenshot-1.jpg Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm My observation -- 1-CPU limit is set to unlimited when i do scaleup from a SO (cpu cap enable) to a SO (cpu cap enable) . -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680993#comment-13680993 ] Wei Zhou commented on CLOUDSTACK-2940: -- Nitin, I have posted a patch for similar issue on 4.0.* which has not been submitted. FYI, please have a look at : https://reviews.apache.org/r/9696/ Maybe we need more changes. -Wei Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati
prashant kumar mishra created CLOUDSTACK-2941: - Summary: system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration) Key: CLOUDSTACK-2941 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2941 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: VMware 5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 steps to reproduce 1-Create a system offering for ssvm( memory:512MB,CPU:1000GHz) 2-scaleup ssvm Expected -- vm should get scaled up Actual --- VM scale up failed Snippet of log -- 2013-06-12 08:05:11,044 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-5:job-118) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration. at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:3250) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1227) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1106) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- 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-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2941: -- Priority: Critical (was: Major) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration) Key: CLOUDSTACK-2941 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2941 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: VMware 5.1 Reporter: prashant kumar mishra Priority: Critical Fix For: 4.2.0 Attachments: DB_and_logs.rar steps to reproduce 1-Create a system offering for ssvm( memory:512MB,CPU:1000GHz) 2-scaleup ssvm Expected -- vm should get scaled up Actual --- VM scale up failed Snippet of log -- 2013-06-12 08:05:11,044 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-5:job-118) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration. at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:3250) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1227) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1106) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- 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-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2941: -- Attachment: DB_and_logs.rar system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration) Key: CLOUDSTACK-2941 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2941 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: VMware 5.1 Reporter: prashant kumar mishra Fix For: 4.2.0 Attachments: DB_and_logs.rar steps to reproduce 1-Create a system offering for ssvm( memory:512MB,CPU:1000GHz) 2-scaleup ssvm Expected -- vm should get scaled up Actual --- VM scale up failed Snippet of log -- 2013-06-12 08:05:11,044 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-5:job-118) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration. at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:3250) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1227) at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1106) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- 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-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-2347: Fix Version/s: 4.2.0 Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681009#comment-13681009 ] Harikrishna Patnala commented on CLOUDSTACK-2347: - in RB https://reviews.apache.org/r/11820/ Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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-2942) [VPC][VMware]Unexpected exception while creating the private gateway .
manasaveloori created CLOUDSTACK-2942: - Summary: [VPC][VMware]Unexpected exception while creating the private gateway . Key: CLOUDSTACK-2942 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2942 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: VMware5.1 Reporter: manasaveloori Priority: Critical Fix For: 4.2.0 Steps: 1. Have a CS with advanced zone and VMware host. 2. Create a VPC. 3. Add a private gateway . Observation: Observed “ Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router” The same is observed while deleting the private gateway and the gateway is not getting deleted. following is the snippet from the management server log: 2013-06-12 17:39:11,253 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3743) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.applyNetworkACLs(VpcVirtualNetworkApplianceManagerImpl.java:717) at com.cloud.network.element.VpcVirtualRouterElement.applyACLItemsToPrivateGw(VpcVirtualRouterElement.java:463) at com.cloud.network.vpc.NetworkACLManagerImpl.applyACLItemsToPrivateGw(NetworkACLManagerImpl.java:325) at com.cloud.network.vpc.NetworkACLManagerImpl.revokeACLItemsForPrivateGw(NetworkACLManagerImpl.java:284) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.destroyPrivateGateway(VpcVirtualNetworkApplianceManagerImpl.java:1053) at com.cloud.network.element.VpcVirtualRouterElement.deletePrivateGateway(VpcVirtualRouterElement.java:378) at com.cloud.network.vpc.VpcManagerImpl.deleteVpcPrivateGateway(VpcManagerImpl.java:1475) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.vpc.VpcManagerImpl.applyVpcPrivateGateway(VpcManagerImpl.java:1436) at org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd.execute(CreatePrivateGatewayCmd.java:158) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-12 17:39:11,256 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Complete async job-31, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router 2013-06-12 17:39:11,286 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-32:job-31) Sync queue (1) is currently empty 2013-06-12 17:39:12,095 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResultjobId=e55475db-71fa-49f1-ad72-23e1b890cfe4response=jsonsessionkey=zS6DxXVJCRyZ3MzvBTZl5fjDY54%3D_=1371019500910 Attaching the management server log for reference. -- 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-2942) [VPC][VMware]Unexpected exception while creating the private gateway .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-2942: -- Attachment: management-server.log [VPC][VMware]Unexpected exception while creating the private gateway . -- Key: CLOUDSTACK-2942 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2942 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: VMware5.1 Reporter: manasaveloori Priority: Critical Fix For: 4.2.0 Attachments: management-server.log Steps: 1.Have a CS with advanced zone and VMware host. 2.Create a VPC. 3.Add a private gateway . Observation: Observed “ Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router” The same is observed while deleting the private gateway and the gateway is not getting deleted. following is the snippet from the management server log: 2013-06-12 17:39:11,253 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3743) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.applyNetworkACLs(VpcVirtualNetworkApplianceManagerImpl.java:717) at com.cloud.network.element.VpcVirtualRouterElement.applyACLItemsToPrivateGw(VpcVirtualRouterElement.java:463) at com.cloud.network.vpc.NetworkACLManagerImpl.applyACLItemsToPrivateGw(NetworkACLManagerImpl.java:325) at com.cloud.network.vpc.NetworkACLManagerImpl.revokeACLItemsForPrivateGw(NetworkACLManagerImpl.java:284) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.destroyPrivateGateway(VpcVirtualNetworkApplianceManagerImpl.java:1053) at com.cloud.network.element.VpcVirtualRouterElement.deletePrivateGateway(VpcVirtualRouterElement.java:378) at com.cloud.network.vpc.VpcManagerImpl.deleteVpcPrivateGateway(VpcManagerImpl.java:1475) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.vpc.VpcManagerImpl.applyVpcPrivateGateway(VpcManagerImpl.java:1436) at org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd.execute(CreatePrivateGatewayCmd.java:158) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-12 17:39:11,256 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Complete async job-31, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router 2013-06-12 17:39:11,286 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-32:job-31) Sync queue (1) is currently empty 2013-06-12 17:39:12,095 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResultjobId=e55475db-71fa-49f1-ad72-23e1b890cfe4response=jsonsessionkey=zS6DxXVJCRyZ3MzvBTZl5fjDY54%3D_=1371019500910 Attaching the management server log for reference. -- 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-2944) [Multiple IPs PerNic] [UI] Failed to addIpToNic using a custom guest ip address
venkata swamybabu budumuru created CLOUDSTACK-2944:
--
Summary: [Multiple IPs PerNic] [UI] Failed to addIpToNic using a
custom guest ip address
Key: CLOUDSTACK-2944
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2944
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: commit # 673b293d75419a4b76379092db2b204cdc6160a4
Reporter: venkata swamybabu budumuru
Assignee: Brian Federle
Priority: Minor
Fix For: 4.2.0
Steps to reproduce:
1. Have latest CS setup with at least one advanced zone.
2. deploy at least one VM
3. Go to Instances - VM - NICs - View Secondary IPs - Acquire New Secondary
IP wizard
4. pass a valid guest IP in the guest CIDR range
Observations :
(i) It failed acquire the IP passed in step (4). instead it got a random ip
from the guest CIDR assigned
(ii) API that was fired sent an invalid parameter for ipaddress.
Here is the API snippet :
_ 1371021942248
command addIpToNic
ipaddr 10.0.1.2
nicId 8663e098-7473-4005-afcc-0856c0d9a607
responsejson
sessionkey X4s9nS+qXdk0LHOZc/DAkM3iuOY=
(iii) It should send ipaddress as parameter instead of ipaddr.
Here is the snippet from mgmt server log
2013-06-12 08:54:31,618 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
===START=== 10.252.192.8 -- GET
command=addIpToNicresponse=jsonsessionkey=X4s9nS%2BqXdk0LHOZc%2FDAkM3iuOY%3DnicId=8663e098-7473-4005-afcc-0856c0d9a607ipaddr=10.0.1.2_=1371021942248
2013-06-12 08:54:31,657 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-19:null) submit async job-108, details: AsyncJobVO {id:108,
userId: 2, accountId: 2, sessionKey: null, instanceType: IpAddress, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.vm.AddIpToVmNicCmd,
cmdOriginator: null, cmdInfo:
{response:json,sessionkey:X4s9nS+qXdk0LHOZc/DAkM3iuOY\u003d,ipaddr:10.0.1.2,ctxUserId:2,httpmethod:GET,_:1371021942248,ctxAccountId:2,ctxStartEventId:401,nicId:8663e098-7473-4005-afcc-0856c0d9a607},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7280707764394,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 08:54:31,660 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
===END=== 10.252.192.8 -- GET
command=addIpToNicresponse=jsonsessionkey=X4s9nS%2BqXdk0LHOZc%2FDAkM3iuOY%3DnicId=8663e098-7473-4005-afcc-0856c0d9a607ipaddr=10.0.1.2_=1371021942248
2013-06-12 08:54:31,663 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-86:job-108) Executing
org.apache.cloudstack.api.command.user.vm.AddIpToVmNicCmd for job-108
2013-06-12 08:54:31,675 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-86:job-108) Sync job-108 execution on object network.213
2013-06-12 08:54:31,701 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-86:job-108) job
org.apache.cloudstack.api.command.user.vm.AddIpToVmNicCmd for job-108 was
queued, processing the queue.
2013-06-12 08:54:31,710 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-86:job-108) Executing sync queue item: SyncQueueItemVO {id:13,
queueId: 2, contentType: AsyncJob, contentId: 108, lastProcessMsid:
7280707764394, lastprocessNumber: 13, lastProcessTime: Wed Jun 12 08:54:31 EDT
2013, created: Wed Jun 12 08:54:31 EDT 2013}
2013-06-12 08:54:31,712 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-86:job-108) Schedule queued job-108
2013-06-12 08:54:31,721 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-86:job-108) There is a pending process in sync queue(id: 2)
2013-06-12 08:54:31,723 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-87:job-108) Executing
org.apache.cloudstack.api.command.user.vm.AddIpToVmNicCmd for job-108
2013-06-12 08:54:31,754 DEBUG [cloud.network.NetworkServiceImpl]
(Job-Executor-87:job-108) Calling the ip allocation ...
2013-06-12 08:54:31,762 DEBUG [cloud.network.NetworkServiceImpl]
(Job-Executor-87:job-108) Setting nic_secondary_ip table ...
2013-06-12 08:54:31,776 INFO [user.vm.AddIpToVmNicCmd]
(Job-Executor-87:job-108) Associated ip address to NIC : 10.0.1.211
2013-06-12 08:54:31,780 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-87:job-108) Complete async job-108, jobStatus: 1, resultCode: 0,
result: org.apache.cloudstack.api.response.NicSecondaryIpResponse@77715b45
2013-06-12 08:54:31,798 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-87:job-108) Sync queue (2) is currently empty
2013-06-12 08:54:31,799 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-87:job-108) Done executing
org.apache.cloudstack.api.command.user.vm.AddIpToVmNicCmd for job-108
2013-06-12 08:54:32,414 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-463:null)
[jira] [Created] (CLOUDSTACK-2943) [ZWPS][VMWARE]: NPE while creating volume from snapshot
Srikanteswararao Talluri created CLOUDSTACK-2943:
Summary: [ZWPS][VMWARE]: NPE while creating volume from snapshot
Key: CLOUDSTACK-2943
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2943
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Snapshot
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.2.0
1. create a snapshot created from a disk on zone scoped primary storage
2. create a volume from the snapshot created in step1.
===START=== 10.252.192.7 -- GET
command=createVolumeresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3Dsnapshotid=2112f1f0-9fc0-42f5-bde9-900dffeab7dfname=zwpsvol_=1371021830999
2013-06-12 08:48:01,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) submit async job-133, details: AsyncJobVO {id:133,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
28, cmd: org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:28,response:json,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,snapshotid:2112f1f0-9fc0-42f5-bde9-900dffeab7df,name:zwpsvol,httpmethod:GET,_:1371021830999,ctxAccountId:2,ctxStartEventId:553},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 08:48:01,876 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=createVolumeresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3Dsnapshotid=2112f1f0-9fc0-42f5-bde9-900dffeab7dfname=zwpsvol_=1371021830999
2013-06-12 08:48:01,879 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-20:job-133) Executing
org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-133
2013-06-12 08:48:01,882 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=0551e5bd-8be0-4ffe-91e5-1a9e65e41284response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371021831100
2013-06-12 08:48:01,941 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=0551e5bd-8be0-4ffe-91e5-1a9e65e41284response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371021831100
2013-06-12 08:48:01,987 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: primary
2013-06-12 08:48:01,997 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: primary2
2013-06-12 08:48:02,004 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: talluri_zonewide
2013-06-12 08:48:02,011 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Secondary storage garbage collector found 0 templates
to cleanup on secondary storage host:
nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware
2013-06-12 08:48:02,028 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184073: Sending { Cmd , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 100011,
[{CleanupSnapshotBackupCommand:{secondaryStoragePoolURL:nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware,dcId:1,accountId:2,volumeId:19,validBackupUUIDs:[cd638b62-94c5-4c32-a3b6-f684ae95e20f/cd638b62-94c5-4c32-a3b6-f684ae95e20f],wait:0}}]
}
2013-06-12 08:48:02,183 DEBUG [agent.transport.Request]
(AgentManager-Handler-10:null) Seq 3-1245184073: Processing: { Ans: , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 10,
[{Answer:{result:true,wait:0}}] }
2013-06-12 08:48:02,184 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184073: Received: { Ans: , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 10, { Answer } }
2013-06-12 08:48:02,197 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184074: Sending { Cmd , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 100011,
[{CleanupSnapshotBackupCommand:{secondaryStoragePoolURL:nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware,dcId:1,accountId:2,volumeId:26,validBackupUUIDs:[f0c770b2-adf1-4116-95b6-3e3b2f1a6aae/f0c770b2-adf1-4116-95b6-3e3b2f1a6aae],wait:0}}]
}
2013-06-12 08:48:02,279 DEBUG [agent.transport.Request]
(AgentManager-Handler-11:null) Seq 3-1245184074: Processing: { Ans: , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 10,
[{Answer:{result:true,wait:0}}] }
2013-06-12 08:48:02,280 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184074: Received: { Ans: , MgmtId:
[jira] [Created] (CLOUDSTACK-2945) [ZWPS][VMWARE]: detach volume is throwing an exception
Srikanteswararao Talluri created CLOUDSTACK-2945:
Summary: [ZWPS][VMWARE]: detach volume is throwing an exception
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request] (DirectAgent-185:null)
Seq 1-2112815433: Processing: { Ans: , MgmtId: 7635042566263, via: 1, Ver: v1,
Flags: 10, [{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 09:01:29,950 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815434: Sending { Cmd , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 100111,
[jira] [Commented] (CLOUDSTACK-2945) [ZWPS][VMWARE]: detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681018#comment-13681018
]
Srikanteswararao Talluri commented on CLOUDSTACK-2945:
--
this is not specific to zone wide primary storage, it is happening with volumes
on cluster scoped primary storage also
===START=== 10.252.192.7 -- GET
command=detachVolumeid=13d85476-1a59-4a7b-a222-ab7da85cc7f7response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022726552
2013-06-12 09:02:57,381 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-19:null) submit async job-139, details: AsyncJobVO {id:139,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
30, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:13d85476-1a59-4a7b-a222-ab7da85cc7f7,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022726552,ctxAccountId:2,ctxStartEventId:575},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:02:57,385 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=13d85476-1a59-4a7b-a222-ab7da85cc7f7response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022726552
2013-06-12 09:02:57,388 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-139) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-139
2013-06-12 09:02:57,433 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-189:null) Seq 1-2112815442: Executing request
2013-06-12 09:02:57,434 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-189:null) Seq 1-2112815442: Response Received:
2013-06-12 09:02:57,434 DEBUG [agent.transport.Request] (DirectAgent-189:null)
Seq 1-2112815442: Processing: { Ans: , MgmtId: 7635042566263, via: 1, Ver: v1,
Flags: 10, [{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:02:57,443 DEBUG [agent.transport.Request]
(Job-Executor-26:job-139) Seq 1-2112815442: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:02:57,444 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-26:job-139) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:02:57,444 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-26:job-139) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:02:57,444 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-26:job-139) Error while collecting disk stats for vm: cpucap from
host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 09:02:57,450 DEBUG [agent.transport.Request]
(Job-Executor-26:job-139) Seq 1-2112815443: Sending { Cmd , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 100111, [{AttachVolumeCommand
[ZWPS][VMWARE]: detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects
[jira] [Updated] (CLOUDSTACK-2945) detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-2945:
-
Summary: detach volume is throwing an exception (was: [ZWPS][VMWARE]:
detach volume is throwing an exception)
detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request]
(DirectAgent-185:null) Seq 1-2112815433: Processing: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10,
[{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at
[jira] [Updated] (CLOUDSTACK-2942) [VPC][VMware]Unexpected exception while creating the private gateway .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-2942: -- Priority: Blocker (was: Critical) Has most of the test cases related to multiple private gateways to VPc failing making it as a blocker Unable to create static route,reboot VPC is throwing exception.,reboot VR --router is not coming up. [VPC][VMware]Unexpected exception while creating the private gateway . -- Key: CLOUDSTACK-2942 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2942 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: VMware5.1 Reporter: manasaveloori Priority: Blocker Fix For: 4.2.0 Attachments: management-server.log Steps: 1.Have a CS with advanced zone and VMware host. 2.Create a VPC. 3.Add a private gateway . Observation: Observed “ Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router” The same is observed while deleting the private gateway and the gateway is not getting deleted. following is the snippet from the management server log: 2013-06-12 17:39:11,253 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Unexpected exception while executing org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3743) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.applyNetworkACLs(VpcVirtualNetworkApplianceManagerImpl.java:717) at com.cloud.network.element.VpcVirtualRouterElement.applyACLItemsToPrivateGw(VpcVirtualRouterElement.java:463) at com.cloud.network.vpc.NetworkACLManagerImpl.applyACLItemsToPrivateGw(NetworkACLManagerImpl.java:325) at com.cloud.network.vpc.NetworkACLManagerImpl.revokeACLItemsForPrivateGw(NetworkACLManagerImpl.java:284) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.destroyPrivateGateway(VpcVirtualNetworkApplianceManagerImpl.java:1053) at com.cloud.network.element.VpcVirtualRouterElement.deletePrivateGateway(VpcVirtualRouterElement.java:378) at com.cloud.network.vpc.VpcManagerImpl.deleteVpcPrivateGateway(VpcManagerImpl.java:1475) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.vpc.VpcManagerImpl.applyVpcPrivateGateway(VpcManagerImpl.java:1436) at org.apache.cloudstack.api.command.admin.vpc.CreatePrivateGatewayCmd.execute(CreatePrivateGatewayCmd.java:158) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-06-12 17:39:11,256 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-31) Complete async job-31, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Resource [DataCenter:1] is unreachable: Unable to apply network acls on router 2013-06-12 17:39:11,286 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-32:job-31) Sync queue (1) is currently empty 2013-06-12 17:39:12,095 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResultjobId=e55475db-71fa-49f1-ad72-23e1b890cfe4response=jsonsessionkey=zS6DxXVJCRyZ3MzvBTZl5fjDY54%3D_=1371019500910 Attaching the management server log for reference. -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681025#comment-13681025 ] Nitin Mehta commented on CLOUDSTACK-2940: - Wei - Thanks for informing about this. I had forgotten. I can revert my changes if you want, but can you submit this soon ? Last comment says that there were files missing, which got changed because of refactoring - have you corrected that ? Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681026#comment-13681026 ] ASF subversion and git services commented on CLOUDSTACK-2347: - Commit 215b638e8eb22fd433ebdc396d4b7a38b0f6796a in branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=215b638 ] CLOUDSTACK-2347: Zone filter for listSnapshots API Added new optional parameter zone id in listSnapshots API which allows to list snapshots with additional criteria. Signed off by :- Nitin Mehta nitin.me...@citrix.com Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681029#comment-13681029 ] Wei Zhou commented on CLOUDSTACK-2940: -- Nitin, Not yet, as I am working on other tasks. your patch looks good. What we need to do is finding a way to improve it. Please feel free to change it to whatever you think. If you do not have time, I can do it after current stuffs (maybe at the end of this month). -Wei Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2945) detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou reassigned CLOUDSTACK-2945:
Assignee: Wei Zhou
detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Wei Zhou
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request]
(DirectAgent-185:null) Seq 1-2112815433: Processing: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10,
[{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 09:01:29,950 DEBUG [agent.transport.Request]
[jira] [Commented] (CLOUDSTACK-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681036#comment-13681036 ] Nitin Mehta commented on CLOUDSTACK-2940: - Wei - I understand. I am occupied with other tasks as well, so might not be able to do it right away, not even by the month end. Feel free to enhance it :). Thanks again for contacting. -Nitin Domain on SSVM is not being updated for download urls that come for CS. --- Key: CLOUDSTACK-2940 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta -- 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-2931) Allow deleting of snapshots that have errored out.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-2931. - Resolution: Fixed Fixed with commit 07e5cbe81394fbd4e36d5ad2fff36cd8eea40a8e Allow deleting of snapshots that have errored out. -- Key: CLOUDSTACK-2931 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2931 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-2347. - Resolution: Fixed Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-2347: Issue Type: Bug (was: New Feature) Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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-2347) Zone filter for listSnapshots API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-2347: Affects Version/s: 4.2.0 Zone filter for listSnapshots API - Key: CLOUDSTACK-2347 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2347 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Snapshot Affects Versions: 4.2.0 Reporter: David Noland Assignee: Harikrishna Patnala Fix For: 4.2.0 Many of the list APIs such as listVirtualMachines, listVPCs, listNetworks, listVolumes, and listTemplates have a zoneid parameter that can be used to restrict the last to a specified zone. The zoneid parameter is also needed for the listSnapshot API in order to properly filter the result set by zone. The returned XML should also return the zone id for each snapshot. -- 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] [Closed] (CLOUDSTACK-1392) NPE while creating template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri closed CLOUDSTACK-1392. Resolution: Fixed NPE while creating template --- Key: CLOUDSTACK-1392 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1392 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Environment: advanced zone Reporter: Srikanteswararao Talluri Assignee: edison su Priority: Blocker Fix For: 4.2.0 NPE while creating template Unexpected exception while executing org.apache.cloudstack.api.command.user.template.CreateTemplateCmd java.lang.NullPointerException at org.apache.cloudstack.storage.image.manager.ImageDataStoreManagerImpl.getImageDataStore(ImageDataStoreManagerImpl.java:60) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at org.apache.cloudstack.storage.datastore.DataStoreManagerImpl.getDataStore(DataStoreManagerImpl.java:47) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at
[jira] [Updated] (CLOUDSTACK-2946) Storage capacity shown in UI is incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2946: Fix Version/s: 4.2.0 Assignee: Nitin Mehta Affects Version/s: 4.2.0 Storage capacity shown in UI is incorrect - Key: CLOUDSTACK-2946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2946 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta 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-1392) NPE while creating template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681059#comment-13681059
]
Srikanteswararao Talluri commented on CLOUDSTACK-1392:
--
I am closing this issue and opening new one for the below mentioned issue as
the original was addressed in this bug and it is fixed.
===START=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,111 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-5:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 10:37:02,111 INFO [cloud.api.ApiServer] (catalina-exec-5:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
2013-06-12 10:37:02,114 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371028371208
2013-06-12 10:37:02,283 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-140, details: AsyncJobVO {id:140,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId:
206, cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
cmdOriginator: null, cmdInfo:
{sessionkey:78yZ9E1cc1DcOk9TqRoqnU2ycyU\u003d,ctxUserId:2,httpmethod:GET,osTypeId:d59bb3b2-cdf8-11e2-8fc8-06f1ac77,isPublic:true,response:json,id:206,displayText:td,snapshotid:3528aa5d-ddfe-4527-8887-2b1047c61e53,passwordEnabled:false,name:td,_:1371028371311,ctxAccountId:2,ctxStartEventId:579},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 10:37:02,286 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===END=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,289 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-140
2013-06-12 10:37:02,403 DEBUG [cloud.template.TemplateManagerImpl]
(Job-Executor-27:job-140) Failed to create
templatejava.lang.NullPointerException
2013-06-12 10:37:02,426 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to create
templatejava.lang.NullPointerException
at
com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1770)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 10:37:02,433 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Complete async job-140, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: Failed to create
templatejava.lang.NullPointerException
NPE while creating template
---
Key: CLOUDSTACK-1392
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1392
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Environment: advanced zone
Reporter: Srikanteswararao Talluri
Assignee: edison su
Priority: Blocker
[jira] [Created] (CLOUDSTACK-2946) Storage capacity shown in UI is incorrect
Nitin Mehta created CLOUDSTACK-2946: --- Summary: Storage capacity shown in UI is incorrect Key: CLOUDSTACK-2946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2946 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta -- 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-2923) Delete Secondary storage of a Zone is giving java NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2923: Assignee: Nitin Mehta Delete Secondary storage of a Zone is giving java NPE - Key: CLOUDSTACK-2923 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2923 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta Repro Steps: 1.Create a Zone 2. Create few VMs to it 3.Delete Secondary storage Bug: Ms logs shows Java NPE Expected Result: Delete sceondary storage should not give any NPE We are getting NPE in Ms log once we delete Secondary storage MS Log shows : 2012-11-16 13:36:23,370 WARN [cloud.vm.SystemVmLoadScanner] (consoleproxy-1:null) Unexpected exception null java.lang.NullPointerException at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:1177) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1894) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:166) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:101) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:30) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:79) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:69) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2924) Recurring snapshot schedule not showing up in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Mehta updated CLOUDSTACK-2924:
Assignee: Nitin Mehta
Recurring snapshot schedule not showing up in UI
Key: CLOUDSTACK-2924
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2924
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Reporter: Nitin Mehta
Assignee: Nitin Mehta
Issue is now exhibiting itself again:
Volume id 502 has 4 snapshots, two DAILY, 1 WEEKLY, and 1 MONTHLY. Most
recent snapshot is today.
request:
http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotslistAll=truepage=1pagesize=20volumeid=502response=jsonsessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3D_=1354580214377
response:
{ listsnapshotsresponse : { count:4 ,snapshot : [
{id:0c2d17c1-a537-4d19-b83f-c13539d656a5,account:profserv,domainid:d7030e4e-f105-4996-bf82-bd4ec3e4cf38,domain:PS,snapshottype:DAILY,volumeid:502,volumename:i-8-478-VM-ROOT,volumetype:ROOT,created:2012-12-03T02:03:38-0800,name:i-8-478-VM_i-8-478-VM-ROOT_20121203100338,intervaltype:DAILY,state:BackedUp,tags:[]},
{id:d2438a81-6874-4e9b-8335-42c7f1d09691,account:profserv,domainid:d7030e4e-f105-4996-bf82-bd4ec3e4cf38,domain:PS,snapshottype:WEEKLY,volumeid:502,volumename:i-8-478-VM-ROOT,volumetype:ROOT,created:2012-12-03T02:03:38-0800,name:i-8-478-VM_i-8-478-VM-ROOT_20121203100338,intervaltype:WEEKLY,state:BackedUp,tags:[]},
{id:03ceeafc-83ac-40fa-85b1-a18464429206,account:profserv,domainid:d7030e4e-f105-4996-bf82-bd4ec3e4cf38,domain:PS,snapshottype:MONTHLY,volumeid:502,volumename:i-8-478-VM-ROOT,volumetype:ROOT,created:2012-12-02T02:03:36-0800,name:i-8-478-VM_i-8-478-VM-ROOT_20121202100336,intervaltype:MONTHLY,state:BackedUp,tags:[]},
{id:29524d7e-e420-4193-9169-0d3cc4b1c810,account:profserv,domainid:d7030e4e-f105-4996-bf82-bd4ec3e4cf38,domain:PS,snapshottype:DAILY,volumeid:502,volumename:i-8-478-VM-ROOT,volumetype:ROOT,created:2012-12-02T02:03:35-0800,name:i-8-478-VM_i-8-478-VM-ROOT_20121202100335,intervaltype:DAILY,state:BackedUp,tags:[]}
] } }
However, listing the recurring schedule shows nothing:
request:
http://dogfood.lab.vmops.com:8080/client/api?command=listSnapshotPoliciesresponse=jsonsessionkey=YhtXeqcrNUxE6LEVHB1%2Ff9q3PLU%3Dvolumeid=502_=1354580037175
response:
{ listsnapshotpoliciesresponse : { } }
--
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-2947) NPE while creating template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-2947:
-
Description:
NPE while creating template
===START=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,111 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-5:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 10:37:02,111 INFO [cloud.api.ApiServer] (catalina-exec-5:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
2013-06-12 10:37:02,114 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371028371208
2013-06-12 10:37:02,283 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-140, details: AsyncJobVO {id:140,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId:
206, cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
cmdOriginator: null, cmdInfo:
{sessionkey:78yZ9E1cc1DcOk9TqRoqnU2ycyU\u003d,ctxUserId:2,httpmethod:GET,osTypeId:d59bb3b2-cdf8-11e2-8fc8-06f1ac77,isPublic:true,response:json,id:206,displayText:td,snapshotid:3528aa5d-ddfe-4527-8887-2b1047c61e53,passwordEnabled:false,name:td,_:1371028371311,ctxAccountId:2,ctxStartEventId:579},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 10:37:02,286 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===END=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,289 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-140
2013-06-12 10:37:02,403 DEBUG [cloud.template.TemplateManagerImpl]
(Job-Executor-27:job-140) Failed to create
templatejava.lang.NullPointerException
2013-06-12 10:37:02,426 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to create
templatejava.lang.NullPointerException
at
com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1770)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 10:37:02,433 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Complete async job-140, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: Failed to create
templatejava.lang.NullPointerException
was:
NPE while creating template
Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
java.lang.NullPointerException
at
org.apache.cloudstack.storage.image.manager.ImageDataStoreManagerImpl.getImageDataStore(ImageDataStoreManagerImpl.java:60)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
[jira] [Updated] (CLOUDSTACK-2937) Scheduled snapshot events should be shown to users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2937: Assignee: Nitin Mehta Scheduled snapshot events should be shown to users -- Key: CLOUDSTACK-2937 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2937 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta Scheduled snapshot events are generated from root account rather than the initiator accounts. Hence these initiated users are missing all events related to their snapshots. IMPACT == Users who have scheduled their snapshots are missing all the snapshot events related to them as they are generated from root/system account. DETAILED DESCRIPTION == Recurring snapshots are intiaited by a user, but they are created by Root user on CS. Whenever a snapshot is created, alongwith, a notification/event is also created. Since Root user creates the snapshot, the event is associated with Root user and not with the user who initiated it. -- 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-2689) Create volume after upgrade from snapshot taken in 2.2.14 deletes the snapshot physically from sec. storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2689: Assignee: Nitin Mehta Create volume after upgrade from snapshot taken in 2.2.14 deletes the snapshot physically from sec. storage. Key: CLOUDSTACK-2689 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2689 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta In pre 3.0 release for any install be it fresh or upgraded the swift_id is 0 bcz the swift_id is long and not the Java object Long and so by default gets set to 0 instead of NULL in the DB. Now the code assumes that the snapshot is present in swift and can be deleted from sec. storage after any operation on the snapshot by checking the condition snapshot.getSwiftId() != null.It should have checked for snapshot.getSwiftId() != null snapshot.getSwiftId() != 0. Why this not an issue in fresh installs for 3.0 series ? I think in 3.0 we added all the code for swift. There was also a code change for Action which made swift_id as JAVA Long and so for fresh installs in 3.0 series swift_id was NULL in the DB by default and hence these operations succeeded without deleting snapshot physically from sec. storage. But for any upgraded version from 2.2.8 onwards (when swift_id got first introduced) this would be 0 and since we check only for SwiftId() != null we will delete the snapshot from sec. storage. -- 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-2669) ScaleVm - resource limit and count logic missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2669: Fix Version/s: 4.2.0 Assignee: Nitin Mehta ScaleVm - resource limit and count logic missing Key: CLOUDSTACK-2669 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2669 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Assignee: Nitin Mehta 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-2922) System VM's agent dosent run in the Vmware setup with the latest System VM template.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy reassigned CLOUDSTACK-2922: - Assignee: Jayapal Reddy System VM's agent dosent run in the Vmware setup with the latest System VM template. Key: CLOUDSTACK-2922 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2922 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Assignee: Jayapal Reddy Priority: Blocker Tried creating a Advanced Zone with the new system VM template. The System Vm's came up but the builtin template is not downloaded. When tried to debug the cloud agent is not running in the SSVM. -- 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-2946) Storage capacity shown in UI is incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681065#comment-13681065 ] ASF subversion and git services commented on CLOUDSTACK-2946: - Commit 83fcba9ee64cdf4fe28e2c751fcfb2f83f9938d2 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=83fcba9 ] CLOUDSTACK-2946 CS-15158: Correcting the allocated size for local storage in listStoragePools Storage capacity shown in UI is incorrect - Key: CLOUDSTACK-2946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2946 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2946) Storage capacity shown in UI is incorrect
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-2946. - Resolution: Fixed Storage capacity shown in UI is incorrect - Key: CLOUDSTACK-2946 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2946 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2922) System VM's agent dosent run in the Vmware setup with the latest System VM template.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-2922. --- Resolution: Fixed This issue is specific to template. In the new template /dev/cdrom2 is created instead of /dev/cdrom1 The correct template is create by Abhi. System VM's agent dosent run in the Vmware setup with the latest System VM template. Key: CLOUDSTACK-2922 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2922 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Assignee: Jayapal Reddy Priority: Blocker Tried creating a Advanced Zone with the new system VM template. The System Vm's came up but the builtin template is not downloaded. When tried to debug the cloud agent is not running in the SSVM. -- 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-1704) cluster is not getting disabled after threshold value set to global parameter cluster.cpu.allocated.capacity.disablethreshold
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681069#comment-13681069 ] ASF subversion and git services commented on CLOUDSTACK-1704: - Commit a30f9fa64a49acfe7d3ac57f2ef9d890473f48c4 in branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a30f9fa ] Fix for CLOUDSTACK-1704 and CLOUDSTACK-1622 Signed-off-by: Abhinandan Prateek aprat...@apache.org cluster is not getting disabled after threshold value set to global parameter cluster.cpu.allocated.capacity.disablethreshold --- Key: CLOUDSTACK-1704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Harikrishna Patnala Fix For: 4.2.0 Attachments: cloud-backup.dmp, log.rar -- cluster.cpu.allocated.capacity.disablethreshold Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available. --when i set cluster.cpu.allocated.capacity.disablethreshold to blank character at cluster level , Global parametercluster.cpu.allocated.capacity.disablethreshold stop working. Steps to reproduce 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , 2-Restart MS 3-Set cluster.cpu.allocated.capacity.desablethreshold to blank character 4-Deploy some vms , so that cpu utilizatio should be 0.5 Expected - Cluster should be disabled after threshold value Actual --- cluster is not getting disabled after threshold value -- 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-2510) 2013-05-15 10:56:24,530 ERROR [cloud.api.ApiServer] (catalina-exec-14:null) unhandled exception executing api command: listStoragePools java.lang.NullPointerExcept
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681068#comment-13681068
]
Srikanteswararao Talluri commented on CLOUDSTACK-2510:
--
I have hit this issue on vmware setup while adding second zone wide primary
storage. Another observation is , this issue is not seen after some time. I
could list the storage pools successfully
===START=== 10.252.192.7 -- GET
command=createStoragePoolscope=zonezoneid=15a42cd5-317c-4c48-b331-d1cc3f9f2eeahypervisor=VMwarename=zwps2url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Ftalluri%2Fvmwarezwps2response=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371029094785
2013-06-12 10:49:05,614 DEBUG [cloud.storage.StorageManagerImpl]
(catalina-exec-19:null) Adding pool null to host 1
2013-06-12 10:49:05,622 DEBUG [agent.transport.Request] (catalina-exec-19:null)
Seq 1-2112815925: Sending { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1,
Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:4,uuid:7a535f47-191f-3048-a0a0-f5d97b010c4e,host:10.147.28.7,path:/export/home/talluri/vmwarezwps2,port:2049,type:NetworkFilesystem},localPath:/mnt//7a535f47-191f-3048-a0a0-f5d97b010c4e,wait:0}}]
}
2013-06-12 10:49:05,623 DEBUG [agent.transport.Request] (catalina-exec-19:null)
Seq 1-2112815925: Executing: { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1,
Flags: 100011,
[{ModifyStoragePoolCommand:{add:true,pool:{id:4,uuid:7a535f47-191f-3048-a0a0-f5d97b010c4e,host:10.147.28.7,path:/export/home/talluri/vmwarezwps2,port:2049,type:NetworkFilesystem},localPath:/mnt//7a535f47-191f-3048-a0a0-f5d97b010c4e,wait:0}}]
}
2013-06-12 10:49:05,623 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-206:null) Seq 1-2112815925: Executing request
2013-06-12 10:49:05,624 INFO [vmware.resource.VmwareResource]
(DirectAgent-206:10.147.40.7) Executing resource ModifyStoragePoolCommand:
{add:true,pool:{id:4,uuid:7a535f47-191f-3048-a0a0-f5d97b010c4e,host:10.147.28.7,path:/export/home/talluri/vmwarezwps2,port:2049,type:NetworkFilesystem},localPath:/mnt//7a535f47-191f-3048-a0a0-f5d97b010c4e,wait:0}
2013-06-12 10:49:06,041 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=ec2f72db-0095-4ca0-aa9d-bc2e45103964response=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371029095223
2013-06-12 10:49:06,074 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=ec2f72db-0095-4ca0-aa9d-bc2e45103964response=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371029095223
2013-06-12 10:49:07,249 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===START=== 10.252.192.7 -- GET
command=listZonesresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371029096459
2013-06-12 10:49:07,251 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371029096334
2013-06-12 10:49:07,268 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-1:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 10:49:07,269 INFO [cloud.api.ApiServer] (catalina-exec-1:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
2013-06-12 10:49:07,272 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371029096334
2013-06-12 10:49:07,277 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===END=== 10.252.192.7 -- GET
command=listZonesresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371029096459
2013-06-12 10:49:07,310 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===START=== 10.252.192.7 -- GET
command=listPodsresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dpage=1pagesize=1_=1371029096520
2013-06-12 10:49:07,325 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===END=== 10.252.192.7 -- GET
command=listPodsresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dpage=1pagesize=1_=1371029096520
2013-06-12 10:49:07,361 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===START=== 10.252.192.7 -- GET
command=listClustersresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dpage=1pagesize=1_=1371029096568
2013-06-12 10:49:07,384 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=listClustersresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dpage=1pagesize=1_=1371029096568
2013-06-12 10:49:07,417 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.252.192.7 -- GET
[jira] [Closed] (CLOUDSTACK-2922) System VM's agent dosent run in the Vmware setup with the latest System VM template.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-2922. Verified it with the new template created by Abhi and it is working fine. System VM's agent dosent run in the Vmware setup with the latest System VM template. Key: CLOUDSTACK-2922 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2922 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Assignee: Jayapal Reddy Priority: Blocker Tried creating a Advanced Zone with the new system VM template. The System Vm's came up but the builtin template is not downloaded. When tried to debug the cloud agent is not running in the SSVM. -- 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-1622) Global parameter cluster.memory.allocated.capacity.disablethreshold is not disabling cluster after threshold value
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-1622. - Resolution: Fixed Global parameter cluster.memory.allocated.capacity.disablethreshold is not disabling cluster after threshold value - Key: CLOUDSTACK-1622 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1622 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Harikrishna Patnala Fix For: 4.2.0 Attachments: logs.rar Cluster should get disable after alocated memory crosses threshold of global parameter cluster.memory.allocated.capacity.disablethreshold . ---when i set cluster.memory.allocated.capacity.disablethreshold to blank character at cluster level , Global parametercluster.memory.allocated.capacity.disablethreshold stop working. Steps to repo --- 1-Set Global parameter cluster.memory.allocated.capacity.disablethreshold to some value say 0.3 2-set cluster level parameter cluster.memory.allocated.capacity.disablethreshold to blank space 3-Deploy vms Expected After threshold value (0.3) cluster should get disable Actual - Cluster is not getting disable -- 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-1704) cluster is not getting disabled after threshold value set to global parameter cluster.cpu.allocated.capacity.disablethreshold
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-1704. - Resolution: Fixed cluster is not getting disabled after threshold value set to global parameter cluster.cpu.allocated.capacity.disablethreshold --- Key: CLOUDSTACK-1704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: prashant kumar mishra Assignee: Harikrishna Patnala Fix For: 4.2.0 Attachments: cloud-backup.dmp, log.rar -- cluster.cpu.allocated.capacity.disablethreshold Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available. --when i set cluster.cpu.allocated.capacity.disablethreshold to blank character at cluster level , Global parametercluster.cpu.allocated.capacity.disablethreshold stop working. Steps to reproduce 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , 2-Restart MS 3-Set cluster.cpu.allocated.capacity.desablethreshold to blank character 4-Deploy some vms , so that cpu utilizatio should be 0.5 Expected - Cluster should be disabled after threshold value Actual --- cluster is not getting disabled after threshold value -- 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-2304) NPE while migrating volume from one zone wide primary to another
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-2304:
-
Environment: KVM/VMware deployment with Zone wide primary storage (was:
KVM deployment with Zone wide primary storage)
NPE while migrating volume from one zone wide primary to another
Key: CLOUDSTACK-2304
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2304
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: KVM/VMware deployment with Zone wide primary storage
Reporter: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.2.0
Try to migrate a volume from one zone wide primary storage to another.
===START=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,384 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-3:null) submit async job-97, details: AsyncJobVO {id:97,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,sessionkey:yMNGYR64PRQhdJaPj99Bvs2KDDE\u003d,ctxUserId:2,storageid:230ae4af-0446-3929-a8cd-63ab88f31ab1,_:1367485037836,volumeid:d9efc3d8-1612-4998-95d7-c713e90b7173,ctxAccountId:2,ctxStartEventId:310},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-02 20:06:59,388 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,391 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
2013-05-02 20:06:59,423 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-66:job-97) migrate volume failed:java.lang.NullPointerException
2013-05-02 20:06:59,424 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Complete async job-97, jobStatus: 1, resultCode: 0,
result: null
2013-05-02 20:06:59,434 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Done executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
--
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-2304) [ZWPS]NPE while migrating volume from one zone wide primary to another
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanteswararao Talluri updated CLOUDSTACK-2304:
-
Summary: [ZWPS]NPE while migrating volume from one zone wide primary to
another (was: NPE while migrating volume from one zone wide primary to another)
[ZWPS]NPE while migrating volume from one zone wide primary to another
--
Key: CLOUDSTACK-2304
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2304
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: KVM/VMware deployment with Zone wide primary storage
Reporter: Srikanteswararao Talluri
Priority: Critical
Fix For: 4.2.0
Try to migrate a volume from one zone wide primary storage to another.
===START=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,384 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-3:null) submit async job-97, details: AsyncJobVO {id:97,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,sessionkey:yMNGYR64PRQhdJaPj99Bvs2KDDE\u003d,ctxUserId:2,storageid:230ae4af-0446-3929-a8cd-63ab88f31ab1,_:1367485037836,volumeid:d9efc3d8-1612-4998-95d7-c713e90b7173,ctxAccountId:2,ctxStartEventId:310},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-02 20:06:59,388 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,391 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
2013-05-02 20:06:59,423 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-66:job-97) migrate volume failed:java.lang.NullPointerException
2013-05-02 20:06:59,424 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Complete async job-97, jobStatus: 1, resultCode: 0,
result: null
2013-05-02 20:06:59,434 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Done executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
--
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-2948) Vm is created using the root directory on the Zone which is dedicated to a Sub domain.
Kiran Koneti created CLOUDSTACK-2948: Summary: Vm is created using the root directory on the Zone which is dedicated to a Sub domain. Key: CLOUDSTACK-2948 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2948 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Below are the steps followed: 1)In a freshly installed host created a Sub domain under the root Domain.(domain kiran is created). 2)While creating a Zone dedicated it to the subdomain created in the step1. 3)The Zone creation was Successful . 4)Then logged in as the root user and tried to create a VM in the Zone which is dedicated to the Subdomain. 5)The VM creation was successful. Expected Result is the VM creation from the root domain should fail in this Zone as the Zone is dedicated to another Subdomain. -- 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-2642) [XenServer] Add support for XenServer 6.2.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681072#comment-13681072 ] ASF subversion and git services commented on CLOUDSTACK-2642: - Commit fe506d9b68395358457b17bd5788ed6cfbe589b7 in branch refs/heads/master from [~swamy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fe506d9 ] CLOUDSTACK-2642: [XenServer] Add support for XenServer 6.2.0 Currently XcpServerDiscoverer.java is only allowing till XenServer 6.1.0. Added code to support XenServer 6.2.0. Also, added support to allow the RC build of XenSever 6.2.0. Signed-off-by: venkataswamybabu budumuru venkataswamybabu.budum...@citrix.com Signed-off-by: Abhinandan Prateek aprat...@apache.org [XenServer] Add support for XenServer 6.2.0 Key: CLOUDSTACK-2642 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2642 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.2.0 Environment: commit # fce59b8fc42412f87ccbda5cf4f53e1465935070 Reporter: venkata swamybabu budumuru Assignee: venkata swamybabu budumuru Priority: Critical Fix For: 4.2.0 Steps to reproduce : 1. Have a CloudStack 4.2 setup 2. Try to create an advanced zone using the XenServer 6.2.0 Observations : (i) Adding host fails because XcpDiscoverer.java is currently allowing only till XenServer 6.1.0 release. -- 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-2949) [VPC][UI]ListNetworkACL while creating a private gateway is listing all the ACLs irrespective of VPC/zone/Domian/account.
manasaveloori created CLOUDSTACK-2949: - Summary: [VPC][UI]ListNetworkACL while creating a private gateway is listing all the ACLs irrespective of VPC/zone/Domian/account. Key: CLOUDSTACK-2949 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2949 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: manasaveloori Fix For: 4.2.0 Steps: 1. Have a CS with 2 advanced zones and 1 non root account user. 2. Login as admin. 3. Create a VPC in zone1 and create an ACL under that VPC. 4. Create a VPC in zone 2 and create an ACL under that VPC. 5. Now login as a user (non root domain). 6. Create a VPC and create an ACL under that VPC. 7. Login as admin and try to create a private gateway for a VPC in any zone. 8. The listnetwork ACL is listing all the ACLs irrespective of VPCs/Zones/Domians. Observation The API passed here to list ACLs is http://10.147.38.154:8096/client/api?command=listNetworkACLLists vpc_id parameter is not passed. -- 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-2950) VM craetion using the explicit dedication affinity group in the Root Domain is successful even if has no dedicated hosts.
Kiran Koneti created CLOUDSTACK-2950: Summary: VM craetion using the explicit dedication affinity group in the Root Domain is successful even if has no dedicated hosts. Key: CLOUDSTACK-2950 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2950 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Below are the steps followed: 1)In a freshly installed setup where there is only a single cluster and single host created a Affinity group for explicit dedication. 2)Then once the Zone is up tried to create a VM using the affinity group. 3)The Vm creation was Successful. The expected result is the Vm creation should be failed as it dosent have any dedicated 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-2948) Vm is created using the root directory on the Zone which is dedicated to a Sub domain.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681075#comment-13681075 ] Kiran Koneti commented on CLOUDSTACK-2948: -- The dedicated Resource table is as below: mysql select * from dedicated_resources; ++--++++-+---++ | id | uuid | data_center_id | pod_id | cluster_id | host_id | domain_id | account_id | ++--++++-+---++ | 3 | e22282da-e57a-47c2-a758-a6d1be4dd817 | 3 | NULL | NULL |NULL | 2 | NULL | ++--++++-+---++ 1 row in set (0.00 sec) Vm is created using the root directory on the Zone which is dedicated to a Sub domain. -- Key: CLOUDSTACK-2948 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2948 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Below are the steps followed: 1)In a freshly installed host created a Sub domain under the root Domain.(domain kiran is created). 2)While creating a Zone dedicated it to the subdomain created in the step1. 3)The Zone creation was Successful . 4)Then logged in as the root user and tried to create a VM in the Zone which is dedicated to the Subdomain. 5)The VM creation was successful. Expected Result is the VM creation from the root domain should fail in this Zone as the Zone is dedicated to another Subdomain. -- 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-2934) list firewall rules should list uuids in response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy reassigned CLOUDSTACK-2934: - Assignee: Jayapal Reddy list firewall rules should list uuids in response - Key: CLOUDSTACK-2934 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2934 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Assignee: Jayapal Reddy listfirewallrules is showing numeric ip address id and listegressfirewallrules is listing numeric network id. The APIs should list UUID instead of numeric ids. -- 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-2950) VM craetion using the explicit dedication affinity group in the Root Domain is successful even if has no dedicated hosts.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava reassigned CLOUDSTACK-2950: -- Assignee: Saksham Srivastava VM craetion using the explicit dedication affinity group in the Root Domain is successful even if has no dedicated hosts. - Key: CLOUDSTACK-2950 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2950 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Saksham Srivastava Priority: Critical Fix For: 4.2.0 Below are the steps followed: 1)In a freshly installed setup where there is only a single cluster and single host created a Affinity group for explicit dedication. 2)Then once the Zone is up tried to create a VM using the affinity group. 3)The Vm creation was Successful. The expected result is the Vm creation should be failed as it dosent have any dedicated 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] [Assigned] (CLOUDSTACK-2948) Vm is created using the root directory on the Zone which is dedicated to a Sub domain.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava reassigned CLOUDSTACK-2948: -- Assignee: Saksham Srivastava Vm is created using the root directory on the Zone which is dedicated to a Sub domain. -- Key: CLOUDSTACK-2948 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2948 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Assignee: Saksham Srivastava Priority: Critical Fix For: 4.2.0 Below are the steps followed: 1)In a freshly installed host created a Sub domain under the root Domain.(domain kiran is created). 2)While creating a Zone dedicated it to the subdomain created in the step1. 3)The Zone creation was Successful . 4)Then logged in as the root user and tried to create a VM in the Zone which is dedicated to the Subdomain. 5)The VM creation was successful. Expected Result is the VM creation from the root domain should fail in this Zone as the Zone is dedicated to another Subdomain. -- 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-2951) [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set.
venkata swamybabu budumuru created CLOUDSTACK-2951: -- Summary: [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set. Key: CLOUDSTACK-2951 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2951 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: commit # 673b293d75419a4b76379092db2b204cdc6160a4 Reporter: venkata swamybabu budumuru Assignee: Jessica Tomechak Priority: Minor Fix For: 4.2.0 Steps to reproduce : 1. Have at least 2 zones (1 Basic zone and another Advanced zone) with latest CloudStack setup 2. Make sure all the system vm templates and built in centOS templates listed before setting the zone-type drop down to some value. 3. Now set the zone type drop down (which can be found at top right corner of mgmt server main page) to either advanced/basic 4. Try to add instance and move to add template screen 5. open up the firebug as well and observe Observations: (i) Add template screen doesn't list any templates (ii) we can see in firebug that listTemplates API fired for featured, community etc.,, with zone type=advanced/basic, but, nothing returned as response. Attaching the screenshots, mgmt server logs, db dump to the bug. Also, found another issue i.e. Set Zone type drop down value to advanced/basic then go to Templates page Observations: (i) It lists all the templates irrespective of which zone they belong to. Attached a screenshot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2951) [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-2951: --- Attachment: Screen Shot 2013-06-12 at 3.25.08 PM.png Screen Shot 2013-06-12 at 3.20.36 PM.png Screen Shot 2013-06-12 at 3.19.46 PM.png [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set. --- Key: CLOUDSTACK-2951 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2951 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: commit # 673b293d75419a4b76379092db2b204cdc6160a4 Reporter: venkata swamybabu budumuru Assignee: Jessica Tomechak Priority: Minor Fix For: 4.2.0 Attachments: Screen Shot 2013-06-12 at 3.19.46 PM.png, Screen Shot 2013-06-12 at 3.20.36 PM.png, Screen Shot 2013-06-12 at 3.25.08 PM.png Steps to reproduce : 1. Have at least 2 zones (1 Basic zone and another Advanced zone) with latest CloudStack setup 2. Make sure all the system vm templates and built in centOS templates listed before setting the zone-type drop down to some value. 3. Now set the zone type drop down (which can be found at top right corner of mgmt server main page) to either advanced/basic 4. Try to add instance and move to add template screen 5. open up the firebug as well and observe Observations: (i) Add template screen doesn't list any templates (ii) we can see in firebug that listTemplates API fired for featured, community etc.,, with zone type=advanced/basic, but, nothing returned as response. Attaching the screenshots, mgmt server logs, db dump to the bug. Also, found another issue i.e. Set Zone type drop down value to advanced/basic then go to Templates page Observations: (i) It lists all the templates irrespective of which zone they belong to. Attached a screenshot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2945) detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681080#comment-13681080
]
ASF subversion and git services commented on CLOUDSTACK-2945:
-
Commit 51a3a5a9b56426de4b3818b900d493cf9f439779 in branch refs/heads/master
from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=51a3a5a ]
CLOUDSTACK-2945: ignore collect disk statistics if vm is not running on KVM or
XenServer
detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Wei Zhou
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request]
(DirectAgent-185:null) Seq 1-2112815433: Processing: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10,
[{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at
[jira] [Updated] (CLOUDSTACK-2951) [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-2951: --- Attachment: management-server.log cloud.sql apilog.log [Mixed-Zone-Management] during add Instance wizard, listTemplates API is not listing any templates if the Zone type is set. --- Key: CLOUDSTACK-2951 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2951 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: commit # 673b293d75419a4b76379092db2b204cdc6160a4 Reporter: venkata swamybabu budumuru Assignee: Jessica Tomechak Priority: Minor Fix For: 4.2.0 Attachments: apilog.log, cloud.sql, management-server.log, Screen Shot 2013-06-12 at 3.19.46 PM.png, Screen Shot 2013-06-12 at 3.20.36 PM.png, Screen Shot 2013-06-12 at 3.25.08 PM.png Steps to reproduce : 1. Have at least 2 zones (1 Basic zone and another Advanced zone) with latest CloudStack setup 2. Make sure all the system vm templates and built in centOS templates listed before setting the zone-type drop down to some value. 3. Now set the zone type drop down (which can be found at top right corner of mgmt server main page) to either advanced/basic 4. Try to add instance and move to add template screen 5. open up the firebug as well and observe Observations: (i) Add template screen doesn't list any templates (ii) we can see in firebug that listTemplates API fired for featured, community etc.,, with zone type=advanced/basic, but, nothing returned as response. Attaching the screenshots, mgmt server logs, db dump to the bug. Also, found another issue i.e. Set Zone type drop down value to advanced/basic then go to Templates page Observations: (i) It lists all the templates irrespective of which zone they belong to. Attached a screenshot for the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2945) detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou resolved CLOUDSTACK-2945.
--
Resolution: Fixed
detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Wei Zhou
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request]
(DirectAgent-185:null) Seq 1-2112815433: Processing: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10,
[{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 09:01:29,950 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136)
[jira] [Closed] (CLOUDSTACK-2945) detach volume is throwing an exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou closed CLOUDSTACK-2945.
detach volume is throwing an exception
--
Key: CLOUDSTACK-2945
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2945
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Wei Zhou
Fix For: 4.2.0
1. Create a data volume on zone scoped primary storage
2. attach it to a VM whose root volume is on zone scoped primary storage
3. detach the volume attached in step2
===START=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,877 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-136, details: AsyncJobVO {id:136,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
27, cmd: org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:493e8653-d2c6-4b91-854e-3f4ec1a7af8d,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,httpmethod:GET,_:1371022639049,ctxAccountId:2,ctxStartEventId:565},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 09:01:29,880 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=detachVolumeid=493e8653-d2c6-4b91-854e-3f4ec1a7af8dresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371022639049
2013-06-12 09:01:29,882 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-23:job-136) Executing
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd for job-136
2013-06-12 09:01:29,934 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Executing request
2013-06-12 09:01:29,935 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-185:null) Seq 1-2112815433: Response Received:
2013-06-12 09:01:29,935 DEBUG [agent.transport.Request]
(DirectAgent-185:null) Seq 1-2112815433: Processing: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10,
[{UnsupportedAnswer:{result:false,details:Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?,wait:0}}] }
2013-06-12 09:01:29,943 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815433: Received: { Ans: , MgmtId:
7635042566263, via: 1, Ver: v1, Flags: 10, { UnsupportedAnswer } }
2013-06-12 09:01:29,943 WARN [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Unsupported Command: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-23:job-136) Details from executing class
com.cloud.agent.api.GetVmDiskStatsCommand: Unsupported command
issued:com.cloud.agent.api.GetVmDiskStatsCommand. Are you sure you got the
right type of server?
2013-06-12 09:01:29,944 WARN [cloud.vm.UserVmManagerImpl]
(Job-Executor-23:job-136) Error while collecting disk stats for vm: zwpsroot
from host: 10.147.40.7
java.lang.ClassCastException: com.cloud.agent.api.UnsupportedAnswer cannot be
cast to com.cloud.agent.api.GetVmDiskStatsAnswer
at
com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3434)
at
com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1910)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 09:01:29,950 DEBUG [agent.transport.Request]
(Job-Executor-23:job-136) Seq 1-2112815434: Sending
[jira] [Created] (CLOUDSTACK-2952) [VPC][PrivateGateway]Creating a private gateway with ACL belonging to other VPC should throw an appropriate error to admin user.
manasaveloori created CLOUDSTACK-2952: - Summary: [VPC][PrivateGateway]Creating a private gateway with ACL belonging to other VPC should throw an appropriate error to admin user. Key: CLOUDSTACK-2952 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2952 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: manasaveloori Fix For: 4.2.0 Steps: 1. Have a CS with 2 advanced zones and 1 non root account user. 2. Login as admin. 3. Create a VPC in zone1 and create an ACL under that VPC. 4. Create a VPC in zone 2 and create an ACL under that VPC. 5. Now login as a user (non root domain). 6. Create a VPC and create an ACL under that VPC. 7. Login as admin and create a private gateway by selecting the ACL belong to other VPC/Account/domain. Observation: Admin user is able to create a private gateway by selecting ACL which is not belong to that VPC. Expected behavior: Should throw the message as ACL does not belong to that VPC/domain/account and private gateway should not get created. -- 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-2953) [Multiple_IP_Ranges] VM does not get the public key from VR incase of multiple subnets per vlan
Sanjeev N created CLOUDSTACK-2953: - Summary: [Multiple_IP_Ranges] VM does not get the public key from VR incase of multiple subnets per vlan Key: CLOUDSTACK-2953 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2953 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: Setup: Basic zone with xen cluster Build: Laset master build Reporter: Sanjeev N Priority: Critical Fix For: 4.2.0 VM does not get the public key from VR incase of multiple subnets per vlan Steps to Reproduce: 1.Bring up CS in basic zone with xen server 2.Add guest ip ranges in two CIDRs in the same vlan 3.Generate ssh key pair using follwoing api: http://10.147.59.119:8096/client/api?command=createSSHKeyPairname=test2account=admindomainid=1 4.Register a template to CS which has ssh key reset script copied. 5.Deploy two guest vms with ip addresses from both the CIDRs with the key pair generated above Expected Behavior: === In both the VM's authouried keys file should contain the public key and key based access to vm should succeed. Actual Result: Guest vm deployed with ip address from first cidr able to fetch the public key but not the other vm. Observations: === On VR web service is running on port 80 with ip address from the primary subnet but not with the alias ip , hence fetching keys from the VR with alias ip address failed. [root@ceddb099-8fee-462f-9520-c01b57762e4d ~]# wget http://10.147.43.131/latest/public-keys --2013-06-12 10:02:49-- http://10.147.43.131/latest/public-keys Connecting to 10.147.43.131:80... failed: Connection refused. -- 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-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n
prashant kumar mishra created CLOUDSTACK-2954: - Summary: Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class Key: CLOUDSTACK-2954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2954 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: prashant kumar mishra Priority: Minor Fix For: 4.2.0 MS log is full of this message Log - 2013-06-12 11:28:24,137 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:null) Async job-161 completed 2013-06-12 11:28:24,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031453325 2013-06-12 11:28:25,881 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963 2013-06-12 11:28:25,892 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-23:null) Object entity uuid = undefined does not exist in the database. 2013-06-12 11:28:25,892 INFO [cloud.api.ApiServer] (catalina-exec-23:null) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class. 2013-06-12 11:28:25,894 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null) ===END=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963 2013-06-12 11:28:26,107 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===START=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315 2013-06-12 11:28:26,126 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-25:null) Async job-159 completed 2013-06-12 11:28:26,134 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315 2013-06-12 11:28:27,076 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198 2013-06-12 11:28:27,086 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null) Object entity uuid = undefined does not exist in the database. 2013-06-12 11:28:27,086 INFO [cloud.api.ApiServer] (catalina-exec-10:null) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class. 2013-06-12 11:28:27,088 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===END=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198 2013-06-12 11:28:27,118 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===START=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327 2013-06-12 11:28:27,138 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:null) Async job-161 completed 2013-06-12 11:28:27,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327 2013-06-12 11:28:28,217 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031457321 2013-06-12 11:28:28,226 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-20:null) Object entity uuid = undefined does not exist in the database. 2013-06-12 11:28:28,227 INFO [cloud.api.ApiServer] (catalina-exec-20:null) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class. -- This message is
[jira] [Updated] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2954: -- Attachment: DB_Logs.rar Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class - Key: CLOUDSTACK-2954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2954 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: prashant kumar mishra Priority: Minor Fix For: 4.2.0 Attachments: DB_Logs.rar MS log is full of this message Log - 2013-06-12 11:28:24,137 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:null) Async job-161 completed 2013-06-12 11:28:24,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031453325 2013-06-12 11:28:25,881 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963 2013-06-12 11:28:25,892 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-23:null) Object entity uuid = undefined does not exist in the database. 2013-06-12 11:28:25,892 INFO [cloud.api.ApiServer] (catalina-exec-23:null) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class. 2013-06-12 11:28:25,894 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null) ===END=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963 2013-06-12 11:28:26,107 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===START=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315 2013-06-12 11:28:26,126 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-25:null) Async job-159 completed 2013-06-12 11:28:26,134 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315 2013-06-12 11:28:27,076 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198 2013-06-12 11:28:27,086 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null) Object entity uuid = undefined does not exist in the database. 2013-06-12 11:28:27,086 INFO [cloud.api.ApiServer] (catalina-exec-10:null) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or due to incorrect parameter annotation for the field in api cmd class. 2013-06-12 11:28:27,088 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===END=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198 2013-06-12 11:28:27,118 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===START=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327 2013-06-12 11:28:27,138 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:null) Async job-161 completed 2013-06-12 11:28:27,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===END=== 10.252.192.7 -- GET command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327 2013-06-12 11:28:28,217 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) ===START=== 10.252.192.33 -- GET command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031457321
[jira] [Updated] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-2954:
--
Description:
MS log is full of this message
API
--
--
http://10.147.*.*:8080/client/api?command=queryAsyncJobResultjobId=undefinedresponse=json
sessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031697935
response
{ queryasyncjobresultresponse :
{uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to
execute API command queryasyncjobresult due to invalid value. Invalid parameter
jobid value=undefined due to incorrect long value format, or entity does not
exist or due to incorrect parameter annotation for the field in api cmd
class.} }
Log
-
2013-06-12 11:28:24,137 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) Async job-161 completed
2013-06-12 11:28:24,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031453325
2013-06-12 11:28:25,881 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:25,892 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-23:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 11:28:25,892 INFO [cloud.api.ApiServer] (catalina-exec-23:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
2013-06-12 11:28:25,894 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031452963
2013-06-12 11:28:26,107 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:26,126 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-25:null) Async job-159 completed
2013-06-12 11:28:26,134 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=9f87d724-0204-45a4-8dc4-979c28a00d2bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031455315
2013-06-12 11:28:27,076 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,086 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 11:28:27,086 INFO [cloud.api.ApiServer] (catalina-exec-10:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
2013-06-12 11:28:27,088 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031456198
2013-06-12 11:28:27,118 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327
2013-06-12 11:28:27,138 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-12:null) Async job-161 completed
2013-06-12 11:28:27,145 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=c8dd04a1-8bac-4066-94bb-44c112f5f62bresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3D_=1371031456327
2013-06-12 11:28:28,217 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371031457321
2013-06-12 11:28:28,226 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-20:null)
Object entity uuid = undefined does not exist in the database.
2013-06-12 11:28:28,227 INFO [cloud.api.ApiServer] (catalina-exec-20:null)
Unable to execute API command queryasyncjobresult due to invalid value. Invalid
parameter jobid value=undefined due to incorrect long value format, or entity
does not exist or due to incorrect parameter annotation for the field in api
cmd class.
[jira] [Created] (CLOUDSTACK-2955) [PortableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API
venkata swamybabu budumuru created CLOUDSTACK-2955:
--
Summary: [PortableIPrange][UI] deletePortableIpRange fails because
of UI firing an incorrect API
Key: CLOUDSTACK-2955
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2955
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
Reporter: venkata swamybabu budumuru
Assignee: Brian Federle
Steps to reproduce :
1. Have latest CS installation with at least 1 advanced zone
2. createPortableIpRange with at least 1 range
3. Try to deletePortableIpRange which was just added in previous step
Observations:
(i) deletePortablIpRange fails with the following error.
Here is the firebug snippet
_ 1371032217698
command deletePortableIpRange
responsejson
sessionkey 62Rxynqub3NPvpxcfpUlvhj+1aE=
{ deleteportablepublicipresponse :
{uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to
execute API command deleteportablepublicip due to missing parameter id} }
(ii) Above API didn't send the parameter id hence it failed in this case.
Attaching all the logs along with db dump to the bug.
--
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-1372) nTier Apps 2.0 : Support Cisco ASA as external firewall provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-1372: Fix Version/s: (was: 4.2.0) Future nTier Apps 2.0 : Support Cisco ASA as external firewall provider Key: CLOUDSTACK-1372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1372 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.1.0 Reporter: Jayapal Reddy Assignee: Koushik Das Fix For: Future Supporting external physical device cisco ASA as firewall device for nTier Apps 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-1372) nTier Apps 2.0 : Support Cisco ASA as external firewall provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681085#comment-13681085 ] Koushik Das commented on CLOUDSTACK-1372: - ASA is not supported for nTier in 4.2, so moving out nTier Apps 2.0 : Support Cisco ASA as external firewall provider Key: CLOUDSTACK-1372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1372 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.1.0 Reporter: Jayapal Reddy Assignee: Koushik Das Fix For: 4.2.0 Supporting external physical device cisco ASA as firewall device for nTier Apps 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-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681088#comment-13681088
]
Ram Ganesh commented on CLOUDSTACK-2385:
Kiran
Can you please attach the entire mgmt log files for further investigation
template download fails with Unexpected failure in Vmware.
--
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:PrepareExtractTemplate: Failed
to create OVA for template extraction
and in the management server log below are the error messages observed.
2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:21e135aa-4df9-4818-b89c-99c64de5ee70,sessionkey:xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d,ctxUserId:2,zoneid:58e1ce4d-fb5c-48c4-948f-408c969deae0,httpmethod:GET,_:1367993227024,ctxAccountId:2,ctxStartEventId:322,mode:HTTP_DOWNLOAD},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
(Job-Executor-26:job-78) Failed to create OVA for template
Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
non-existing.
2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate:
Failed to create OVA for template extraction.
at
com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
at
com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-08 17:03:14,907 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Complete async job-78, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: PrepareExtractTemplate: Failed to
create OVA for template extraction.
2013-05-08 17:03:16,752 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-18:null) Ping from 5
2013-05-08 17:03:17,262 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-198:null) Ping from 1
2013-05-08 17:03:17,884 DEBUG [cloud.api.ApiServlet]
[jira] [Commented] (CLOUDSTACK-2947) NPE while creating template
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681086#comment-13681086
]
Srikanteswararao Talluri commented on CLOUDSTACK-2947:
--
this is happening when we have a mixture of cluster scoped and zone scoped
primary storage. I did not observe this issue on a deployment where only zone
wide primary storage is available
NPE while creating template
---
Key: CLOUDSTACK-2947
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2947
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Environment: advanced zone
Reporter: Srikanteswararao Talluri
Assignee: edison su
Priority: Blocker
Fix For: 4.2.0
NPE while creating template
===START=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,111 DEBUG [cloud.api.ApiDispatcher]
(catalina-exec-5:null) Object entity uuid = undefined does not exist in the
database.
2013-06-12 10:37:02,111 INFO [cloud.api.ApiServer] (catalina-exec-5:null)
Unable to execute API command queryasyncjobresult due to invalid value.
Invalid parameter jobid value=undefined due to incorrect long value format,
or entity does not exist or due to incorrect parameter annotation for the
field in api cmd class.
2013-06-12 10:37:02,114 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.33 -- GET
command=queryAsyncJobResultjobId=undefinedresponse=jsonsessionkey=%2BuRMVVnN2JBVe6oDv%2B0ZAqV8gso%3D_=1371028371208
2013-06-12 10:37:02,283 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-140, details: AsyncJobVO {id:140,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
cmdOriginator: null, cmdInfo:
{sessionkey:78yZ9E1cc1DcOk9TqRoqnU2ycyU\u003d,ctxUserId:2,httpmethod:GET,osTypeId:d59bb3b2-cdf8-11e2-8fc8-06f1ac77,isPublic:true,response:json,id:206,displayText:td,snapshotid:3528aa5d-ddfe-4527-8887-2b1047c61e53,passwordEnabled:false,name:td,_:1371028371311,ctxAccountId:2,ctxStartEventId:579},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 10:37:02,286 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===END=== 10.252.192.7 -- GET
command=createTemplateresponse=jsonsessionkey=78yZ9E1cc1DcOk9TqRoqnU2ycyU%3Dsnapshotid=3528aa5d-ddfe-4527-8887-2b1047c61e53name=tddisplayText=tdosTypeId=d59bb3b2-cdf8-11e2-8fc8-06f1ac77isPublic=truepasswordEnabled=false_=1371028371311
2013-06-12 10:37:02,289 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-140
2013-06-12 10:37:02,403 DEBUG [cloud.template.TemplateManagerImpl]
(Job-Executor-27:job-140) Failed to create
templatejava.lang.NullPointerException
2013-06-12 10:37:02,426 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to create
templatejava.lang.NullPointerException
at
com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1770)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:256)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 10:37:02,433 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-27:job-140) Complete
[jira] [Updated] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-2385:
-
Attachment: management-server.zip
template download fails with Unexpected failure in Vmware.
--
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:PrepareExtractTemplate: Failed
to create OVA for template extraction
and in the management server log below are the error messages observed.
2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:21e135aa-4df9-4818-b89c-99c64de5ee70,sessionkey:xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d,ctxUserId:2,zoneid:58e1ce4d-fb5c-48c4-948f-408c969deae0,httpmethod:GET,_:1367993227024,ctxAccountId:2,ctxStartEventId:322,mode:HTTP_DOWNLOAD},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
(Job-Executor-26:job-78) Failed to create OVA for template
Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
non-existing.
2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate:
Failed to create OVA for template extraction.
at
com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
at
com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-08 17:03:14,907 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Complete async job-78, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: PrepareExtractTemplate: Failed to
create OVA for template extraction.
2013-05-08 17:03:16,752 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-18:null) Ping from 5
2013-05-08 17:03:17,262 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-198:null) Ping from 1
2013-05-08 17:03:17,884 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===START=== 10.146.0.136 -- GET
[jira] [Commented] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681099#comment-13681099
]
Kiran Koneti commented on CLOUDSTACK-2385:
--
HI RamG,
I have uploaded the Management server log.
Regards,
Kiran.
template download fails with Unexpected failure in Vmware.
--
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:PrepareExtractTemplate: Failed
to create OVA for template extraction
and in the management server log below are the error messages observed.
2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:21e135aa-4df9-4818-b89c-99c64de5ee70,sessionkey:xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d,ctxUserId:2,zoneid:58e1ce4d-fb5c-48c4-948f-408c969deae0,httpmethod:GET,_:1367993227024,ctxAccountId:2,ctxStartEventId:322,mode:HTTP_DOWNLOAD},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
(Job-Executor-26:job-78) Failed to create OVA for template
Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
non-existing.
2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate:
Failed to create OVA for template extraction.
at
com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
at
com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-05-08 17:03:14,907 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Complete async job-78, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: PrepareExtractTemplate: Failed to
create OVA for template extraction.
2013-05-08 17:03:16,752 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-18:null) Ping from 5
2013-05-08 17:03:17,262 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-198:null) Ping from 1
2013-05-08
[jira] [Created] (CLOUDSTACK-2956) listStoragePools API is returning cluster details for zone scoped primary storage
Srikanteswararao Talluri created CLOUDSTACK-2956: Summary: listStoragePools API is returning cluster details for zone scoped primary storage Key: CLOUDSTACK-2956 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2956 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Srikanteswararao Talluri Priority: Critical Fix For: 4.2.0 1. While deploying a zone using zone create wizard and add a zone scoped primary storage. 2. Invoke listStoragePools API. It is listing cluster details for zone scoped primary storage which doesn't make sense. This is happening when createStoragePool API is invoked by providing clustered= and podId= command=createStoragePoolzoneid=223c3687-f561-4b16-9584-2e1266c303b1podId=fd70cc91-07ee-4c5e-92ff-3090911653a8clusterid=ce410600-35c3-4e69-af4e-972b61bd9259name=primscope=zonehypervisor=VMwareurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Ftalluri%2Fmysetup_primresponse=jsonsessionkey=vQryK5i4jo4Lm%2BLJ%2F3gHgGQzneg%3D_=1371030846595 liststoragepoolsresponse cloud-stack-version=4.2.0-SNAPSHOT count3/count storagepool id98a13fa4-5768-3a67-b6ed-6c06e609a4dc/id zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid zonenamezwpszone/zonename zonetypeAdvanced/zonetype podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid podnamepod/podname nameprim3/name ipaddress10.147.28.7/ipaddress path/export/home/talluri/mysetup_prim3/path created2013-06-12T21:44:10+0530/created typeNetworkFilesystem/type clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid clustername10.147.60.15/stormig/stormig_clus/clustername disksizetotal590228480/disksizetotal disksizeallocated0/disksizeallocated disksizeused3281502081024/disksizeused stateUp/state scopeZONE/scope hypervisorVMware/hypervisor /storagepool storagepool idece502dc-5d06-3043-afec-38e3d54fe995/id zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid zonenamezwpszone/zonename zonetypeAdvanced/zonetype nameprim2/name ipaddress10.147.28.7/ipaddress path/export/home/talluri/mysetup_prim2/path created2013-06-12T21:23:13+0530/created typeNetworkFilesystem/type disksizetotal590228480/disksizetotal disksizeallocated0/disksizeallocated disksizeused3281155739648/disksizeused stateUp/state scopeZONE/scope hypervisorVMware/hypervisor /storagepool storagepool id5a830e2f-3b1e-32fd-bdde-a418fba453a2/id zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid zonenamezwpszone/zonename zonetypeAdvanced/zonetype podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid podnamepod/podname nameprim/name ipaddress10.147.28.7/ipaddress path/export/home/talluri/mysetup_prim/path created2013-06-12T20:49:33+0530/created typeNetworkFilesystem/type clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid clustername10.147.60.15/stormig/stormig_clus/clustername disksizetotal590228480/disksizetotal disksizeallocated8489271296/disksizeallocated disksizeused3280631812096/disksizeused stateUp/state scopeZONE/scope hypervisorVMware/hypervisor /storagepool /liststoragepoolsresponse -- 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-2957) deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume
Nitin Mehta created CLOUDSTACK-2957: --- Summary: deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume Key: CLOUDSTACK-2957 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2957 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta 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-2958) [ZWPS][VMWARE]: NPE while attaching a volume to a VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681116#comment-13681116
]
Srikanteswararao Talluri commented on CLOUDSTACK-2958:
--
liststoragepoolsresponse cloud-stack-version=4.2.0-SNAPSHOT
count3/count
storagepool
id98a13fa4-5768-3a67-b6ed-6c06e609a4dc/id
zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
zonenamezwpszone/zonename
zonetypeAdvanced/zonetype
podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
podnamepod/podname
nameprim3/name
ipaddress10.147.28.7/ipaddress
path/export/home/talluri/mysetup_prim3/path
created2013-06-12T21:44:10+0530/created
typeNetworkFilesystem/type
clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
clustername10.147.60.15/stormig/stormig_clus/clustername
disksizetotal590228480/disksizetotal
disksizeallocated0/disksizeallocated
disksizeused3281502081024/disksizeused
stateUp/state
scopeZONE/scope
hypervisorVMware/hypervisor
/storagepool
storagepool
idece502dc-5d06-3043-afec-38e3d54fe995/id
zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
zonenamezwpszone/zonename
zonetypeAdvanced/zonetype
nameprim2/name
ipaddress10.147.28.7/ipaddress
path/export/home/talluri/mysetup_prim2/path
created2013-06-12T21:23:13+0530/created
typeNetworkFilesystem/type
disksizetotal590228480/disksizetotal
disksizeallocated0/disksizeallocated
disksizeused3281155739648/disksizeused
stateUp/state
scopeZONE/scope
hypervisorVMware/hypervisor
/storagepool
storagepool
id5a830e2f-3b1e-32fd-bdde-a418fba453a2/id
zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
zonenamezwpszone/zonename
zonetypeAdvanced/zonetype
podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
podnamepod/podname
nameprim/name
ipaddress10.147.28.7/ipaddress
path/export/home/talluri/mysetup_prim/path
created2013-06-12T20:49:33+0530/created
typeNetworkFilesystem/type
clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
clustername10.147.60.15/stormig/stormig_clus/clustername
disksizetotal590228480/disksizetotal
disksizeallocated8489271296/disksizeallocated
disksizeused3280631812096/disksizeused
stateUp/state
scopeZONE/scope
hypervisorVMware/hypervisor
/storagepool
/liststoragepoolsresponse
[ZWPS][VMWARE]: NPE while attaching a volume to a VM
Key: CLOUDSTACK-2958
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2958
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.2.0
1. Deploy a vmware zone with zone wide primary storage
2. create an Instance
3. Take snaphot of the root volume
4. create volume from snapshot
5. attach the volume created in step 4 to the vm created in step 2.
NOTE: Zone has multiple zone wide primary storages
===START=== 10.252.192.7 -- GET
command=attachVolumeid=214ee1ea-1b05-4e05-b967-8db48b318dcavirtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7response=jsonsessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D_=1371034570223
2013-06-12 21:51:37,493 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-20, details: AsyncJobVO {id:20,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
7, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:214ee1ea-1b05-4e05-b967-8db48b318dca,sessionkey:5ez1jBXiPUJzcam0/t9UtTy9L+Y\u003d,ctxUserId:2,virtualMachineId:7092ef40-8aef-40fa-a3a0-8ae2443109a7,httpmethod:GET,_:1371034570223,ctxAccountId:2,ctxStartEventId:78},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 21:51:37,497 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=attachVolumeid=214ee1ea-1b05-4e05-b967-8db48b318dcavirtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7response=jsonsessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D_=1371034570223
2013-06-12 21:51:37,500 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-20) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-20
2013-06-12 21:51:37,610 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-20) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1502)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1741)
at
[jira] [Created] (CLOUDSTACK-2958) [ZWPS][VMWARE]: NPE while attaching a volume to a VM
Srikanteswararao Talluri created CLOUDSTACK-2958:
Summary: [ZWPS][VMWARE]: NPE while attaching a volume to a VM
Key: CLOUDSTACK-2958
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2958
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.2.0
1. Deploy a vmware zone with zone wide primary storage
2. create an Instance
3. Take snaphot of the root volume
4. create volume from snapshot
5. attach the volume created in step 4 to the vm created in step 2.
NOTE: Zone has multiple zone wide primary storages
===START=== 10.252.192.7 -- GET
command=attachVolumeid=214ee1ea-1b05-4e05-b967-8db48b318dcavirtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7response=jsonsessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D_=1371034570223
2013-06-12 21:51:37,493 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-11:null) submit async job-20, details: AsyncJobVO {id:20,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 7,
cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:214ee1ea-1b05-4e05-b967-8db48b318dca,sessionkey:5ez1jBXiPUJzcam0/t9UtTy9L+Y\u003d,ctxUserId:2,virtualMachineId:7092ef40-8aef-40fa-a3a0-8ae2443109a7,httpmethod:GET,_:1371034570223,ctxAccountId:2,ctxStartEventId:78},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 21:51:37,497 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null)
===END=== 10.252.192.7 -- GET
command=attachVolumeid=214ee1ea-1b05-4e05-b967-8db48b318dcavirtualMachineId=7092ef40-8aef-40fa-a3a0-8ae2443109a7response=jsonsessionkey=5ez1jBXiPUJzcam0%2Ft9UtTy9L%2BY%3D_=1371034570223
2013-06-12 21:51:37,500 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-20) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-20
2013-06-12 21:51:37,610 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-20) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1502)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1741)
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:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 21:51:37,612 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-20) Complete async job-20, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: null
2013-06-12 21:51:39,145 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 1 routers to update status.
--
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-2905) Recurring Snapshots are failing becuase of NullPointerException.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala reassigned CLOUDSTACK-2905: -- Assignee: Rajesh Battala Recurring Snapshots are failing becuase of NullPointerException. Key: CLOUDSTACK-2905 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2905 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: cloudstack-management-4.1.0-0.el6.x86_64 Reporter: satoru nakaya Assignee: Rajesh Battala Priority: Blocker Fix For: 4.1.1 Create an Hourly Recurring snapshot policy on the ROOT disk. Snapshot policy gets created successfully. But when it is time to create a snapshot, snapshot scheduler thread encounters a NullPointer Exception: Management server logs: # tail -f management-server.log | grep SnapshotSchedulerImpl 2013-06-08 08:06:11,393 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2013-06-07 23:06:11 GMT 2013-06-08 08:06:11,395 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Got 0 snapshots to be executed at 2013-06-07 23:06:11 GMT 2013-06-08 08:08:39,459 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (catalina-exec-4:null) Current time is 2013-06-07 23:06:11 GMT. NextScheduledTime of policyId 1 is 2013-06-07 23:10:00 GMT 2013-06-08 08:11:11,393 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2013-06-07 23:11:11 GMT 2013-06-08 08:11:11,397 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Got 1 snapshots to be executed at 2013-06-07 23:11:11 GMT 2013-06-08 08:11:11,400 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Scheduling 1 snapshot for volume 3 for schedule id: 1 at 2013-06-07 23:10:00 GMT 2013-06-08 08:11:11,453 WARN [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Scheduling snapshot failed due to java.lang.NullPointerException -- 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-2943) [ZWPS][VMWARE]: NPE while creating volume from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi reassigned CLOUDSTACK-2943:
Assignee: Sateesh Chodapuneedi
[ZWPS][VMWARE]: NPE while creating volume from snapshot
---
Key: CLOUDSTACK-2943
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2943
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Sateesh Chodapuneedi
Priority: Blocker
Fix For: 4.2.0
1. create a snapshot created from a disk on zone scoped primary storage
2. create a volume from the snapshot created in step1.
===START=== 10.252.192.7 -- GET
command=createVolumeresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3Dsnapshotid=2112f1f0-9fc0-42f5-bde9-900dffeab7dfname=zwpsvol_=1371021830999
2013-06-12 08:48:01,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-18:null) submit async job-133, details: AsyncJobVO {id:133,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
28, cmd: org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:28,response:json,sessionkey:WibLOc01S7zuDtvZAhmKpsaufLY\u003d,ctxUserId:2,snapshotid:2112f1f0-9fc0-42f5-bde9-900dffeab7df,name:zwpsvol,httpmethod:GET,_:1371021830999,ctxAccountId:2,ctxStartEventId:553},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7635042566263,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-06-12 08:48:01,876 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null)
===END=== 10.252.192.7 -- GET
command=createVolumeresponse=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3Dsnapshotid=2112f1f0-9fc0-42f5-bde9-900dffeab7dfname=zwpsvol_=1371021830999
2013-06-12 08:48:01,879 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-20:job-133) Executing
org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-133
2013-06-12 08:48:01,882 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===START=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=0551e5bd-8be0-4ffe-91e5-1a9e65e41284response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371021831100
2013-06-12 08:48:01,941 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.192.7 -- GET
command=queryAsyncJobResultjobId=0551e5bd-8be0-4ffe-91e5-1a9e65e41284response=jsonsessionkey=WibLOc01S7zuDtvZAhmKpsaufLY%3D_=1371021831100
2013-06-12 08:48:01,987 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: primary
2013-06-12 08:48:01,997 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: primary2
2013-06-12 08:48:02,004 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Storage pool garbage collector found 0 templates to
clean up in storage pool: talluri_zonewide
2013-06-12 08:48:02,011 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-20:job-133) Secondary storage garbage collector found 0
templates to cleanup on secondary storage host:
nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware
2013-06-12 08:48:02,028 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184073: Sending { Cmd , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 100011,
[{CleanupSnapshotBackupCommand:{secondaryStoragePoolURL:nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware,dcId:1,accountId:2,volumeId:19,validBackupUUIDs:[cd638b62-94c5-4c32-a3b6-f684ae95e20f/cd638b62-94c5-4c32-a3b6-f684ae95e20f],wait:0}}]
}
2013-06-12 08:48:02,183 DEBUG [agent.transport.Request]
(AgentManager-Handler-10:null) Seq 3-1245184073: Processing: { Ans: ,
MgmtId: 7635042566263, via: 3, Ver: v1, Flags: 10,
[{Answer:{result:true,wait:0}}] }
2013-06-12 08:48:02,184 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184073: Received: { Ans: , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 10, { Answer } }
2013-06-12 08:48:02,197 DEBUG [agent.transport.Request]
(Job-Executor-20:job-133) Seq 3-1245184074: Sending { Cmd , MgmtId:
7635042566263, via: 3, Ver: v1, Flags: 100011,
[{CleanupSnapshotBackupCommand:{secondaryStoragePoolURL:nfs://10.147.28.7/export/home/prashant/secondary.4.2.vmware,dcId:1,accountId:2,volumeId:26,validBackupUUIDs:[f0c770b2-adf1-4116-95b6-3e3b2f1a6aae/f0c770b2-adf1-4116-95b6-3e3b2f1a6aae],wait:0}}]
}
2013-06-12 08:48:02,279 DEBUG
[jira] [Created] (CLOUDSTACK-2959) [PortableIPrange] it is good show ip ranges rather individual ip list as part of listPortableIpRanges response
venkata swamybabu budumuru created CLOUDSTACK-2959: -- Summary: [PortableIPrange] it is good show ip ranges rather individual ip list as part of listPortableIpRanges response Key: CLOUDSTACK-2959 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2959 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Steps to reproduce: 1. Have the latest CloudStack setup with at least 1 region and 1 advanced zone. 2. create the following portable IP range start ip : 10.147.54.100 end ip : 10.147.54.103 vlan : 54 netmask : 10.147.54.1 3. fire listPortableIpRange and check for the response. Observations : (i) currently listPortableIpRanges shows both ranges as well as each individual IP and it makes it little difficult to quickly find out the ip ranges. (ii) it will be good to show only ip ranges if there is no special requirement for listing out all the individual ips. even if it is required then adding another flag as param will make the response simple. Here is the snippet of listPortableIpRanges response: count = 2 portableiprange: id = 6bddb4af-97f3-416e-b64a-0c023987 endip = 10.147.54.102 gateway = 10.147.54.1 netmask = 255.255.255.0 portableipaddress: ipaddress = 10.147.54.100 state = Free ipaddress = 10.147.54.101 state = Free ipaddress = 10.147.54.102 state = Free regionid = 1 startip = 10.147.54.100 vlan = 54 Attaching all the required logs along with db dump to the bug. -- 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-2573) [Zone-Wide-PrimaryStorage] SystemVMs are not coming up using zone wide primary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-2573: - Assignee: Sateesh Chodapuneedi [Zone-Wide-PrimaryStorage] SystemVMs are not coming up using zone wide primary storage -- Key: CLOUDSTACK-2573 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2573 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Environment: commit # 85d54cd1c088997dd08f0328984bee1a55703636 Reporter: venkata swamybabu budumuru Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.2.0 Attachments: logs.tgz Steps to reproduce : 1. Have a CloudStack setup with at least 1 advanced zone. 2. Deploy advanced zone with default which brings up the primary storage with scope set to Cluster 3. Disable the zone 4. Remove the primary storage. 5. add primary storage with scope set to Zone. 6. Enable Zone Observations: (i) CloudStack didnt kick in for system vm bring up. Here is the snippet from mgmt server log. 2013-05-20 08:45:58,347 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM 2013-05-20 08:45:58,372 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Primary storage is not ready, wait until it is ready to launch secondary storage vm. dcId: 2 system.vm.use.local.storage: falseIf you want to use local storage to start ssvm, need to set system.vm.use.local.storage to true 2013-05-20 08:45:58,372 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is not ready to launch secondary storage VM yet 2013-05-20 08:45:58,807 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy 2013-05-20 08:45:58,817 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Primary storage is not ready, wait until it is ready to launch console proxy 2013-05-20 08:45:58,817 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is not ready to launch console proxy yet 2013-05-20 08:46:02,447 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-21:null) Ping from 1 Here is the db snippet for the same *** 4. row *** id: 5 name: primaryZone2 uuid: b5671f5d-c64c-36e7-9249-6d87010c7bac pool_type: NetworkFilesystem port: 2049 data_center_id: 2 pod_id: NULL cluster_id: NULL available_bytes: 0 capacity_bytes: 0 host_address: 10.147.28.7 user_info: NULL path: /export/home/swamy/primary.campo.vmw.1 created: 2013-05-20 12:21:08 removed: NULL update_time: NULL status: Up storage_provider_name: ancient primary data store provider scope: ZONE 4 rows in set (0.00 sec) Attaching all the required logs to the bug along with db dump -- 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-2711) UpdateDefaultNicForVirtualMachine api is not updating default nic on VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava reassigned CLOUDSTACK-2711: -- Assignee: Saksham Srivastava UpdateDefaultNicForVirtualMachine api is not updating default nic on VM --- Key: CLOUDSTACK-2711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2711 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: build: CloudStack-non-OSS-MASTER-410-rhel6.3 Reporter: shweta agarwal Assignee: Saksham Srivastava Priority: Blocker Fix For: 4.2.0 Repro steps: 1.Create a VM 2. Create a Network 3.Add this Network to VM 4. Reboot the VM inorder to reflect the changes of new nic 5.Make the newly added nic as Default nic 6. Reboot the VM Bug: Even after rebooting the VM ;it shows old Default Nic as default one Expected Result: After VM reboots , Default nic should be updated My sql shows Default nic for a vm as id uuid instance_id mac_address ip4_address netmask gateway ip_type broadcast_uri network_idmode state reserver_name reservation_iddevice_id update_time isolation_uri ip6_address default_nic vm_type created removed ip6_gateway ip6_cidr secondary_ip display_nic 40 cd8deae5-ebc4-45ba-998b-5e14afe39d01 3 02:00:6b:dc:00:01 10.1.4.98 255.255.255.0 10.1.4.1 Ip4 vlan://1041 208 Dhcp Reserved ExternalGuestNetworkGuru0 2013-05-28 10:02:57 vlan://1041 1 User 2013-05-28 11:30:54 0 1 VM entries for ip route show 10.1.4.0/24 dev eth1 proto kernel scope link src 10.1.4.98 10.1.5.0/24 dev eth2 proto kernel scope link src 10.1.5.49 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.47 169.254.0.0/16 dev eth2 scope link default via 10.1.1.1 dev eth0 -- 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] [Issue Comment Deleted] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-2385:
-
Comment: was deleted
(was: After this I released the dedicated zone from the subdomain 1 and tried
to dedicate it to the subdomain 2 then observed the below error message:
2013-06-12 22:04:59,701 INFO
[cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-35:job-49)
Host 1 found to be unsuitable for explicit dedication as it is running
instances of another domain
2013-06-12 22:04:59,703 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-35:job-49) Unexpected exception while executing
org.apache.cloudstack.api.commands.DedicateZoneCmd
com.cloud.utils.exception.CloudRuntimeException: Host 1 found to be unsuitable
for explicit dedication as it is running instances of another domain
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:575)
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostsSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:586)
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicateZone(DedicatedResourceManagerImpl.java:211)
at
org.apache.cloudstack.api.commands.DedicateZoneCmd.execute(DedicateZoneCmd.java:95)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 22:04:59,704 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-35:job-49) Complete async job-49, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: Host 1 found to be unsuitable for explicit
dedication as it is running instances of another domain
And when it tried to dedicate it to the Root domain there are no exceptions
seen.)
template download fails with Unexpected failure in Vmware.
--
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:PrepareExtractTemplate: Failed
to create OVA for template extraction
and in the management server log below are the error messages observed.
2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:21e135aa-4df9-4818-b89c-99c64de5ee70,sessionkey:xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d,ctxUserId:2,zoneid:58e1ce4d-fb5c-48c4-948f-408c969deae0,httpmethod:GET,_:1367993227024,ctxAccountId:2,ctxStartEventId:322,mode:HTTP_DOWNLOAD},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
2013-05-08 17:03:14,894 DEBUG
[jira] [Commented] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681123#comment-13681123
]
Kiran Koneti commented on CLOUDSTACK-2385:
--
After this I released the dedicated zone from the subdomain 1 and tried to
dedicate it to the subdomain 2 then observed the below error message:
2013-06-12 22:04:59,701 INFO
[cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-35:job-49)
Host 1 found to be unsuitable for explicit dedication as it is running
instances of another domain
2013-06-12 22:04:59,703 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-35:job-49) Unexpected exception while executing
org.apache.cloudstack.api.commands.DedicateZoneCmd
com.cloud.utils.exception.CloudRuntimeException: Host 1 found to be unsuitable
for explicit dedication as it is running instances of another domain
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:575)
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostsSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:586)
at
org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicateZone(DedicatedResourceManagerImpl.java:211)
at
org.apache.cloudstack.api.commands.DedicateZoneCmd.execute(DedicateZoneCmd.java:95)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-06-12 22:04:59,704 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-35:job-49) Complete async job-49, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: Host 1 found to be unsuitable for explicit
dedication as it is running instances of another domain
And when it tried to dedicate it to the Root domain there are no exceptions
seen.
template download fails with Unexpected failure in Vmware.
--
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.zip
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:PrepareExtractTemplate: Failed
to create OVA for template extraction
and in the management server log below are the error messages observed.
2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78,
userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
instanceId: 206, cmd:
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{response:json,id:21e135aa-4df9-4818-b89c-99c64de5ee70,sessionkey:xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d,ctxUserId:2,zoneid:58e1ce4d-fb5c-48c4-948f-408c969deae0,httpmethod:GET,_:1367993227024,ctxAccountId:2,ctxStartEventId:322,mode:HTTP_DOWNLOAD},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplatemode=HTTP_DOWNLOADid=21e135aa-4df9-4818-b89c-99c64de5ee70zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0response=jsonsessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
[jira] [Created] (CLOUDSTACK-2960) [portableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API
venkata swamybabu budumuru created CLOUDSTACK-2960: -- Summary: [portableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API Key: CLOUDSTACK-2960 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2960 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: venkata swamybabu budumuru -- 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-2304) [ZWPS]NPE while migrating volume from one zone wide primary to another
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala reassigned CLOUDSTACK-2304:
--
Assignee: Rajesh Battala
[ZWPS]NPE while migrating volume from one zone wide primary to another
--
Key: CLOUDSTACK-2304
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2304
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.2.0
Environment: KVM/VMware deployment with Zone wide primary storage
Reporter: Srikanteswararao Talluri
Assignee: Rajesh Battala
Priority: Critical
Fix For: 4.2.0
Try to migrate a volume from one zone wide primary storage to another.
===START=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,384 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-3:null) submit async job-97, details: AsyncJobVO {id:97,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId:
null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd,
cmdOriginator: null, cmdInfo:
{response:json,sessionkey:yMNGYR64PRQhdJaPj99Bvs2KDDE\u003d,ctxUserId:2,storageid:230ae4af-0446-3929-a8cd-63ab88f31ab1,_:1367485037836,volumeid:d9efc3d8-1612-4998-95d7-c713e90b7173,ctxAccountId:2,ctxStartEventId:310},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-02 20:06:59,388 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.252.241.40 -- GET
command=migrateVolumestorageid=230ae4af-0446-3929-a8cd-63ab88f31ab1volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173response=jsonsessionkey=yMNGYR64PRQhdJaPj99Bvs2KDDE%3D_=1367485037836
2013-05-02 20:06:59,391 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
2013-05-02 20:06:59,423 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-66:job-97) migrate volume failed:java.lang.NullPointerException
2013-05-02 20:06:59,424 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Complete async job-97, jobStatus: 1, resultCode: 0,
result: null
2013-05-02 20:06:59,434 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-66:job-97) Done executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-97
--
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-2957) deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-2957: Description: size atribute when used with custom disk offering should be limited by storage.max.volume.size global config (default 2000 gb) as it is in createVolume but from the code seems like its not. The number is used to avoid abuse by the end user. deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume Key: CLOUDSTACK-2957 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2957 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 size atribute when used with custom disk offering should be limited by storage.max.volume.size global config (default 2000 gb) as it is in createVolume but from the code seems like its not. The number is used to avoid abuse by the end user. -- 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-2960) [portableIPrange] CS should check the portable ip range, vlan with existing public ip ranges and clans
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-2960: --- Component/s: Network Controller Fix Version/s: 4.2.0 Assignee: Murali Reddy Description: Steps to reproduce : 1. Have latest cloudstack setup with at least one adv zone. 2. Have the following public ip range already added start ip : 10.147.44.80 end ip : 10.147.44.89 gw : 10.147.44.1 mask : 255.255.255.0 VLAN : 44 3. Add the same above range including vlan to the portable ip range Observations: (i) This goes fine without any issues. (ii) Allowing the above will create issue when user tries to have the same ip from public ip range and portable ip range on the same router. Attaching all the required logs and db dump to the bug. Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4 Affects Version/s: 4.2.0 Summary: [portableIPrange] CS should check the portable ip range, vlan with existing public ip ranges and clans (was: [portableIPrange][UI] deletePortableIpRange fails because of UI firing an incorrect API) [portableIPrange] CS should check the portable ip range, vlan with existing public ip ranges and clans --- Key: CLOUDSTACK-2960 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2960 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4 Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Steps to reproduce : 1. Have latest cloudstack setup with at least one adv zone. 2. Have the following public ip range already added start ip : 10.147.44.80 end ip : 10.147.44.89 gw : 10.147.44.1 mask : 255.255.255.0 VLAN : 44 3. Add the same above range including vlan to the portable ip range Observations: (i) This goes fine without any issues. (ii) Allowing the above will create issue when user tries to have the same ip from public ip range and portable ip range on the same router. Attaching all the required logs and db dump to the bug. -- 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-2957) deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681133#comment-13681133 ] ASF subversion and git services commented on CLOUDSTACK-2957: - Commit 2aafc39f3d0570fac1ddcebf4623f1c37e8e47e5 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2aafc39 ] CLOUDSTACK-2957 deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume. deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume Key: CLOUDSTACK-2957 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2957 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 size atribute when used with custom disk offering should be limited by storage.max.volume.size global config (default 2000 gb) as it is in createVolume but from the code seems like its not. The number is used to avoid abuse by the end user. -- 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-2420) NPE: Attaching an Uploaded volume to a VM, (NPE while moving from
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala reassigned CLOUDSTACK-2420: -- Assignee: Rajesh Battala NPE: Attaching an Uploaded volume to a VM, (NPE while moving from -- Key: CLOUDSTACK-2420 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2420 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.2.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Fix For: 4.2.0 2013-05-09 18:36:46,997 DEBUG [cloud.api.ApiServlet] (6876027@qtp-10225875-14:null) ===END=== 10.144.7.13 -- GET command=attachVolumeid=e0075fb1-2432-4375-a22e-b7e6015afac6virtualMachineId=aa6b941d-a7ea-42da-a175-578005fcb41bresponse=jsonsessionkey=vCZWZNneQ9l2xOkDXYUoEuAluYw%3D_=1368104845639 2013-05-09 18:36:47,077 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-6:job-29) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd java.lang.NullPointerException at com.cloud.storage.VolumeManagerImpl.copyVolume(VolumeManagerImpl.java:1444) at com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1488) at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1727) 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:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2013-05-09 18:36:47,080 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-6:job-29) Complete async job-29, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null -- 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
