[jira] [Created] (CLOUDSTACK-3293) DeleteAccount fails with ConstraintViolation on snapshot_store_ref
Prasanna Santhanam created CLOUDSTACK-3293: -- Summary: DeleteAccount fails with ConstraintViolation on snapshot_store_ref Key: CLOUDSTACK-3293 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3293 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Reporter: Prasanna Santhanam Priority: Critical Fix For: 4.2.0 The following issue was encountered when deleting accounts: 2013-06-30 13:38:49,034 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ] 2013-06-30 13:38:49,036 DEBUG [cloud.api.ApiServlet] (706873057@qtp-20348362-3:null) ===END=== 127.0.0.1 -- GET signature=oO%2FgP9Ffx%2FlE%2FYIC7tXPcFfb8Pg%3D&apiKey=oN8VZaaSyTapdOEJPP29padHk23dgCof3zxoaH9rMm4V4XUpNv2EAkSTixufmjQLr-kbdwLphVC8UQnkcfdUNw&command=queryAsyncJobResult&response=json&jobid=bb4be72e-a4a1-4d1d-9ecd-f4516807990b 2013-06-30 13:38:49,043 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Removed account 28 2013-06-30 13:38:49,053 WARN [storage.snapshot.SnapshotManagerImpl] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed to delete all snapshot for volume 47 on secondary storage nfs://10.147.28.6:/export/home/sandbox/secondary 2013-06-30 13:38:49,053 ERROR [storage.snapshot.SnapshotManagerImpl] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) unsupported command:com.cloud.agent.api.DeleteSnapshotsDirCommand 2013-06-30 13:38:49,055 DEBUG [db.Transaction.Transaction] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Rolling back the transaction: Time = 1 Name = -AsyncJobManagerImpl$1.run:418-Executors$RunnableAdapter.call:439-FutureTask$Sync.innerRun:303-FutureTask.run:138-ThreadPoolExecutor$Worker.runTask:895-ThreadPoolExecutor$Worker.run:918-Thread.run:680; called by -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:682-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118 2013-06-30 13:38:49,056 WARN [cloud.user.AccountManagerImpl] (Job-Executor-72:job-142 = [ bb4be72e-a4a1-4d1d-9ecd-f4516807990b ]) Failed to cleanup account Acct[28-test-5E4I97] due to com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@3632317c: DELETE FROM snapshots WHERE snapshots.id= 3 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:682) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1255) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:177) at org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:118) at org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:100) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:455) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a forei
[jira] [Commented] (CLOUDSTACK-2813) System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696309#comment-13696309 ] ASF subversion and git services commented on CLOUDSTACK-2813: - Commit 4c0425f9189f1dce889d0f1532f7823f9381757b in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4c0425f ] CLOUDSTACK-2813 - Some deployment failures do not release the resources. Applying the short term fix of force cleaning up if the answer recieved from startcommand is not valid Signed off by : nitin mehta > System VMs not coming up due to “InsufficientServerCapacityException”.(not > consistently reproducible) > - > > Key: CLOUDSTACK-2813 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2813 > 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: manasaveloori >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Seps:t > 1.Have a CS with advanced zone . > 2.Created some user VMs. > 3.Created VPCs and VMs under VPCs. > 4.Shutdown the Host(Xen) and MS. > 5.Start the Host and MS. > Observation: > The SSVM and CPVM were not coming up with > “InsufficientServerCapacityException” exception. > The Dashboard was showing exhausted management IPs . > Deleted all the VMS ,still the IPs were not released. > Below is the table which shows that all the management ips are reserved. > mysql> select * from op_dc_ip_address_alloc; > ++---++++--+-+-+ > | id | ip_address| data_center_id | pod_id | nic_id | reservation_id > | taken | mac_address | > ++---++++--+-+-+ > | 1 | 10.147.40.181 | 1 | 1 | 34 | > 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 | 1 | > | 2 | 10.147.40.182 | 1 | 1 | 3 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 2 | > | 3 | 10.147.40.183 | 1 | 1 | 7 | > 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 | 3 | > | 4 | 10.147.40.184 | 1 | 1 | 7 | > 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 | 4 | > | 5 | 10.147.40.185 | 1 | 1 | 29 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 5 | > | 6 | 10.147.40.186 | 1 | 1 | 30 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 6 | > | 7 | 10.147.40.187 | 1 | 1 | 4 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 7 | > | 8 | 10.147.40.188 | 1 | 1 | 7 | > ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 | 8 | > | 9 | 10.147.40.189 | 1 | 1 | 7 | > 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 | 9 | > | 10 | 10.147.40.190 | 1 | 1 | 7 | > 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 | 10 | > ++---++++--+-+-+ > As all the IPs were in reserved state ,SSVM and CPVM were not coming up. > Was not able to reproduce this issue again . > Attached is the server log. -- 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-2813) System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696308#comment-13696308 ] ASF subversion and git services commented on CLOUDSTACK-2813: - Commit 6f86b6b73c8c20ad89847c9584555f6d69c4332e in branch refs/heads/master-6-17-stable from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6f86b6b ] CLOUDSTACK-2813 - Some deployment failures do not release the resources. Applying the short term fix of force cleaning up if the answer recieved from startcommand is not valid Signed off by : nitin mehta > System VMs not coming up due to “InsufficientServerCapacityException”.(not > consistently reproducible) > - > > Key: CLOUDSTACK-2813 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2813 > 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: manasaveloori >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Seps:t > 1.Have a CS with advanced zone . > 2.Created some user VMs. > 3.Created VPCs and VMs under VPCs. > 4.Shutdown the Host(Xen) and MS. > 5.Start the Host and MS. > Observation: > The SSVM and CPVM were not coming up with > “InsufficientServerCapacityException” exception. > The Dashboard was showing exhausted management IPs . > Deleted all the VMS ,still the IPs were not released. > Below is the table which shows that all the management ips are reserved. > mysql> select * from op_dc_ip_address_alloc; > ++---++++--+-+-+ > | id | ip_address| data_center_id | pod_id | nic_id | reservation_id > | taken | mac_address | > ++---++++--+-+-+ > | 1 | 10.147.40.181 | 1 | 1 | 34 | > 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 | 1 | > | 2 | 10.147.40.182 | 1 | 1 | 3 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 2 | > | 3 | 10.147.40.183 | 1 | 1 | 7 | > 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 | 3 | > | 4 | 10.147.40.184 | 1 | 1 | 7 | > 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 | 4 | > | 5 | 10.147.40.185 | 1 | 1 | 29 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 5 | > | 6 | 10.147.40.186 | 1 | 1 | 30 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 6 | > | 7 | 10.147.40.187 | 1 | 1 | 4 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 7 | > | 8 | 10.147.40.188 | 1 | 1 | 7 | > ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 | 8 | > | 9 | 10.147.40.189 | 1 | 1 | 7 | > 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 | 9 | > | 10 | 10.147.40.190 | 1 | 1 | 7 | > 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 | 10 | > ++---++++--+-+-+ > As all the IPs were in reserved state ,SSVM and CPVM were not coming up. > Was not able to reproduce this issue again . > Attached is the server log. -- 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-3294) CLONE - System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-3294: Assignee: (was: Nitin Mehta) > CLONE - System VMs not coming up due to > “InsufficientServerCapacityException”.(not consistently reproducible) > - > > Key: CLOUDSTACK-3294 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3294 > 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: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Seps:t > 1.Have a CS with advanced zone . > 2.Created some user VMs. > 3.Created VPCs and VMs under VPCs. > 4.Shutdown the Host(Xen) and MS. > 5.Start the Host and MS. > Observation: > The SSVM and CPVM were not coming up with > “InsufficientServerCapacityException” exception. > The Dashboard was showing exhausted management IPs . > Deleted all the VMS ,still the IPs were not released. > Below is the table which shows that all the management ips are reserved. > mysql> select * from op_dc_ip_address_alloc; > ++---++++--+-+-+ > | id | ip_address| data_center_id | pod_id | nic_id | reservation_id > | taken | mac_address | > ++---++++--+-+-+ > | 1 | 10.147.40.181 | 1 | 1 | 34 | > 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 | 1 | > | 2 | 10.147.40.182 | 1 | 1 | 3 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 2 | > | 3 | 10.147.40.183 | 1 | 1 | 7 | > 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 | 3 | > | 4 | 10.147.40.184 | 1 | 1 | 7 | > 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 | 4 | > | 5 | 10.147.40.185 | 1 | 1 | 29 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 5 | > | 6 | 10.147.40.186 | 1 | 1 | 30 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 6 | > | 7 | 10.147.40.187 | 1 | 1 | 4 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 7 | > | 8 | 10.147.40.188 | 1 | 1 | 7 | > ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 | 8 | > | 9 | 10.147.40.189 | 1 | 1 | 7 | > 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 | 9 | > | 10 | 10.147.40.190 | 1 | 1 | 7 | > 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 | 10 | > ++---++++--+-+-+ > As all the IPs were in reserved state ,SSVM and CPVM were not coming up. > Was not able to reproduce this issue again . > Attached is the server log. -- 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-3294) CLONE - System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)
Nitin Mehta created CLOUDSTACK-3294: --- Summary: CLONE - System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible) Key: CLOUDSTACK-3294 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3294 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: Nitin Mehta Assignee: Nitin Mehta Priority: Critical Fix For: 4.2.0 Attachments: management-server.zip Seps:t 1. Have a CS with advanced zone . 2. Created some user VMs. 3. Created VPCs and VMs under VPCs. 4. Shutdown the Host(Xen) and MS. 5. Start the Host and MS. Observation: The SSVM and CPVM were not coming up with “InsufficientServerCapacityException” exception. The Dashboard was showing exhausted management IPs . Deleted all the VMS ,still the IPs were not released. Below is the table which shows that all the management ips are reserved. mysql> select * from op_dc_ip_address_alloc; ++---++++--+-+-+ | id | ip_address| data_center_id | pod_id | nic_id | reservation_id | taken | mac_address | ++---++++--+-+-+ | 1 | 10.147.40.181 | 1 | 1 | 34 | 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 | 1 | | 2 | 10.147.40.182 | 1 | 1 | 3 | a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 2 | | 3 | 10.147.40.183 | 1 | 1 | 7 | 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 | 3 | | 4 | 10.147.40.184 | 1 | 1 | 7 | 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 | 4 | | 5 | 10.147.40.185 | 1 | 1 | 29 | 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 5 | | 6 | 10.147.40.186 | 1 | 1 | 30 | 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 6 | | 7 | 10.147.40.187 | 1 | 1 | 4 | a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 7 | | 8 | 10.147.40.188 | 1 | 1 | 7 | ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 | 8 | | 9 | 10.147.40.189 | 1 | 1 | 7 | 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 | 9 | | 10 | 10.147.40.190 | 1 | 1 | 7 | 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 | 10 | ++---++++--+-+-+ As all the IPs were in reserved state ,SSVM and CPVM were not coming up. Was not able to reproduce this issue again . Attached is the server log. -- 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-3294) CLONE - System VMs not coming up due to “InsufficientServerCapacityException”.(not consistently reproducible)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696310#comment-13696310 ] Nitin Mehta commented on CLOUDSTACK-3294: - CLOUDSTACK-2813 has the short term fix, but we need to looking up at the cleaning up resources holistically atleast for virtual machines and have a better failover in case the cleanup fails. Some ideas add something like a cleanup flag in case the cleanup didn't work, and probably releasing the resources before next retry of vm deployment, expunge thread etc, but I am not convinced if this is the most elegant solution. Is this ok ? Was talking to Murali and he was suggesting if long term, can can make acquiring resources transactional ? Or enhance framework like Journal to keep a log of resources acquired and then releasing them ? Any ideas ? If we go down this path of checking each use case why cleanup resources can fail like for fix in CLOUDSTACK-2813, we will end up with a lot of flags and if else conditions. While it fixes this problem, I still see loopholes in our cleanup approach. At the minimum we should start checking the cleanup() response. If it returns false, cleanup is not done yet and needs to be taken care of in the future (say before another retry of vm deployment or expunge cycle). Next step, could be making cleanup function itself more robust(example – _networkMgr.release throws an exception and we just do nothing right now). > CLONE - System VMs not coming up due to > “InsufficientServerCapacityException”.(not consistently reproducible) > - > > Key: CLOUDSTACK-3294 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3294 > 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: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Seps:t > 1.Have a CS with advanced zone . > 2.Created some user VMs. > 3.Created VPCs and VMs under VPCs. > 4.Shutdown the Host(Xen) and MS. > 5.Start the Host and MS. > Observation: > The SSVM and CPVM were not coming up with > “InsufficientServerCapacityException” exception. > The Dashboard was showing exhausted management IPs . > Deleted all the VMS ,still the IPs were not released. > Below is the table which shows that all the management ips are reserved. > mysql> select * from op_dc_ip_address_alloc; > ++---++++--+-+-+ > | id | ip_address| data_center_id | pod_id | nic_id | reservation_id > | taken | mac_address | > ++---++++--+-+-+ > | 1 | 10.147.40.181 | 1 | 1 | 34 | > 48d95839-6fb1-4bc4-b23a-c9f1891bf1fa | 2013-05-31 17:10:06 | 1 | > | 2 | 10.147.40.182 | 1 | 1 | 3 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 2 | > | 3 | 10.147.40.183 | 1 | 1 | 7 | > 238830cd-8cbe-411e-8016-352129885df6 | 2013-05-31 17:07:30 | 3 | > | 4 | 10.147.40.184 | 1 | 1 | 7 | > 70f091d4-acb4-435b-bfde-9bdb35bcfa6b | 2013-05-31 17:09:15 | 4 | > | 5 | 10.147.40.185 | 1 | 1 | 29 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 5 | > | 6 | 10.147.40.186 | 1 | 1 | 30 | > 14690352-e9a0-4695-a834-0552175f7684 | 2013-05-31 17:08:45 | 6 | > | 7 | 10.147.40.187 | 1 | 1 | 4 | > a7b9610c-9319-478c-84e4-e70be099cd9d | 2013-05-31 17:07:29 | 7 | > | 8 | 10.147.40.188 | 1 | 1 | 7 | > ea8644d1-7801-4dbb-aa0c-204f31e922a1 | 2013-05-31 17:08:25 | 8 | > | 9 | 10.147.40.189 | 1 | 1 | 7 | > 245e0082-d697-454d-9689-b36cc3b6e113 | 2013-05-31 17:11:16 | 9 | > | 10 | 10.147.40.190 | 1 | 1 | 7 | > 094e371a-da69-44e0-80fd-14c2d090e935 | 2013-05-31 17:10:15 | 10 | > ++---++++--+-+-+ > As all the IPs were in reserved state ,SSVM and CPVM were not coming up. > Was not able to reproduce this issue again . > Attached is the server log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA adm
[jira] [Resolved] (CLOUDSTACK-3082) System VMs are failed to start with Xen 6.2.0( Failing to create VIF's)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-3082. - Resolution: Fixed > System VMs are failed to start with Xen 6.2.0( Failing to create VIF's) > --- > > Key: CLOUDSTACK-3082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3082 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Sharad Yadav >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.log.2013-06-19.gz > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1758) SSVM test cases failing in VMware with 4.1 builds
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696345#comment-13696345 ] ASF subversion and git services commented on CLOUDSTACK-1758: - Commit 7d72966e45d3e2f122d5b3d44e9e300bf017a593 in branch refs/heads/master-6-17-stable from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7d72966 ] CLOUDSTACK-1758: Update ssh key location for vmware Signed-off-by: Prasanna Santhanam (cherry picked from commit 6e63bb78220a057bca329ee6a8779f0e4c476586) > SSVM test cases failing in VMware with 4.1 builds > -- > > Key: CLOUDSTACK-1758 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1758 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.1.0, 4.2.0 > Environment: vm ware >Reporter: Rayees Namathponnan >Assignee: Girish Shilamkar >Priority: Blocker > Fix For: 4.2.0 > > > SVM test cases failing in VM ware, > Traceback (most recent call last): > File > "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line > 804, in test_08_reboot_cpvm > self.test_04_cpvm_internals() > File > "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line > 481, in test_04_cpvm_internals > "Check cloud service is running or not" > AssertionError: Check cloud service is running or not > I checked the ssvm, i can see cloud server is running > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > root@s-3-VM:~# service cloud status > cloud.com service (type=secstorage) is running: process id: 2751 > root@s-3-VM:~# service cloud status > cloud.com service (type=secstorage) is running: process id: 2751 > root@s-3-VM:~# > followed below steps > > cp /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud /tmp > > chmod 600 /tmp/id_rsa.cloud > > ssh -i /tmp/id_rsa.cloud -p 3922 root@10.223.250.122 (private ip) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-1758) SSVM test cases failing in VMware with 4.1 builds
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Spindler reopened CLOUDSTACK-1758: Should this have been: ssh -i /var/lib/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no And not: ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no ? > SSVM test cases failing in VMware with 4.1 builds > -- > > Key: CLOUDSTACK-1758 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1758 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.1.0, 4.2.0 > Environment: vm ware >Reporter: Rayees Namathponnan >Assignee: Girish Shilamkar >Priority: Blocker > Fix For: 4.2.0 > > > SVM test cases failing in VM ware, > Traceback (most recent call last): > File > "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line > 804, in test_08_reboot_cpvm > self.test_04_cpvm_internals() > File > "/data/Repo2/incubator-cloudstack/test/integration/smoke/test_ssvm.py", line > 481, in test_04_cpvm_internals > "Check cloud service is running or not" > AssertionError: Check cloud service is running or not > I checked the ssvm, i can see cloud server is running > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > root@s-3-VM:~# service cloud status > cloud.com service (type=secstorage) is running: process id: 2751 > root@s-3-VM:~# service cloud status > cloud.com service (type=secstorage) is running: process id: 2751 > root@s-3-VM:~# > followed below steps > > cp /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud /tmp > > chmod 600 /tmp/id_rsa.cloud > > ssh -i /tmp/id_rsa.cloud -p 3922 root@10.223.250.122 (private ip) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-3220) Object_Store_Refactor - No Download Template link when saved to AWS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas O'Dowd reopened CLOUDSTACK-3220: --- Reopening with the required database dump. > Object_Store_Refactor - No Download Template link when saved to AWS > --- > > Key: CLOUDSTACK-3220 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3220 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: chrome on linux > devcloud > Cloudian and Amazon S3 object stores >Reporter: Thomas O'Dowd >Assignee: Jessica Wang > Attachments: cloud.sql.bz2, NoDownloadTemplateLink.png > > > 1. Remove NFS secondary storage > 2. Add Amazon S3 secondary storage > 3. Upload a template > 4. Verify template is in the S3 bucket (using external tool - s3cmd or other) > 5. Navigate to the template in the GUI. > 6. hover over the quickview > At step 6, I expect a button to download the template and a button to delete > the template. I can only see the delete button though. There is no log output > to suggest why or what might be different. > However, when I use the Cloudian S3 object store in step 2 instead of AWS, > the same gui offers me a download template button. > I've tried this a few times with Amazon storage with the same results. I'm > going to delete my database now and try again with Cloudian just to verify > that I'm not seeing things. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3220) Object_Store_Refactor - No Download Template link when saved to AWS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas O'Dowd updated CLOUDSTACK-3220: -- Attachment: cloud.sql.bz2 Hi Jessica, Please find the database dump attached. Hopefully you can see that I uploaded 2 templates to my local Cloudian (accesskey and secretkey are local only so I left them intact in the dump). - MyTiny - AnotherTiny Both templates have no download link button. Let me know if you need further info. Thanks, Tom. > Object_Store_Refactor - No Download Template link when saved to AWS > --- > > Key: CLOUDSTACK-3220 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3220 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: chrome on linux > devcloud > Cloudian and Amazon S3 object stores >Reporter: Thomas O'Dowd >Assignee: Jessica Wang > Attachments: cloud.sql.bz2, NoDownloadTemplateLink.png > > > 1. Remove NFS secondary storage > 2. Add Amazon S3 secondary storage > 3. Upload a template > 4. Verify template is in the S3 bucket (using external tool - s3cmd or other) > 5. Navigate to the template in the GUI. > 6. hover over the quickview > At step 6, I expect a button to download the template and a button to delete > the template. I can only see the delete button though. There is no log output > to suggest why or what might be different. > However, when I use the Cloudian S3 object store in step 2 instead of AWS, > the same gui offers me a download template button. > I've tried this a few times with Amazon storage with the same results. I'm > going to delete my database now and try again with Cloudian just to verify > that I'm not seeing things. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty reassigned CLOUDSTACK-2927: -- Assignee: Rayees Namathponnan > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI, Packaging >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2162) "Invalid scopeundefined" occurs when build a cloud via choosing "Contine with basic installation" button.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-2162: - Priority: Blocker (was: Major) > "Invalid scopeundefined" occurs when build a cloud via choosing "Contine with > basic installation" button. > - > > Key: CLOUDSTACK-2162 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2162 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy >Affects Versions: 4.2.0 > Environment: Build No.#244 > (CloudStack-non-OSS-MASTER-244-rhel6.3.tar.gz) > XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr > Server, Win7Entx64SP1 for Client machine. >Reporter: Minying Bao >Priority: Blocker > Fix For: 4.2.0 > > Attachments: After clicking Back button.jpg, Invalid > scopeundefined.jpg, ManagementServer.log > > > Repro Steps > Setup the cloudstack environment as normal. (Configured NFS & CS-Mgr Servers) > Launch browser, start CloudStack GUI via [http://cs-mgr IP:8080/client] and > finish to build a cloud step by step. > Expected Result > CloudStack should be set up successfully without any error. > Actual Result > An error "Invalid scopeundefined" occurs. (refer to screenshot named "Invalid > scopeundefined") > And then click "Back" button, the page will nevigate to the "Add Primary > Storage" page. Re-check, all the parameters are correct. (refer to screenshot > named "After clicking Back button") -- 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-1194) Bug with the web interface (re isolation method)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696598#comment-13696598 ] Ryan Lei commented on CLOUDSTACK-1194: -- This problem is now fixed for Chrome on Windows, too. Previously the isolation method could not be shown. > Bug with the web interface (re isolation method) > > > Key: CLOUDSTACK-1194 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1194 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, UI >Affects Versions: 4.0.1 > Environment: Centos 6 x86_64 >Reporter: Nux >Assignee: Hiroaki Kawai > Attachments: centos_firefox.png, isolation_method.png, isolation.png, > MacOS-Chrome-CS4.2.png, MacOS-Chrome.png > > > By total chance I was using Chrome (24.0) today instead of Firefox (stock > EL6, 10.0.12 ESR) and when creating a new zone on Chrome it offers me "VLAN, > GRE or STT" whereas this dropdown menu is not visible in Firefox at all. See > the images: > Firefox: http://img.nux.ro/9Nx-Selection_071.png > Chrome: http://img.nux.ro/P3b-Selection_070.png -- 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-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696604#comment-13696604 ] ASF subversion and git services commented on CLOUDSTACK-2927: - Commit b4f6b57ef5242a2faf9df386aaff6e00ad388e03 in branch refs/heads/master from [~rayeesn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b4f6b57 ] Adding axis2.xml to cloudstack-bridge/webapps/awsapi/WEB-INF/conf as part of defect CLOUDSTACK-2927 > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI, Packaging >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696606#comment-13696606 ] ASF subversion and git services commented on CLOUDSTACK-2927: - Commit 9b722f4ccc0f6fb3ee4a34297593fe01fc23b4d7 in branch refs/heads/4.2 from [~rayeesn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b722f4 ] Adding axis2.xml to cloudstack-bridge/webapps/awsapi/WEB-INF/conf as part of defect CLOUDSTACK-2927 > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI, Packaging >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-2927. Resolution: Fixed > [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error > --- > > Key: CLOUDSTACK-2927 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI, Packaging >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > Attachments: awsapi.log > > > Set enable.ec2.api to true. > Register user using cloudstack-aws-api-register. > Make any SOAP API call e.g. ec2-describe-images using ec2 tools. > Output - Server.InternalError: An unexpected error occurred > Attached awsapi.log for log details > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3235) Settings tab in Account gives ERROR for non root domain admin and user
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal closed CLOUDSTACK-3235. -- > Settings tab in Account gives ERROR for non root domain admin and user > -- > > Key: CLOUDSTACK-3235 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3235 > 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: shweta agarwal >Priority: Minor > Fix For: 4.2.0 > > Attachments: error.png > > > Repro steps: > Create a Domain D under Root domain > create a admin ,user for this domain > login as domain D admin or domain D user > goto account tab > select an account > select settings tab of the account > Bug > Setting Tabs shows error > Expectation: > Setting tab should not be there for non root domain admin and user as they > are not allowed to change settings for the account. > Screen shot attached: -- 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-3295) [AWSAPI] User registration fails with http error code 500
Likitha Shetty created CLOUDSTACK-3295: -- Summary: [AWSAPI] User registration fails with http error code 500 Key: CLOUDSTACK-3295 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3295 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Likitha Shetty Priority: Critical Fix For: 4.2.0 Turn enable.ec2.api flag. Register cloudstack user --- cloudstack-aws-api-register --apikey= --secretkey= --cert= --url=http://:7080/awsapi Output User registration failed with http error code: 500 awsapi.log --- 2013-07-01 11:15:11,602 DEBUG [bridge.service.UserContext] (catalina-exec-int-3:null) initializing a new [anonymous] UserContext! 2013-07-01 11:15:11,603 ERROR [bridge.service.EC2RestServlet] (catalina-exec-int-3:null) SetCertificate exception /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/classes/xes.keystore (No such file or directory) java.io.FileNotFoundException: /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/classes/xes.keystore (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:137) at java.io.FileInputStream.(FileInputStream.java:96) at com.cloud.bridge.service.EC2RestServlet.setCertificate(EC2RestServlet.java:456) at com.cloud.bridge.service.EC2RestServlet.doGetOrPost(EC2RestServlet.java:297) at com.cloud.bridge.service.EC2RestServlet.doGet(EC2RestServlet.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:105) at com.cloud.bridge.service.EC2MainServlet.doGet(EC2MainServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-01 11:15:11,604 ERROR [bridge.service.EC2RestServlet] (catalina-exec-int-3:null) Unexpected exception: null java.lang.NullPointerException at com.cloud.bridge.service.EC2RestServlet.setCertificate(EC2RestServlet.java:494) at com.cloud.bridge.service.EC2RestServlet.doGetOrPost(EC2RestServlet.java:297) at com.cloud.bridge.service.EC2RestServlet.doGet(EC2RestServlet.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCha
[jira] [Reopened] (CLOUDSTACK-3227) Attach volume fails in case of uploaded volume and volume created from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal reopened CLOUDSTACK-3227: Unmarking it duplicate as this bug is tracking two different exception one for uploaded volume and one for snapshot created volume. the one you marked it as duplicate is only for uploaded volume. > Attach volume fails in case of uploaded volume and volume created from > snapshot > --- > > Key: CLOUDSTACK-3227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3227 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot >Affects Versions: 4.2.0 > Environment: build: > CloudPlatform-4.2-117-rhel6.3 >Reporter: shweta agarwal >Assignee: Koushik Das >Priority: Blocker > Fix For: 4.2.0 > > > Repro steps: > 1. Create a VM > 2. Upload a volume compatible to VM created > 3. Attach volume to VM > 4. Create volume from a snapshot > 5. Attach the volume created from snapshot > Bug: > attach volume will fail in both step 3 and 4 > Expected Result: > attach volume should pass in all types of volume > MS log shows: > in case we try to attach snapshot created volume > 2013-06-27 14:00:03,226 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-6:job-323) Unexpected exception while executing > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd > java.lang.NullPointerException > at > com.cloud.storage.VolumeManagerImpl.copyVolume(VolumeManagerImpl.java:1443) > at > com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1487) > at > com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1733) > 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:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-06-27 14:00:03, > in case we try to attach uploaded volume: > Unexpected exception while executing > org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd > java.lang.NullPointerException > at > com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1503) > at > com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1742) > 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:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > Seems attach volumes fails every time it need to copy volume from secondary > to primary . -- 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
