[jira] [Updated] (CLOUDSTACK-3435) Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of the Vms failed to get an ip address/hostname allocation.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy updated CLOUDSTACK-3435:
--
Attachment: ips.txt
dhcphosts.txt
dnsmasq.leases
dnsmasq-1.log
out.txt
Deployed 30 vms in kvm host and got the vm ip address from the DB.
Used the below script to ping all the vms. All the vms are reachable.
That means all the vms got address.
for i in $(cat ips.txt); do ping -c 1 $i >>out.txt; done
> Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of
> the Vms failed to get an ip address/hostname allocation.
>
>
> Key: CLOUDSTACK-3435
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3435
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: Build from 4.2
>Reporter: Sangeetha Hariharan
>Assignee: Jayapal Reddy
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: dhcphosts.txt, dnsmasq-1.log, dnsmasq.leases, ips.txt,
> out.txt, xenparallel.rar
>
>
> Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of
> the Vms failed to get an ip address/hostname allocation.
> Steps to reproduce the problem:
> Advanced zone set up with Xenserver host.
> Deploy 30 Vms in parallel.
> Out of 30 vms , one of the Vms failed to get an ip address/hostname
> allocation.
> Vm-name = "hello-3" and id is "i-3-6".
> DhcpEntry and startCommand both seem to be succeed. But Vm is not assigned an
> ip address/host name.
> There is no entry for this Vm in the /etc/dhcphost.txt
> Management server log snippet when vm was deployed:
> 2013-07-09 16:29:30,734 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350322: Executing: { Cmd , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 100011, [{"com
> .cloud.agent.api.routing.DhcpEntryCommand":{"vmMac":"02:00:78:0b:00:03","vmIpAddress":"10.1.1.154","vmName":"hello-3","defaultRouter":"10.1.1.1","defaultDns":"10.1.1.1","duid":"00
> :03:00:01:02:00:78:0b:00:03","isDefault":true,"executeInSequence":false,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.name":"r-4-VM","router
> .ip":"169.254.3.54"},"wait":0}}] }
> 2013-07-09 16:29:32,955 DEBUG [agent.transport.Request] (DirectAgent-42:null)
> Seq 1-729350322: Processing: { Ans: , MgmtId: 7200344900649, via: 1, Ver:
> v1, Flags: 10, [{"com.clou
> d.agent.api.Answer":{"result":true,"wait":0}}] }
> 2013-07-09 16:29:32,955 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350322: Received: { Ans: , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 10, { Answer } }
> 2013-07-09 16:30:09,920 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350375: Sending { Cmd , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 100011, [{"com.cl
> oud.agent.api.StartCommand":{"vm":{"id":6,"name":"i-3-6-VM","bootloader":"PyGrub","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":262144000,"maxRam":262144000,"arch"
> :"x86_64","os":"CentOS 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"2be9ae733de747c7","pa
> rams":{"enable.dynamic.scaling":"false"},"uuid":"1457d848-3931-4c08-abd4-dea36c6ba1c7","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"d9e985f0-c218-4
> 8ff-ac6a-57979c3641e0","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"be66004e-e6d4-3312-8f15-283793aa26d2","id":1,"poolType":"Net
> workFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/xen/primary","port":2049}},"name":"ROOT-6","size":21474836480,"path":"63420079-fdce-4299-b4e9-549e35d89538",
> "volumeId":5,"vmName":"i-3-6-VM","accountId":3,"format":"VHD","id":5}},"diskSeq":0,"type":"ROOT"},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"IS
> O","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"71bb2293-8644-45c0-8708-975763bd8ed1","ip":"10.1.1.
> 154","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:78:0b:00:03","dns1":"72.52.126.11","dns2":"72.52.126.12","broadcastType":"Vlan","type":"Guest","broadcastUri":"vla
> n://2130","isolationUri":"vlan://2130","isSecurityGroupEnabled":false}]},"hostIp":"10.223.57.3","executeInSequence":false,"wait":0}}]
> }
> 2013-07-09 16:30:09,921 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350375: Exec
[jira] [Commented] (CLOUDSTACK-3794) exception while querying async job
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719301#comment-13719301 ] Sailaja Mada commented on CLOUDSTACK-3794: -- Hi, I have created similar bug @ https://issues.apache.org/jira/browse/CLOUDSTACK-3534 which is closed as resolved/incomplete looking for MS log with TRACE enabled.I could not get the details as I had removed the setup by then. Can you please update the required information by Alena in this bug and reopen the bug. Thanks, Sailaja.M > exception while querying async job > -- > > Key: CLOUDSTACK-3794 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3794 > 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 > > > After management server runs for a while, following exceptions are being > observed: > Unexpected exception while querying async job-78 = [ > 1f22fdcd-359f-4e2f-ac09-d252eba6d943 ] status: > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.PreparedStatement@5b1e89f5: UPDATE async_job SET > async_job.last_polled='2013-07-25 10:58:41' WHERE async_job.id = 78 > at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:822) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:775) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:1256) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.queryAsyncJobResult(AsyncJobManagerImpl.java:441) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.queryAsyncJobResult(AsyncJobManagerImpl.java:401) > at > com.cloud.api.ApiResponseHelper.queryJobResult(ApiResponseHelper.java:1927) > at > org.apache.cloudstack.api.command.user.job.QueryAsyncJobResultCmd.execute(QueryAsyncJobResultCmd.java:66) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.sql.SQLException: Lock wait timeout exceeded; try restarting > transaction > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074) > at com.mysql.jdbc.MysqlIO.checkErrorPac
[jira] [Resolved] (CLOUDSTACK-2768) [SXM] snapshot on a migrated volume is getting NULL path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-2768. --- Resolution: Cannot Reproduce I tried it multiple times with the latest 4.2 branch. I am not able to reproduce the problem. Created an instance with 1 root and 2 data disks. I had 2 clusters each with 2 storage pools. Initiated migration of one data disk from one storage pool to another storage pool within the cluster. Immediately triggered migration of instance to second cluster. Migration of the volume succeeds and migration of the instance fails, which is the expected behavior. Took snapshot of both the data disks and root disk and it was successful. Do let me know you can still reproduce the issue and if I am missing any steps. > [SXM] snapshot on a migrated volume is getting NULL path > - > > Key: CLOUDSTACK-2768 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2768 > 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: Devdeep Singh >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.zip > > > Steps to reproduce: > 1. create two clusters [C1,C2]with two primary storages[P1,P2] respectively. > 2. deploy a VM VM1 and attach 2 data volumes V1,V2. > 3. migrate volume V1. > 4. While volume V1 is being migrated, Migrate VM1 with volumes to Cluster C2. > Step 4 will result in failure and all the volumes and VM should be as it was > before migrate operation. > 5. Now, take a snapshot of volume V1 OR V2. This is updating the path in the > snapshot table as NULL, which in turn results in Null pointer exception on > snapshot operations(template/volume creation from snapshot) > id: 3 > data_center_id: 1 > account_id: 2 >domain_id: 1 >volume_id: 25 > disk_offering_id: 5 > status: BackedUp > path: NULL > name: sharedshared_tt_20130530164422 > uuid: 3ba59708-cb37-4019-a54c-5f6db4eaa36d >snapshot_type: 0 > type_description: MANUAL > size: 107374182400 > created: 2013-05-30 16:44:22 > removed: NULL > backup_snap_id: NULL > swift_id: NULL > sechost_id: NULL > prev_snap_id: 0 > hypervisor_type: XenServer > version: 2.2 >s3_id: 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
[jira] [Created] (CLOUDSTACK-3794) exception while querying async job
Srikanteswararao Talluri created CLOUDSTACK-3794: Summary: exception while querying async job Key: CLOUDSTACK-3794 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3794 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 After management server runs for a while, following exceptions are being observed: Unexpected exception while querying async job-78 = [ 1f22fdcd-359f-4e2f-ac09-d252eba6d943 ] status: com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.PreparedStatement@5b1e89f5: UPDATE async_job SET async_job.last_polled='2013-07-25 10:58:41' WHERE async_job.id = 78 at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:822) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:775) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.update(GenericDaoBase.java:1256) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.async.AsyncJobManagerImpl.queryAsyncJobResult(AsyncJobManagerImpl.java:441) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.async.AsyncJobManagerImpl.queryAsyncJobResult(AsyncJobManagerImpl.java:401) at com.cloud.api.ApiResponseHelper.queryJobResult(ApiResponseHelper.java:1927) at org.apache.cloudstack.api.command.user.job.QueryAsyncJobResultCmd.execute(QueryAsyncJobResultCmd.java:66) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355) at org.apache.commons.dbcp.
[jira] [Updated] (CLOUDSTACK-2481) Object_Store_Refactor - Templates - Not able to create a template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-2481:
--
Attachment: cloud.dmp
management-server.rar
Attached management server log file and cloud DB.
> Object_Store_Refactor - Templates - Not able to create a template from
> snapshot.
>
>
> Key: CLOUDSTACK-2481
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2481
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: Build from object store
>Reporter: Sangeetha Hariharan
>Assignee: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: cloud.dmp, management-server.rar
>
>
> Steps to reproduce the problem:
> Deploy a VM.
> Take a snapshot of the root volume.
> Create a template from this snapshot.
> API fails with following error message:
> "DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@bb917d1: DELETE FROM
> vm_template WHERE vm_template.id= 203"
> Management server logs:
> 2013-05-14 09:32:33,964 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
> ===START=== 10.217.252.128 -- GET command=createTemplate&response=json
> &sessionkey=X%2FK09rgZ%2BYIUuGYkv7UGa0FoBEc%3D&snapshotid=d44ae73f-3cbd-49d3-8964-6c3325c24286&name=template1&displayText=template1&osTypeId=fce76ff
> 6-bc28-11e2-8a23-6a01c7e420f0&isPublic=true&passwordEnabled=false&_=1368552572710
> 2013-05-14 09:32:34,059 DEBUG [cloud.template.TemplateManagerImpl]
> (catalina-exec-3:null) This template is getting created from other template,
> sett
> ing source template Id to: 202
> 2013-05-14 09:32:34,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-3:null) submit async job-18, details: AsyncJobVO {id:18,
> userId: 2, a
> ccountId: 2, sessionKey: null, instanceType: Template, instanceId: 203, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdO
> riginator: null, cmdInfo:
> {"sessionkey":"X/K09rgZ+YIUuGYkv7UGa0FoBEc\u003d","ctxUserId":"2","httpmethod":"GET","osTypeId":"fce76ff6-bc28-11e2-8a23-6
> a01c7e420f0","isPublic":"true","response":"json","id":"203","displayText":"template1","snapshotid":"d44ae73f-3cbd-49d3-8964-6c3325c24286","passwordE
> nabled":"false","name":"template1","_":"1368552572710","ctxAccountId":"2","ctxStartEventId":"61"},
> cmdVersion: 0, callbackType: 0, callbackAddress:
> null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid:
> 206915885079359, completeMsid: null, lastUpdated: null, lastPolled: null,
> created: null}
> 2013-05-14 09:32:34,119 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-20:job-18) Executing
> org.apache.cloudstack.api.command.user.template.C
> reateTemplateCmd for job-18
> 2013-05-14 09:32:34,122 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
> ===END=== 10.217.252.128 -- GET command=createTemplate&response=json&s
> essionkey=X%2FK09rgZ%2BYIUuGYkv7UGa0FoBEc%3D&snapshotid=d44ae73f-3cbd-49d3-8964-6c3325c24286&name=template1&displayText=template1&osTypeId=fce76ff6-
> bc28-11e2-8a23-6a01c7e420f0&isPublic=true&passwordEnabled=false&_=1368552572710
> 2013-05-14 09:32:34,207 DEBUG [agent.transport.Request]
> (Job-Executor-20:job-18) Seq 3-178062289: Sending { Cmd , MgmtId:
> 206915885079359, via: 3,
> Ver: v1, Flags: 100111,
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":
> "snapshots/2/1/29d8dd25-c221-4bbc-bc8b-b89d37e362de","volume":{"uuid":"5d0bd6d7-4ebe-4fb6-98ad-5df52850e739","volumeType":"ROOT","dataStore":{"org.a
> pache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"e97b5727-d157-3dc1-b32c-065b99806623","id":1,"poolType":"NetworkFilesystem","host":"10.223.
> 110.232","path":"/export/home/sangeetha/campo-systemp-1/primary","port":2049}},"name":"ROOT-5","size":8589934592,"path":"86b8d3a8-44c9-4bb0-b4fb-1ba
> 98d3e4f75","volumeId":5,"vmName":"i-2-5-VM","accountId":2,"id":5},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232/export/h
> ome/sangeetha/campo-systemp-1/secondary","_role":"Image"}},"vmName":"i-2-5-VM","name":"test-2_ROOT-5_20130514161859","hypervisorType":"XenServer","i
> d":1}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/203","uuid":"7f10ae7a-0e78-40ed-9b51-3a6a23c9dc66","id
> ":203,"format":"RAW","accountId":2,"hvm":true,"displayText":"template1","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.2
> 32/export/home/sangeetha/campo-systemp-1/secondary","_role":"Image"}},"name":"25860e266-0bd4-3eab-abe5-190cd2cafb8b"}},"wait":10800}}]
>
[jira] [Reopened] (CLOUDSTACK-2481) Object_Store_Refactor - Templates - Not able to create a template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N reopened CLOUDSTACK-2481:
---
Verified this bug on the latest ACS 4.2 build. I still see the issue.
Template creation failed with CloudRuntimeException: Failed to create
templatetimeout
Log snippet from management server log file:
===
2013-07-25 01:49:15,300 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===START=== 10.146.0.20 -- GET
command=createTemplate&response=json&sessionkey=WZF71LaQge%2FCxbMvbNdG7KLOOkM%3D&snapshotid=0c8fccb2-8804-45ad-a245-00c4a0e117b0&name=CS-2481&displayText=CS-2481&osTypeId=c893a654-f367-11e2-97d7-06045a66&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&_=1374731355190
2013-07-25 01:49:15,459 DEBUG [cloud.template.TemplateManagerImpl]
(catalina-exec-13:null) This template is getting created from other template,
setting source template Id to: 5
2013-07-25 01:49:15,523 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-13:null) submit async job-93 = [
a0ada67d-899c-4147-9adb-2d5a0fc15c91 ], details: AsyncJobVO {id:93, userId: 2,
accountId: 2, sessionKey: null, instanceType: Template, instanceId: 202, cmd:
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
cmdOriginator: null, cmdInfo:
{"sessionkey":"WZF71LaQge/CxbMvbNdG7KLOOkM\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","httpmethod":"GET","osTypeId":"c893a654-f367-11e2-97d7-06045a66","isPublic":"true","isdynamicallyscalable":"false","response":"json","id":"202","displayText":"CS-2481","snapshotid":"0c8fccb2-8804-45ad-a245-00c4a0e117b0","passwordEnabled":"false","name":"CS-2481","_":"1374731355190","ctxAccountId":"2","ctxStartEventId":"366"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6615759585382,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-25 01:49:15,527 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===END=== 10.146.0.20 -- GET
command=createTemplate&response=json&sessionkey=WZF71LaQge%2FCxbMvbNdG7KLOOkM%3D&snapshotid=0c8fccb2-8804-45ad-a245-00c4a0e117b0&name=CS-2481&displayText=CS-2481&osTypeId=c893a654-f367-11e2-97d7-06045a66&isPublic=true&passwordEnabled=false&isdynamicallyscalable=false&_=1374731355190
2013-07-25 01:49:15,530 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-19:job-93 = [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) Executing
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-93 =
[ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]
2013-07-25 01:49:15,580 DEBUG [storage.image.TemplateDataFactoryImpl]
(Job-Executor-19:job-93 = [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) template
202 is already in store:1, type:Image
2013-07-25 01:49:15,596 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-19:job-93 = [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) copyAsync
inspecting src type SNAPSHOT copyAsync inspecting dest type TEMPLATE
2013-07-25 01:49:15,663 DEBUG [agent.transport.Request] (Job-Executor-19:job-93
= [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) Seq 3-875365393: Sending { Cmd ,
MgmtId: 6615759585382, via: 3, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/24/53c10659-48cd-4c45-9da2-2b53bab80b3d","volume":{"uuid":"beb7a932-aa9c-45a4-ba62-ee54b284cf6d","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c65a038a-750c-3b4f-bf26-7ce3b74e1c85","id":1,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/sanjeev/pri_xen_os","port":2049}},"name":"ROOT-14","size":21474836480,"path":"10eb79a0-3d16-49e6-84f3-92f5767a30bd","volumeId":24,"vmName":"i-2-14-VM","accountId":2,"format":"VHD","id":24},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/sanjeev/sec_xen_os","_role":"Image"}},"vmName":"i-2-14-VM","name":"storage-gc_ROOT-14_20130725054019","hypervisorType":"XenServer","id":22}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/202","uuid":"90bac93d-b873-4042-aa7d-f1adfbd71d36","id":202,"format":"RAW","accountId":2,"hvm":true,"displayText":"CS-2481","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/sanjeev/sec_xen_os","_role":"Image"}},"name":"246cb2165-0311-3110-bb89-b64e553bb510"}},"executeInSequence":false,"wait":10800}}]
}
2013-07-25 01:49:27,004 DEBUG [agent.transport.Request] (Job-Executor-19:job-93
= [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) Seq 3-875365393: Received: { Ans:
, MgmtId: 6615759585382, via: 3, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-07-25 01:49:27,021 DEBUG [cloud.template.TemplateManagerImpl]
(Job-Executor-19:job-93 = [ a0ada67d-899c-4147-9adb-2d5a0fc15c91 ]) Failed
[jira] [Updated] (CLOUDSTACK-3779) Support System vm scaling on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-3779: Status: Ready To Review (was: In Progress) > Support System vm scaling on VMWare > --- > > Key: CLOUDSTACK-3779 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3779 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.2.0 > > > This is to support system vm dynamic scaling of cpu/ram. This sets the latest > system template for VMWare as dynamically_scalable and enhance the flow > accordingly -- 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-3637) system vm scaleup is failing on xen server ;Unable to Scale the vm: s-1-VMas vm does not have xs tools to support dynamic scaling
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala resolved CLOUDSTACK-3637.
-
Resolution: Not A Problem
As the new system template for xenserver does not have XS tools we cannot
support system vm scaling on Xenserver. we only support system vm scaling on
Xenserver
> system vm scaleup is failing on xen server ;Unable to Scale the vm: s-1-VMas
> vm does not have xs tools to support dynamic scaling
> --
>
> Key: CLOUDSTACK-3637
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3637
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
> Environment: hypsrvisor:xen-6.1
>Reporter: prashant kumar mishra
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Logs_db.rar
>
>
> Steps to reproduce
> ---
> 1-create system offering for Secondary storage VM say ssvm
> :(cpu=500,Memory=512)
> 2-Try to scale up secondary storage vm to 'ssvm'
> Expected
> --
> scale up should be successful
> Actual
> --
> Scaling up failed
> Log
>
> w used: 10334765056, reserved: 0; requested mem:
> 536870912,alloc_from_last:false
> 2013-07-18 13:05:58,723 DEBUG [agent.transport.Request]
> (Job-Executor-25:job-25 = [ e831a436-25d8-4078-a37e-47af4aafa9cf ]) Seq
> 1-1677852845: Sending { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1, Flags:
> 100111,
> [{"com.cloud.agent.api.ScaleVmCommand":{"vm":{"id":1,"name":"s-1-VM","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false},"vmName":"s-1-VM","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"wait":0}}]
> }
> 2013-07-18 13:05:58,724 DEBUG [agent.transport.Request]
> (Job-Executor-25:job-25 = [ e831a436-25d8-4078-a37e-47af4aafa9cf ]) Seq
> 1-1677852845: Executing: { Cmd , MgmtId: 7635042566263, via: 1, Ver: v1,
> Flags: 100111,
> [{"com.cloud.agent.api.ScaleVmCommand":{"vm":{"id":1,"name":"s-1-VM","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false},"vmName":"s-1-VM","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"wait":0}}]
> }
> 2013-07-18 13:05:58,725 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-111:null) Seq 1-1677852845: Executing request
> 2013-07-18 13:05:58,844 WARN [xen.resource.CitrixResourceBase]
> (DirectAgent-111:null) Unable to upgrade s-1-VM due to Unable to Scale the
> vm: s-1-VMas vm does not have xs tools to support dynamic scaling
> com.cloud.utils.exception.CloudRuntimeException: Unable to Scale the vm:
> s-1-VMas vm does not have xs tools to support dynamic scaling
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:697)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:638)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-18 13:05:58,852 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-111:null) Seq 1-1677852845: Response Received:
> 2013-07-18 13:05:58,853 DEBUG [agent.transport.Request]
> (DirectAgent-111:null) Seq 1-1677852845: Processing: { Ans: , MgmtId:
> 7635042566263, via: 1, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.ScaleVmAnswer":{"result":false,"details":"Unable to
> upgrade s-1-VM due to Unable to Scale the vm: s-1-VM
[jira] [Commented] (CLOUDSTACK-2571) [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719276#comment-13719276
]
Rajesh Battala commented on CLOUDSTACK-2571:
reported issue got fixed with the commit
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=7054db44700ba813d513bf8e16b0266d308a8dc6
> [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
> ---
>
> Key: CLOUDSTACK-2571
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2571
> 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: Rajesh Battala
> Labels: automation, integration-test
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have a CloudStack with at least one advanced zone
> 2. Add a zone-wide primary storage.
> 3. Try to put the above primary storage into maintenance
> Observations:
> (i) It throws an NPE while trying to enable the maintenance.
> Here is the exception snippet from mgmt server log.
> 013-05-20 06:14:26,338 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.240.57 -- GET
> command=createStoragePool&scope=zone&zoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&name=primaryNew&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025128021
> 2013-05-20 06:14:26,411 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.240.57 -- GET
> command=createStoragePool&scope=zone&zoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&name=primaryNew&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025128021
> 2013-05-20 06:14:32,555 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-20 06:14:32,558 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-20 06:14:32,664 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-20 06:14:32,667 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-20 06:14:38,857 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===START=== 10.252.240.57 -- GET
> command=listZones&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&id=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&_=1369025140804
> 2013-05-20 06:14:38,875 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===END=== 10.252.240.57 -- GET
> command=listZones&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&id=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&_=1369025140804
> 2013-05-20 06:14:39,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.252.240.57 -- GET
> command=listStoragePools&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025140864
> 2013-05-20 06:14:39,056 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===END=== 10.252.240.57 -- GET
> command=listStoragePools&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025140864
> 2013-05-20 06:14:41,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
> ===START=== 10.252.240.57 -- GET
> command=enableStorageMaintenance&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025142915
> 2013-05-20 06:14:41,109 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-16:null) submit async job-11, details: AsyncJobVO {id:11,
> userId: 2, accountId: 2, sessionKey: null, instanceType: StoragePool,
> instanceId: 2, cmd:
> org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"a1a1a150-6709-3d81-a414-4cee93e62168","sessionkey":"wmpW6VMxTUivFIGDqS52aaozHqs\u003d","ctxUserId":"2","httpmethod":"GET","_":"1369025142915","ctxAccountId":"2","ctxStartEventId":"50"},
> 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-05-20 06:14:41,113 DEBUG [cloud.api.ApiServlet] (catalin
[jira] [Commented] (CLOUDSTACK-3421) When hypervisor is down, no HA occurs with log output "Agent state cannot be determined, do nothing"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719270#comment-13719270
]
Bryan Whitehead commented on CLOUDSTACK-3421:
-
I've also added my logs for the same problem in issue 3535.
> When hypervisor is down, no HA occurs with log output "Agent state cannot be
> determined, do nothing"
>
>
> Key: CLOUDSTACK-3421
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3421
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Management Server
>Affects Versions: 4.1.0
> Environment: CentOS 6.4 minimal install
> Libvirt, KVM/Qemu
> CloudStack 4.1
> GlusterFS 3.2, replicated+distributed as primary storage via Shared Mount
> Point
> 3 physical servers
> * 1 management server, running NFS secondary storage
> ** 1 nic, management+storage
> * 2 hypervisor nodes, running glusterfs-server
> ** 4x nic, management+storage, public, guest, gluster peering
> * Advanced zone
> * KVM
> * 4 networks:
> eth0: cloudbr0: management+secondary storage,
> eth2: cloudbr1: public
> eth3: cloudbr2: guest
> eth1: gluster peering
> * Shared Mount Point
> * custom network offering with redundant routers enabled
> * global settings tweaked to increase speed of identifying down state
> ** ping.interval: 10sec
>Reporter: Gerard Lynch
>Priority: Critical
> Fix For: 4.1.1, 4.2.0, Future
>
> Attachments: catalina_management-server.zip
>
>
> We wanted to test CloudStack's HA capabilities by simulating outages to find
> out how long it would take to recover. One of the tests was simulating loss
> of a hypervisor node by shutting it down. When we tested this, we found
> that CloudStack failed to bring up any of the VMs (System or Instance), which
> were on the down node, until the node was powered back up and reconnected.
> In the logs, we see repeating occurances of:
> INFO [utils.exception.CSExceptionErrorCode] (AgentTaskPool-11:) Could not
> find exception: com.cloud.exception.OperationTimedoutException in error code
> list for exceptions
> INFO [utils.exception.CSExceptionErrorCode] (AgentTaskPool-10:) Could not
> find exception: com.cloud.exception.OperationTimedoutException in error code
> list for exceptions
> WARN [agent.manager.AgentAttache] (AgentTaskPool-11:) Seq 14-660013135:
> Timed out on Seq 14-660013135: { Cmd , MgmtId: 93515041483, via: 14, Ver:
> v1, Flags: 100011, [{"CheckHealthCommand":{"wait":50}}] }
> WARN [agent.manager.AgentAttache] (AgentTaskPool-10:) Seq 15-1097531400:
> Timed out on Seq 15-1097531400: { Cmd , MgmtId: 93515041483, via: 15, Ver:
> v1, Flags: 100011, [{"CheckHealthCommand":{"wait":50}}] }
> WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-11:) Operation timed
> out: Commands 660013135 to Host 14 timed out after 100
> WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-10:) Operation timed
> out: Commands 1097531400 to Host 15 timed out after 100
> WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-11:) Agent state cannot
> be determined, do nothing
> WARN [agent.manager.AgentManagerImpl] (AgentTaskPool-10:) Agent state cannot
> be determined, do nothing
> To reproduce:
> 1. Build the environment as detailed above
> 2. Register an ISO
> 3. Create a new guest network using the custom network offering (that offers
> redundant routers)
> 3. Provision an instance
> 4. Ensure the system VMs and instance are on the first hypervisor node
> 5. Shutdown the first hypervisor node (or pull the plug)
> Expected result:
> All system VMs and instance(s) should be brought up on the 2nd hypervisor
> node.
> Actual result:
> We see the first hypervisor node marked "disconnected."
> All System VMs and the Instance are still marked "Running", however ping to
> any of them fails.
> Ping to the redundant router on the 2nd hypervisor node is still working.
> We see in the logs
> "INFO [utils.exception.CSExceptionErrorCode] (AgentTaskPool-11:) Could not
> find exception: com.cloud.exception.OperationTimedoutException in error code
> list for exceptions"
> Followed by
> "Agent state cannot be determined, do nothing"
> Searching for "Cloudstack Agent state cannot be determined, do nothing" lead
> to: CLOUDSTACK-803 - https://reviews.apache.org/r/8853/
> Which caused me some concern, because if I read the logic in the ticket
> correctly... The management server will not perform any HA actions if it's
> unable to determine the state of a hypervisor node. In the scenario above,
> it's not a loss of connectivity, but an actual outage on the hypervisor... so
> I'd rather like HA to occur. S
[jira] [Created] (CLOUDSTACK-3793) Unable to apply userdata and password entry on router
Srikanteswararao Talluri created CLOUDSTACK-3793: Summary: Unable to apply userdata and password entry on router Key: CLOUDSTACK-3793 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3793 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: xenserver deployment Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.2.0 Steps to reproduce: == Try to deploy a new instance on advanced zone which triggers creation of VR. Unable to contact resource. com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable: Unable to apply userdata and password entry on router at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3799) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2991) at com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:941) at com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2026) at com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2132) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2073) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:618) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3334) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2894) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2880) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-25 15:47:05,792 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-46:job-77 = [ 4d488eae-3a74-475a-a6f9-a8d721f78807 ]) Cleaning up resources for the vm VM[User|t] in Starting state -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1591) Cannot reconnect KVM host to management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-1591. --- > Cannot reconnect KVM host to management server > -- > > Key: CLOUDSTACK-1591 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1591 > 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: devcloud-kvm (CentOS 6.3 box acting as Management server > and host, local storage), tools/marvin/devcloud-kvm/devcloud-kvm-advanced.cfg > marvin config >Reporter: Marcus Sorensen >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > Tried running master branch today, everything came up ok, but when I tried to > restart the cloudstack-agent service, it couldn't reconnect to the management > server. The system was complaining about the local storage pool, saying it's > a duplicate pool. If I go to the host and delete the pool, when the agent > tries to reconnect the pool is just recreated, but the same error is thrown. > Should probably do a getPool first and if the uuid exists, with correct path, > call it good rather than complaining about a duplicate. > Management server: > 2013-03-07 13:32:07,033 WARN [cloud.storage.StorageManagerImpl] > (AgentConnectTaskPool-10:null) Unable to setup the local storage pool for > Host[-1-Routing] > com.cloud.utils.exception.CloudRuntimeException: Another active pool with the > same uuid already exists > at > org.apache.cloudstack.storage.datastore.lifecycle.AncientPrimaryDataStoreLifeCycleImpl.initialize(AncientPrimaryDataStoreLifeCycleImpl.java:343) > at > com.cloud.storage.StorageManagerImpl.createLocalStorage(StorageManagerImpl.java:729) > 2013-03-07 13:32:17,553 WARN [agent.manager.AgentManagerImpl] > (AgentConnectTaskPool-11:null) Monitor LocalStoragePoolListener says there is > an error in the connect process for 1 due to Unable to setup the local > storage pool for Host[-1-Routing] -- 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-1676) basic zone security groups enabled with 'DefaultSharedNetworkOffering'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-1676. --- > basic zone security groups enabled with 'DefaultSharedNetworkOffering' > -- > > Key: CLOUDSTACK-1676 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1676 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.1.0, 4.2.0 > Environment: KVM Hosts >Reporter: Marcus Sorensen >Assignee: Jessica Wang > Fix For: 4.2.0 > > > I deployed a basic zone with a management bridge and a guest bridge, > selecting 'DefaultSharedNetworkOffering' as the network offering. > I launched an instance > I could not ssh into instance, but instance could ping gateway, google, etc. > I ran 'ebtables -t nat -L' and saw that there were rules for this instance. > I ran 'ebtables -t nat -F i-2-3-VM-in', and could now SSH into server. > It was as though firewall/security groups were enabled, but without any way > to edit. -- 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-1948) users can no longer set global limits to -1 (e.g. pagesize)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-1948. --- > users can no longer set global limits to -1 (e.g. pagesize) > --- > > Key: CLOUDSTACK-1948 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1948 > 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, 4.2.0 >Reporter: Marcus Sorensen >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > Just installed 4.1 over a 4.0 install, and ran into an issue where the max > pagesize global parameter was set to -1, which worked to effectively disable > paging in 4.0, but 4.1 passes the -1 right on to the SQL query, which mysql > hates. > management server log shows "LIMIT 0, -1" in mysql statements. I'm assuming > that a non-positive integer used to just remove the limit clause, since it > worked in 4.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] [Closed] (CLOUDSTACK-3015) VPC virtual router lists deleted nics
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-3015. --- > VPC virtual router lists deleted nics > - > > Key: CLOUDSTACK-3015 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3015 > 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, 4.2.0 >Reporter: Marcus Sorensen >Assignee: Min Chen >Priority: Blocker > Labels: integration-test > Fix For: 4.1.1, 4.2.0 > > > Create a VPC > Create a network in VPC > Create a VM in network in VPC > Shut down VM > Wait awhile > Observed: Something cleans up the unused network in the VPC, removing the > guest network nic from the VPC router. > Start VM > Observed: New nic is allocated for VPC router > List routers > Observed: Router shows both old and new nics. > We need to either avoid cleaning up these nics when the aren't used, or avoid > showing them whenever a VPC/router is queried for nics. > As a bonus, I've occasionally seen vpcs fail to be deletable. It seemed to be > because some of its nics had no broadcast URI (the removed ones), and a NULL > pointer was thrown. -- 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-3382) Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3382. working fine as per the FS hence closing the defect. > Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated. > --- > > Key: CLOUDSTACK-3382 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3382 > 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: Blocker > Fix For: 4.2.0 > > > The details of the defect are as follows: > 1)I have created a Advanced Zone setup with two hosts. > 2)Then created a VM using the Strict Implicit for one account and created > another VM with different account without using any dedication. > 3)two VM's are created on two hosts available and one is implicitly dedicated > host and other one is a shared host. > 4)then tried to migrate the VM from one account to another and clicked on the > UI option available. > Observed that the there is a popup saying no suitable host found. > But according to the FS of the Dedicated resources Zone/pod/cluster/host it > says as below: > "Migration of VMs > 1.If VM to be migrated is non-dedicated: > a.if destination host is implicitly or explicitly dedicated, migrate it to > that host, but an alert is generated > b.if destination host is non-dedicated, migrate it to the destination host. > 2.If VM to be migrated is dedicated > a.if destination host is implicitly or explicitly dedicated to the same > account, migrate it to that host. > b.if destination host is implicitly or explicitly dedicated to different > account, migrate it to that host, but an alert is generated > c.if destination host is non-dedicated, migrate it to that host but an alert > is generated" > -- 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-2571) [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru closed CLOUDSTACK-2571.
--
Have tried to enableStorageMainatenance on the latest CloudStack build and
didn't see any issue reported here. Closing this bug.
command=enableStorageMaintenance&id=0f658e18-7e6a-3442-9c36-de5c56926e26&response=json&sessionkey=Fw1ClHjopxJGuA8EeFNnuaDcLVY%3D&_=137472839799
> [Zone-Wide-PrimaryStorage] NPE while deleting the zone-wide primary storage
> ---
>
> Key: CLOUDSTACK-2571
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2571
> 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: Rajesh Battala
> Labels: automation, integration-test
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have a CloudStack with at least one advanced zone
> 2. Add a zone-wide primary storage.
> 3. Try to put the above primary storage into maintenance
> Observations:
> (i) It throws an NPE while trying to enable the maintenance.
> Here is the exception snippet from mgmt server log.
> 013-05-20 06:14:26,338 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.240.57 -- GET
> command=createStoragePool&scope=zone&zoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&name=primaryNew&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025128021
> 2013-05-20 06:14:26,411 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.240.57 -- GET
> command=createStoragePool&scope=zone&zoneid=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&name=primaryNew&url=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Fswamy%2Fprimary.campo.xen.1&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025128021
> 2013-05-20 06:14:32,555 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-20 06:14:32,558 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-20 06:14:32,664 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-20 06:14:32,667 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-20 06:14:38,857 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===START=== 10.252.240.57 -- GET
> command=listZones&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&id=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&_=1369025140804
> 2013-05-20 06:14:38,875 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===END=== 10.252.240.57 -- GET
> command=listZones&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&id=8adda1e5-ac1c-49b0-bec8-6da98f6ff116&_=1369025140804
> 2013-05-20 06:14:39,033 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===START=== 10.252.240.57 -- GET
> command=listStoragePools&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025140864
> 2013-05-20 06:14:39,056 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
> ===END=== 10.252.240.57 -- GET
> command=listStoragePools&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025140864
> 2013-05-20 06:14:41,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
> ===START=== 10.252.240.57 -- GET
> command=enableStorageMaintenance&id=a1a1a150-6709-3d81-a414-4cee93e62168&response=json&sessionkey=wmpW6VMxTUivFIGDqS52aaozHqs%3D&_=1369025142915
> 2013-05-20 06:14:41,109 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-16:null) submit async job-11, details: AsyncJobVO {id:11,
> userId: 2, accountId: 2, sessionKey: null, instanceType: StoragePool,
> instanceId: 2, cmd:
> org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"a1a1a150-6709-3d81-a414-4cee93e62168","sessionkey":"wmpW6VMxTUivFIGDqS52aaozHqs\u003d","ctxUserId":"2","httpmethod":"GET","_":"1369025142915","ctxAccountId":"2","ctxStartEventId":"50"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7280707764394,
> completeMsid: null, lastUpdated: null, lastPo
[jira] [Updated] (CLOUDSTACK-3743) [Account] test_tags.py:TestResourceTags not tearing down the account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-3743: --- Component/s: Automation Affects Version/s: 4.2.0 Fix Version/s: 4.2.0 > [Account] test_tags.py:TestResourceTags not tearing down the account > > > Key: CLOUDSTACK-3743 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3743 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.0 >Reporter: Rayees Namathponnan >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > After complete this suite test_tags.py:TestResourceTags; account creating > during the test not removed; it will effect following tests execution -- 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-3791) Download Template Fails with NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719207#comment-13719207
]
Ram Ganesh commented on CLOUDSTACK-3791:
John,
Is this issue seen only when devCloud is used?
> Download Template Fails with NPE
>
>
> Key: CLOUDSTACK-3791
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3791
> 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: John Burwell
>Priority: Blocker
>
> When registering a template, the download fails with the following NPE from
> the SSVM:
> 2013-07-24 17:26:31,364 DEBUG [agent.transport.Request]
> (AgentManager-Handler-1:null) Seq 2-1900150803: Processing: { Ans: , MgmtId:
> 1, via: 2, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> GetRootDir for null failed due to java.lang.NullPointerException\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1806)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:1560)\n\tat
>
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:186)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
> Secondary storage is configured as NFS on devcloud
> (nfs://192.168.56.15/opt/storage/secondary). The following is the
> information for the template being registered:
> Name: CentOS 5.x
> Description: CentOS 5.x
> URL: http://bhaisaab.org/vms/cent.vhd
> Zone: All Zones
> Hypervisor: XenServer
> Format: VHD
> Extractable: false
> Password Enabled: false
> Dynamically Scalable: false
> Public: true
> Featured: false
--
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-3774) [XenServer]NPE while creating template from snapshot on a upgraded setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-3774: --- Assignee: Devdeep Singh > [XenServer]NPE while creating template from snapshot on a upgraded setup > > > Key: CLOUDSTACK-3774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3774 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Devdeep Singh >Priority: Critical > Fix For: 4.2.0 > > Attachments: afterupgrademysqldumpusage1.dmp, apilog.log, > beforeupgrade_mysqldump.dmp, management-server.log, snap.png, > templatefromsnapshot.png > > > Setup: Xen 6.1 hosts , Two zone ( Zone1 with local storage ,Zone 2 - NFS ) > Upgraded from 3.0.6 to 4.2 > Steps: > 1) Create Account X and deploy VM on a NFS storage Zone 3 > 2) Create snapshot from ROOT volume of this instance > 3) Tried to create template from this snapshot. > Observations : > 1. It failed with NPE. > 2. UI results NPE as a failure message > 2013-07-24 19:07:50,164 DEBUG [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) snapshots > already exists on secondary storage, and is mounted at > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1 > 2013-07-24 19:07:50,164 INFO [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) snapshots > directory created/exists on Secondary Storage. > 2013-07-24 19:07:50,165 DEBUG [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) volumes > already exists on secondary storage, and is mounted at > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1 > 2013-07-24 19:07:50,166 INFO [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) volumes > directory created/exists on Secondary Storage. > 2013-07-24 19:07:50,166 DEBUG > [storage.resource.LocalNfsSecondaryStorageResource] (Job-Executor-25:job-85 = > [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) Executing: sudo mount > 2013-07-24 19:07:50,224 DEBUG > [storage.resource.LocalNfsSecondaryStorageResource] (Job-Executor-25:job-85 = > [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) Execution is successful. > 2013-07-24 19:07:50,224 DEBUG > [storage.resource.LocalNfsSecondaryStorageResource] (Job-Executor-25:job-85 = > [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) mount point > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1 already > exists > 2013-07-24 19:07:50,309 DEBUG [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) > Executing: null -p > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1/snapshots/4/40 > -s b1988755-6c46-4c73-9d3c-2fd751d27825.vhd -n > f29545c7-cb53-49c8-81a4-5e9ce566093a.vhd -t > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1/template/tmpl/4/207 > 2013-07-24 19:07:50,309 WARN [storage.resource.NfsSecondaryStorageResource] > (Job-Executor-25:job-85 = [ 9d0965c2-23ce-4c82-abec-f68c5e523c56 ]) > Exception: null -p > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1/snapshots/4/40 > -s b1988755-6c46-4c73-9d3c-2fd751d27825.vhd -n > f29545c7-cb53-49c8-81a4-5e9ce566093a.vhd -t > /var/lib/cloud/mnt/secStorage/0a639c32-c2df-36e3-883d-eebcb5093bf1/template/tmpl/4/207 > java.lang.NullPointerException > at java.lang.ProcessBuilder.start(ProcessBuilder.java:457) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfsXenserver(NfsSecondaryStorageResource.java:360) > at > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfs(NfsSecondaryStorageResource.java:401) > at > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.createTemplateFromSnapshot(NfsSecondaryStorageResource.java:419) > at > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:445) > at > org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:208) > at > org.apache.cloudstack.storage.resource.LocalNfsSecondaryStorageResource.executeRequest(LocalNfsSecondaryStora
[jira] [Updated] (CLOUDSTACK-3780) G11N: JA: Garbled code display on Pod configuration & Host configuration pages during "Add zone"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-3780: --- Assignee: Sanjay Tripathi > G11N: JA: Garbled code display on Pod configuration & Host configuration > pages during "Add zone" > > > Key: CLOUDSTACK-3780 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3780 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: > Build#CloudPlatform-4.2-256(CloudPlatform-4.2-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS, CS-Mgr Servers >Reporter: Minying Bao >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > Attachments: JA_Garbled code_Host page.jpg, JA_Garbled code_Pod > page.jpg > > > Repro Steps > 1. Open the browser and login to Web Portal. > 2. Navigate the “Infrastructure” tab. > 3. Click “Zones->view all” button. > 4. Click “Add zone” button. > 5. Check “Basic”. then click “Next” button. > 6. Finish the configuration step by step. > 7. Observe the all the UIs. > Expected Result > All the UIs should be display as normal. > Actual Result > Garbled code display on Pod configuration & Host configuration pages during > "Add zone" > Language info. > JA -> Fail > SC -> pass > EN -> Pass -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Whitehead updated CLOUDSTACK-3535: Attachment: management-server.log.Agent My logs when host power supply died. No HA happened. > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > Attachments: management-server.log.Agent > > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719182#comment-13719182 ] Bryan Whitehead commented on CLOUDSTACK-3535: - Just to point out, my experience with this problem was slightly different. I saw the host as "Disconnected" but no migrations happened and all VM's on the dead host were shown as Running when they were definitely not Running. I'll see if I can dig up the logs. > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719181#comment-13719181 ] Sateesh Chodapuneedi commented on CLOUDSTACK-1809: -- Capacity that CloudStack as an IaaS software looks for is the resource capacity that is available for VM deployment rather than raw physical capacity on hardware. In VMware, virtual machine resource allocation would be done over resource pool defined over host/cluster etc. units. When a host is add to cluster, the host's resources would be taken over by resource pool group of the cluster. Hence total effective (something actually available for VMs' usage on hypervisor) cpu/memory have to read from resource pool group of the cluster which is aggregate capacity of resources from all hosts added to that cluster. Currently CloudStack fetches total capacity for each host and reports to management server and gets stored in op_host_capacity table, and while displaying capacity in dash board capacities of all hosts are added by reading from this table. This just gives raw hardware capacity of resources in zone rather than capacity of resource pool. Resource capacity calculation should take place against resource pool of cluster rather than individual host to get correct capacity. Also there may be more than 1 resource pool existing which need to be taken care of. One more case to consider is enabling DRS where resource management is handled by DRS system. The changes needed to move from raw capacity to resource pool capacity are involved and would need good time. > Actual capacity availble for vm deployement in vmware cluster is less than > what Dashboard shows (total_capacity in op_host_capacity table) > --- > > Key: CLOUDSTACK-1809 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1809 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: vmware >Reporter: prashant kumar mishra >Assignee: Sateesh Chodapuneedi >Priority: Critical > Fix For: 4.2.0 > > Attachments: DB_Logs.rar, screenshot-1.jpg, screenshot-2.jpg > > > ->For vmware cluster(with only one host) vcenter shows total capacity of > cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm > deployment and cloud stack shows (Memory 15.99 GB, CPU 9572) . > ->Due to this calculation difference CS allocator shows capacity is available > on host but vm deployment fails with run time error > "2013-06-13 12:23:01,945 WARN [vmware.resource.VmwareResource] > (DirectAgent-141:10.147.40.7) StartCommand failed due to Exception: > java.lang.RuntimeException > Message: The available CPU resources in the parent resource pool are > insufficient for the operation. > java.lang.RuntimeException: The available CPU resources in the parent > resource pool are insufficient for the operation. > " > DB > - > mysql> select *from op_host_capacity where capacity_type in (0,1)\G; > *** 1. row *** >id: 1 > host_id: 1 >data_center_id: 1 >pod_id: 1 >cluster_id: 1 > used_capacity: 6039797760 > reserved_capacity: 0 >total_capacity: 17169539072 > capacity_type: 0 >capacity_state: Enabled > update_time: 2013-06-13 15:29:33 > created: 2013-06-05 16:05:51 > *** 2. row *** >id: 2 > host_id: 1 >data_center_id: 1 >pod_id: 1 >cluster_id: 1 > used_capacity: 7700 > reserved_capacity: 0 >total_capacity: 9572 > capacity_type: 1 >capacity_state: Enabled > update_time: 2013-06-13 15:29:33 > created: 2013-06-05 16:05:51 > 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719179#comment-13719179
]
Marcus Sorensen commented on CLOUDSTACK-2725:
-
Delay *could* help, but you're assuming that 1) the selected VM template has
hotplug support and 2) that you're waiting long enough, that's a shot in the
dark, though I'm guessing if the delay is 10 minutes that would be sufficient.
What we really need is a way to interrogate for hotplug support before trying
to do so.
> [Automation] Re-attaching volume on VM failing in KVM
> -
>
> Key: CLOUDSTACK-2725
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
> 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: Automation environment KVM
> Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2725.rar
>
>
> Below two test case failing from BVT
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
> integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
> Steps to reproduce
> Step 1 : Create an account, service offering, create volume, create VM
> Step 2 : Attach volume to VM ,
> Step 3 : Detach volume
> Step 4 : Attach volume to VM again
> Actual result
> Attachment failed with below error
> 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
> (Job-Executor-98:job-1246) Seq 5-258539658: Rec
> eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
> AttachAnswer } }
> 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Unexpected e
> xception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
> TestDiskServ to VM: ce79edb6-
> a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
> unable to execute QEMU comman
> d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> at
> com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
> t(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
> 22)
> 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-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Complete asy
> nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
> text: Failed to attach volume
> : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
> org.libvirt.LibvirtException: internal erro
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719176#comment-13719176 ] Marcus Sorensen edited comment on CLOUDSTACK-3535 at 7/25/13 2:49 AM: -- Sounds like this is not KVM specific. Not to be blunt, but I don't think Logan's solution works, at all. We have no way of knowing what's running on a host or not, simply by whether or not we can ping it on the management network. A host may be running with 20 VMs, all healthy, but the management nic went out on the host. Relying on ping presents too many assumptions (Storage is ethernet based, and the same interface/network is serving both management and storage). The only way to go is with proper fencing. For those storage types that support it, revoke access to other hosts when a VM starts, so that even if it was running elsewhere, you basically pull the power cord when you start up the VM in the known good location. Meaning that a host starting a VM has an exclusive lock on the volumes associated with the VM. Additionally/alternatively, an IPMI service that will power off a host if the agent isn't in maintenance mode and is non-communicative. In the mean time, like the short term solution mentions, if we can put the host into maintenance mode manually when it's known-down, and allow vms to migrate, that would at least allow people to get their system working again without DB hacks. was (Author: mlsorensen): Sounds like this is not KVM specific. Not to be blunt, but I don't think Logan's solution works, at all. We have no way of knowing what's running on a host or not, simply by whether or not we can ping it on the management network. A host may be running with 20 VMs, all healthy, but the management nic went out on the host. Relying on ping presents too many assumptions (Storage is ethernet based, and the same interface/network is serving both management and storage). The only way to go is with proper fencing. For those storage types that support it, revoke access to other hosts when a VM starts, so that even if it was running elsewhere, you basically pull the power cord when you start up the VM in the known good location. Additionally/alternatively, an IPMI service that will power off a host if the agent isn't in maintenance mode and is non-communicative. In the mean time, like the short term solution mentions, if we can put the host into maintenance mode manually when it's known-down, and allow vms to migrate, that would at least allow people to get their system working again without DB hacks. > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719176#comment-13719176 ] Marcus Sorensen commented on CLOUDSTACK-3535: - Sounds like this is not KVM specific. Not to be blunt, but I don't think Logan's solution works, at all. We have no way of knowing what's running on a host or not, simply by whether or not we can ping it on the management network. A host may be running with 20 VMs, all healthy, but the management nic went out on the host. Relying on ping presents too many assumptions (Storage is ethernet based, and the same interface/network is serving both management and storage). The only way to go is with proper fencing. For those storage types that support it, revoke access to other hosts when a VM starts, so that even if it was running elsewhere, you basically pull the power cord when you start up the VM in the known good location. Additionally/alternatively, an IPMI service that will power off a host if the agent isn't in maintenance mode and is non-communicative. In the mean time, like the short term solution mentions, if we can put the host into maintenance mode manually when it's known-down, and allow vms to migrate, that would at least allow people to get their system working again without DB hacks. > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719171#comment-13719171 ] Bryan Whitehead commented on CLOUDSTACK-3535: - Comment for [~tqlogan]… I've had the e1000 driver die / oops on me causing a disconnect of a host with v3.0.2 of cloudstack (as you described as an unlikely scenario). HA kicked in but qemu-kvm was unable to get a lock on the qcow2 files to start up the VM's on another host. This was resolved by me shutting down the host with no network forcing all the qemu-kvm's to shutdown and release their locks. (Note: the shared filesystem was gluster over infiniband/IPoIB). No harm done. Not sure how other shared filesystem/block devices would react though… I'm not in favor of just alerting an admin if a host is down. I'd like to see the previous 3.0.2 behavior restored of HA kicking in with a host disconnect (after a reasonable amount of time). (FWIW I've not experienced a host failure on 4.0.x so I'm not sure if that version also has this problem). > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3568) [Automation]Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15 Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719169#comment-13719169
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3568:
-
Went through the logs and looked at Sangeetha's setup (primary storage).
Let's take an example failure in the logs and trace the events:
2013-07-16 15:47:48,631 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-68:10.223.57.66) creating linked clone from template
2013-07-16 15:47:49,316 DEBUG [storage.motion.AncientDataMotionStrategy]
(Job-Executor-9:job-102 = [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) copyAsync
inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME
2013-07-16 15:47:49,323 DEBUG [agent.transport.Request] (Job-Executor-9:job-102
= [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) Seq 1-227737728: Sending { Cmd ,
MgmtId: 7647994577963, via: 1, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"6343361f88b73f178855d62eb1c3a698","origUrl":"http://nfs1.lab.vmops.com/templates/passwordssh/CentOS5.3-x86_64.ova","uuid":"1c3517c1-0226-47a7-90b3-96b7de70fc64","id":202,"format":"OVA","accountId":2,"checksum":"f6f881b7f2292948d8494db837fe0f47","hvm":true,"displayText":"test","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7caed722-555d-3f71-8794-76c5e8d8d5ad","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/master-vmware/primary","port":2049}},"name":"202-2-5806a2dd-c8ea-3a15-9b1a-af7098ec5de5"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7a3a4484-346a-4d83-903a-59e5dd7d2dff","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7caed722-555d-3f71-8794-76c5e8d8d5ad","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/master-vmware/primary","port":2049}},"name":"ROOT-106","size":0,"volumeId":104,"vmName":"i-4-106-VM","accountId":4,"format":"OVA","id":104}},"executeInSequence":false,"wait":0}}]
}
2013-07-16 15:47:49,324 DEBUG [agent.transport.Request] (Job-Executor-9:job-102
= [ 1b0c2fa4-2326-4fd2-921b-98d19ca17d38 ]) Seq 1-227737728: Executing: { Cmd
, MgmtId: 7647994577963, via: 1, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"6343361f88b73f178855d62eb1c3a698","origUrl":"http://nfs1.lab.vmops.com/templates/passwordssh/CentOS5.3-x86_64.ova","uuid":"1c3517c1-0226-47a7-90b3-96b7de70fc64","id":202,"format":"OVA","accountId":2,"checksum":"f6f881b7f2292948d8494db837fe0f47","hvm":true,"displayText":"test","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7caed722-555d-3f71-8794-76c5e8d8d5ad","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/master-vmware/primary","port":2049}},"name":"202-2-5806a2dd-c8ea-3a15-9b1a-af7098ec5de5"}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7a3a4484-346a-4d83-903a-59e5dd7d2dff","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"7caed722-555d-3f71-8794-76c5e8d8d5ad","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/master-vmware/primary","port":2049}},"name":"ROOT-106","size":0,"volumeId":104,"vmName":"i-4-106-VM","accountId":4,"format":"OVA","id":104}},"executeInSequence":false,"wait":0}}]
}
.
.
.
2013-07-16 15:47:50,229 INFO [vmware.mo.DatastoreMO]
(DirectAgent-70:10.223.57.66) Folder ROOT-106-104 does not exist on datastore
2013-07-16 15:47:51,025 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.223.57.66) creating linked clone from template
.
.
2013-07-16 15:47:53,917 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-70:10.223.57.66) Move volume out of volume-wrapper VM
2013-07-16 15:47:53,927 INFO [storage.resource.VmwareStorageProcessor]
(DirectAgent-68:10.223.57.66) Move volume out of volume-wrapper VM
2013-07-16 15:47:55,099 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-71:10.223.57.66) CreateCommand failed due to Exception:
java.lang.RuntimeException
Message: File [7caed722555d3f71879476c5e8d8d5ad] ROOT-106-104/ROOT-106-104.vmdk
was not found
java.lang.RuntimeException: File [7caed722555d3f71879476c5e8d8d5ad]
ROOT-106-104/ROOT-106-104.vmdk was not found
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:57)
at
com.cloud.hypervisor.vmware.mo.HostDatastoreBrowserMO.searchDatastore(HostDatastoreBrowserMO.java:78)
at
com.cloud.hypervisor.vmware.mo.D
[jira] [Commented] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719163#comment-13719163 ] Chip Childers commented on CLOUDSTACK-3535: --- Bumped up the severity because this is a core feature that isn't working for several users. > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-3535: -- Affects Version/s: (was: Future) 4.2.0 4.1.1 > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, 4.1.1, 4.2.0 > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-3535: -- Priority: Blocker (was: Major) > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, Future > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus >Priority: Blocker > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719160#comment-13719160 ] Bryan Whitehead commented on CLOUDSTACK-3535: - I just wanted to add that his bug is seriously a huge problem. Effectively 4.1/kvm is completely broken as is if a host goes down - when a router system vm is sitting on a dead host all VM's depending on that router are completely hosed. The work around to this is hacking the DB live to force the router systemvm to be Down. More details of my experience with this bug here: http://mail-archives.apache.org/mod_mbox/cloudstack-users/201307.mbox/browser > No HA actions are performed when a KVM host goes offline > > > Key: CLOUDSTACK-3535 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, KVM, Management Server >Affects Versions: 4.1.0, Future > Environment: KVM (CentOS 6.3) with CloudStack 4.1 >Reporter: Paul Angus > > If a KVM host 'goes down', CloudStack does not perform HA for instances which > are marked as HA enabled on that host (including system VMs) > CloudStack does not show the host as disconnected. -- 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-3569) Parallel deployment - Vmware - When deploying 30 parallel Vms , we see few Vms failing in SavePasswordCommand,DhcpEntryCommand ,VmDataCommand.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-3569:
---
Assignee: Sheng Yang
> Parallel deployment - Vmware - When deploying 30 parallel Vms , we see few
> Vms failing in SavePasswordCommand,DhcpEntryCommand ,VmDataCommand.
> ---
>
> Key: CLOUDSTACK-3569
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3569
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: Build from 4.2.0
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log
>
>
> Parallel deployment - Vmware - When deploying 30 parallel Vms , we see ~15
> Vms fail in org.apache.cloudstack.storage.command.CopyCommand.
> Steps to reproduce the problem:
> Set up - Advanced zone with Vmware ESXI, 5.0.0 host.
> Deploy 30 Vms in parallel in a network that is already implemented (router is
> already running).
> Only 9 vms were successfully deployed.
> ~15 Vms failed due to issue reported in cloudstack-3568.
> Rest of the Vm deplpoyment failed in SavePasswordCommand,DhcpEntryCommand
> ,VmDataCommand where it encounters an IO Exception when trying to communicate
> with the router.
> mysql> select count(*),state,type from vm_instance where name like "hello%"
> group by state,type ;
> +--+-+--+
> | count(*) | state | type |
> +--+-+--+
> | 42 | Error | User |
> | 9 | Running | User |
> +--+-+--+
> 2 rows in set (0.00 sec)
> Following exception seen in management server logs:
> 2013-07-16 15:46:18,814 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-44:10.223.57.66) VmDataCommand failed due to Exception:
> java.io.IOException
> Message: There was a problem while connecting to 10.223.57.96:3922
> java.io.IOException: There was a problem while connecting to 10.223.57.96:3922
> at com.trilead.ssh2.Connection.connect(Connection.java:792)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:132)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2345)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:441)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.io.IOException: Premature connection close
> at
> com.trilead.ssh2.transport.ClientServerHello.readLineRN(ClientServerHello.java:33)
> at
> com.trilead.ssh2.transport.ClientServerHello.(ClientServerHello.java:68)
> at
> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:461)
> at com.trilead.ssh2.Connection.connect(Connection.java:732)
> ... 13 more
> 2013-07-16 15:46:18,815 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-44:null) Seq 1-227737678: Response Received:
> 2013-07-16 15:46:18,815 DEBUG [agent.transport.Request] (DirectAgent-44:null)
> Seq 1-227737678: Processing: { Ans: , MgmtId: 7647994577963, via: 1, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"VmDataCommand
> failed due to Exception: java.io.IOException\nMessage: There was a problem
> while connecting to 10.223.57.96:3922\n","wait":0}}] }
> 2013-07-16 15:46:18,816 DEBUG [agent.transport.Request]
> (Job-Executor-16:job-109 = [ f31f7d1f-7f1e-453c-ba0a-5600ebe43487 ]) Seq
> 1-227737678: Received: { Ans: , MgmtId: 7647994577963, via: 1, Ver: v1,
> Flags: 10, { Answer, Answer } }
> 2013-07-16 15:46:18,816 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-1
[jira] [Resolved] (CLOUDSTACK-3629) [Storage]Migration of root disk from shared primary storage to another shared primary storage is throwing NPE.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-3629.
---
Resolution: Duplicate
> [Storage]Migration of root disk from shared primary storage to another shared
> primary storage is throwing NPE.
> --
>
> Key: CLOUDSTACK-3629
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3629
> 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: latest 4.2 build
>Reporter: manasaveloori
>Assignee: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps:
> 1.Have a CS with advanced zone and VMware hypervisor.
> 2.Create 2 shared cluster wide primary storages and a local storage.
> 3.Create an instance using shared storage.
> 4.Now migrate the root volume to another shared storage.
> Observed the following NPE.
> 013-07-18 18:56:28,762 DEBUG [agent.transport.Request]
> (Job-Executor-42:job-115 = [ 0d97cf94-37d4-41fd-8640-2a490aff6bc9 ]) Seq
> 3-357564564: Sending { Cmd , MgmtId: 7562229448750, via: 3, Ver: v1, Flags:
> 100011,
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"3a388fa2-0db1-4288-a38f-dd4795ccb8f6","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"17b16be4-3bd2-34c7-b4d5-cb7a84dc8cdd","id":2,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/manasa/primaryVMw/newpri","port":2049}},"name":"ROOT-16","size":0,"path":"ROOT-16-20","volumeId":20,"vmName":"i-2-16-VM","accountId":2,"format":"OVA","id":20}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"3a388fa2-0db1-4288-a38f-dd4795ccb8f6","volumeType":"ROOT","dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/manasa/secondaryVMw/newsec","_role":"Image"}},"name":"ROOT-16","size":0,"path":"volumes/2/20","volumeId":20,"vmName":"i-2-16-VM","accountId":2,"format":"OVA","id":20}},"executeInSequence":false,"wait":10800}}]
> }
> 2013-07-18 18:56:28,769 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-333:null) Seq 4-549978551: Executing request
> 2013-07-18 18:56:28,797 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-333:10.147.40.18) Datastore summary info, storageId:
> dec3649b-74c1-348e-b897-cbf4aedc1f03, localPath:
> /export/home/manasa/primaryVMw/newpri1, poolType: NetworkFilesystem,
> capacity: 590228480, free: 2051742019584, used: 3850542780416
> 2013-07-18 18:56:28,798 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-333:null) Seq 4-549978551: Response Received:
> 2013-07-18 18:56:28,799 DEBUG [agent.transport.Request]
> (StatsCollector-1:null) Seq 4-549978551: Received: { Ans: , MgmtId:
> 7562229448750, via: 4, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-07-18 18:56:29,624 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-357564564: Processing: { Ans: , MgmtId:
> 7562229448750, via: 3, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException\n\tat
>
> com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:105)\n\tat
>
> com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
> 2013-07-18 18:56:29,625 DEBUG [agent.transport.Request]
> (Job-Executor-42:job-115 = [ 0d97cf94-37d4-41fd-8640-2a490aff6bc9 ]) Seq
> 3-357564564: Received: { Ans: , MgmtId: 7562229448750, via: 3, Ver: v1,
> Flags: 10, { Answer } }
> 2013-07-18 18:56:29,625 DEBUG [storage.motion.AncientDataMotionStrategy]
> (Job-Executor-42:job-115 = [ 0d97cf94-37d4-41fd-8640-2a490aff6bc9 ]) copy to
> image store failed: java.lang.NullPointerException
> at
> com.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:105)
> at
> com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)
> at com.
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13719150#comment-13719150
]
ASF subversion and git services commented on CLOUDSTACK-2304:
-
Commit 80ac885e22b19dc2f7a0a9ba8b02b0911f32a9f3 in branch refs/heads/master
from [~edison]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=80ac885 ]
CLOUDSTACK-2304: fix migrate volume for vmware
> [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: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Archive.zip
>
>
> Try to migrate a volume from one zone wide primary storage to another.
> ===START=== 10.252.241.40 -- GET
> command=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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] [Commented] (CLOUDSTACK-3681) [Automation][BVT][VMWare]Failed to delete template during first time
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719151#comment-13719151
]
ASF subversion and git services commented on CLOUDSTACK-3681:
-
Commit 7f200d966e1558286c41613a0ffa782963bbf4e0 in branch refs/heads/master
from [~edison]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7f200d9 ]
CLOUDSTACK-3681: fix bunch of bugs related to vmware, regarding to snapshot
> [Automation][BVT][VMWare]Failed to delete template during first time
> -
>
> Key: CLOUDSTACK-3681
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3681
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
>Affects Versions: 4.2.0
> Environment: 4.2
> Vmware
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3681.rar
>
>
> BVT tets cases
> integration.smoke.test_templates.TestCreateTemplate.test_01_create_template
> failed with latest run
> Steps to reproduce
> Step 1 : Create a template "TemplateDeleteTest" from root volume
> Step 2 : Delete template "TemplateDeleteTest"
> Result
> Delete template failed, please the attached log (job-39)
> 013-07-19 20:58:02,470 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Sending { Cmd , Mgmt
> Id: 90928106758026, via: 8, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DeleteCommand":{"data":{"org.apache.cloudstack.storage.to.TemplateObj
> ectTO":{"path":"22d8d284a-d237-379b-af73-8631ac0d298b","uuid":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","id":202,"format":"OVA","accountId":2,"hvm":true,"displayText
> ":"TemplateDeleteTest","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1","_role":"I
> mage"}},"name":"22d8d284a-d237-379b-af73-8631ac0d298b"}},"wait":0}}] }
> 2013-07-19 20:58:02,766 DEBUG [agent.transport.Request]
> (AgentManager-Handler-12:null) Seq 8-640811237: Processing: { Ans: , MgmtId:
> 90928106758026, via: 8, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Unable to delete
> file template under Template path 22d8d284a-d237-379b-af73-8631ac0d298b
> ","wait":0}}] }
> 2013-07-19 20:58:02,767 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Received: { Ans: , M
> gmtId: 90928106758026, via: 8, Ver: v1, Flags: 10, { Answer } }
> 2013-07-19 20:58:02,781 WARN [cloud.template.HypervisorTemplateAdapter]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Failed to
> delete the
> template Tmpl[202-OVA-22d8d284a-d237-379b-af73-8631ac0d298b from the image
> store: nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1
> due to: Un
> able to delete file template under Template path
> 22d8d284a-d237-379b-af73-8631ac0d298b
> 2013-07-19 20:58:02,811 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Complete
> async job-39 = [ d534
> 1b65-45a2-45e7-bb60-58043720da15 ], jobStatus: 2, resultCode: 530, result:
> Error Code: 530 Error text: Failed to delete template
> Step 3 : Delete template "TemplateDeleteTest" again
> Result
> Template got deleted and observed below log in MS
> 2013-07-19 20:59:03,818 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
> ===START=== 10.216.51.171 -- GET
> command=deleteTemplate&id=e0d4421d-8bf5-4cb4-9792-5
> af13563ad76&zoneid=34e5d608-9f00-45b7-b808-4a4c47592636&response=json&sessionkey=kzg0H6VMwJZ1qk59pvUJssmIaaw%3D&_=1374293513274
> 2013-07-19 20:59:03,859 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-7:null) submit async job-40 = [
> b2a3496b-aac8-448d-8576-adbd84d0d77a ], details: As
> yncJobVO {id:40, userId: 2, accountId: 2, sessionKey: null, instanceType:
> Template, instanceId: 202, cmd:
> org.apache.cloudstack.api.command.user.template.DeleteTe
> mplateCmd, cmdOriginator: null, cmdInfo:
> {"response":"json","id":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","sessionkey":"kzg0H6VMwJZ1qk59pvUJssmIaaw\u003d","cmdEvent
> Type":"TEMPLATE.DELETE","ctxUserId":"2","zoneid":"34e5d608-9f00-45b7-b808-4a4c47592636","httpmethod":"GET","_":"1374293513274","ctxAccountId":"2","ctxStartEventId
> ":"167"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90928106758026,
> completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07
[jira] [Commented] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719148#comment-13719148
]
Fang Wang commented on CLOUDSTACK-3759:
---
Rayees,
I did a manually test:
1. create a new VM instance (fang-vm1) (on the zone 2 on your machine);
2. Create a new vol (fang-vol1);
3. wait for the VM come up, then stop the VM;
4. after the VM stop completes, I did a vol attach, and it works. no error
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --
>
> Key: CLOUDSTACK-3759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.2.0
> Environment: KVM
> Automation
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3759.rar
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> This issue is reproducible manually;
> Steps to reproduce
> --
> Step 1 : Create a VM
> Step 2 : Stop VM
> Step 3 : Create a volume and attach the volume to stoped VM
> Actual Result
> Volume attachment failed;
> Observed below error automation test log
>
> attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py",
> line 611, in test_06_deploy_startvm_attach_detach
> self.fail("Attach volume failed!")
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> Attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-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:comment-tabpanel&focusedCommentId=13719146#comment-13719146
]
ASF subversion and git services commented on CLOUDSTACK-2304:
-
Commit ca474d0e09f772cb22abf2802a308a2da5351592 in branch refs/heads/4.2 from
[~edison]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca474d0 ]
CLOUDSTACK-2304: fix migrate volume for vmware
> [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: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Archive.zip
>
>
> Try to migrate a volume from one zone wide primary storage to another.
> ===START=== 10.252.241.40 -- GET
> command=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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] [Resolved] (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
]
edison su resolved CLOUDSTACK-2304.
---
Resolution: Fixed
> [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: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Archive.zip
>
>
> Try to migrate a volume from one zone wide primary storage to another.
> ===START=== 10.252.241.40 -- GET
> command=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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=migrateVolume&storageid=230ae4af-0446-3929-a8cd-63ab88f31ab1&volumeid=d9efc3d8-1612-4998-95d7-c713e90b7173&response=json&sessionkey=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] [Resolved] (CLOUDSTACK-3262) [ZWPS][VMWARE] exception while creating template from snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-3262.
---
Resolution: Cannot Reproduce
create template from snapshot issue should be fixed, I can't reproduce it on 4.2
> [ZWPS][VMWARE] exception while creating template from snapshot
> --
>
> Key: CLOUDSTACK-3262
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3262
> 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: VMWARE deployment, ESXI 5.1
>Reporter: Srikanteswararao Talluri
>Assignee: edison su
>Priority: Critical
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> ==
> create a VM with its root volume on zone wide primary storage
> create a snapshot of the root volume
> create a template from snaphot.
> ===START=== 10.252.192.7 -- GET
> command=createTemplate&response=json&sessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D&snapshotid=8b9f5778-4788-4455-8e8a-db754e6634bb&name=t&displayText=t&osTypeId=f9a1c012-de74-11e2-b754-06e1a630&isPublic=true&passwordEnabled=false&_=1372403272346
> 2013-06-28 18:03:13,209 DEBUG [cloud.template.TemplateManagerImpl]
> (catalina-exec-16:null) This template is getting created from other template,
> setting source template Id to: 7
> 2013-06-28 18:03:13,299 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-16:null) submit async job-91, details: AsyncJobVO {id:91,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 209, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"ywi4cWnDQTL903lMXK6spFaF6U4\u003d","ctxUserId":"2","httpmethod":"GET","osTypeId":"f9a1c012-de74-11e2-b754-06e1a630","isPublic":"true","response":"json","id":"209","displayText":"t","snapshotid":"8b9f5778-4788-4455-8e8a-db754e6634bb","passwordEnabled":"false","name":"t","_":"1372403272346","ctxAccountId":"2","ctxStartEventId":"324"},
> 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-28 18:03:13,306 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
> ===END=== 10.252.192.7 -- GET
> command=createTemplate&response=json&sessionkey=ywi4cWnDQTL903lMXK6spFaF6U4%3D&snapshotid=8b9f5778-4788-4455-8e8a-db754e6634bb&name=t&displayText=t&osTypeId=f9a1c012-de74-11e2-b754-06e1a630&isPublic=true&passwordEnabled=false&_=1372403272346
> 2013-06-28 18:03:13,308 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-41:job-91) Executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd for job-91
> 2013-06-28 18:03:13,344 DEBUG [storage.image.ImageDataFactoryImpl]
> (Job-Executor-41:job-91) template 209 is not in store:1, type:Image
> 2013-06-28 18:03:13,446 DEBUG [storage.motion.AncientDataMotionStrategy]
> (Job-Executor-41:job-91) copy failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pools
> in zone 1
> at
> org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.createTemplateFromSnashot(AncientDataMotionStrategy.java:559)
> at
> org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:486)
> at
> org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:59)
> at
> org.apache.cloudstack.storage.image.ImageServiceImpl.createTemplateFromSnapshotAsync(ImageServiceImpl.java:174)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1755)
> 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-28 18:03:13,460 DEBUG [cloud.templa
[jira] [Updated] (CLOUDSTACK-3780) G11N: JA: Garbled code display on Pod configuration & Host configuration pages during "Add zone"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3780: Priority: Critical (was: Major) > G11N: JA: Garbled code display on Pod configuration & Host configuration > pages during "Add zone" > > > Key: CLOUDSTACK-3780 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3780 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: > Build#CloudPlatform-4.2-256(CloudPlatform-4.2-256-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS, CS-Mgr Servers >Reporter: Minying Bao >Priority: Critical > Fix For: 4.2.0 > > Attachments: JA_Garbled code_Host page.jpg, JA_Garbled code_Pod > page.jpg > > > Repro Steps > 1. Open the browser and login to Web Portal. > 2. Navigate the “Infrastructure” tab. > 3. Click “Zones->view all” button. > 4. Click “Add zone” button. > 5. Check “Basic”. then click “Next” button. > 6. Finish the configuration step by step. > 7. Observe the all the UIs. > Expected Result > All the UIs should be display as normal. > Actual Result > Garbled code display on Pod configuration & Host configuration pages during > "Add zone" > Language info. > JA -> Fail > SC -> pass > EN -> Pass -- 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-3741) Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Min Chen resolved CLOUDSTACK-3741.
--
Resolution: Fixed
> Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
> --
>
> Key: CLOUDSTACK-3741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3741
> 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: Chandan Purushothama
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.0
>
>
>
> Steps to Reproduce:
>
> 1. On an Advanced Zone KVM Setup, Create a Template from a Snapshot of a ROOT
> disk of a linux VM.
>
> Observations:
>
> ---
> Management Server Log:
> ---
> Exception:
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-1039532081: Processing: { Ans: , MgmtId:
> 7471666038533, via: 3, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.io.FileNotFoundException:
>
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)","wait":0}}] }
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Seq
> 3-1039532081: Received: { Ans: , MgmtId: 7471666038533, via: 3, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-23 10:54:51,508 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Failed to
> create templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> 2013-07-23 10:54:51,620 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-23 10:54:51,640 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Complete
> async job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> Create Template Job Information:
> [root@asfmgmt ~]# grep -i "job-44"
> /var/log/cloudstack/management/management-server.log
> 2013-07-23 10:53:40,592 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-44 = [
> 5439372e-dfea-42fc-875a-8c16c1588914 ], details: AsyncJobVO {id:44, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 203,
> cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"280DZaDeR88+K7T7HCiizNFdVic\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","httpmethod":"GET","osTypeId":"00905de2-f320-11e2-b49d-06cba2000705","isPublic":"true","response":"json","id":"203","displayText":"TemplateFromHourlySnapshot","snapshotid":"98b9db98-ca0b-48ee-88e5-a1c97edd76f4","passwordEnabled":"fals
[jira] [Commented] (CLOUDSTACK-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719138#comment-13719138 ] ASF subversion and git services commented on CLOUDSTACK-3665: - Commit 2f1d4dd0ba894d1a418ac3c5c7812bde20fe18f5 in branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2f1d4dd ] CLOUDSTACK-3665:KVM specific issue in create volume from snapshot. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719139#comment-13719139 ] Min Chen commented on CLOUDSTACK-3665: -- Tested the fix on Xen and KVM. So Xen and KVM using NFS secondary storage and cluster wide primary storage should work now. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719137#comment-13719137 ] ASF subversion and git services commented on CLOUDSTACK-3665: - Commit 9f23b1c0c1407baf5b7b11ec1f3112ff7bba201b in branch refs/heads/4.2 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f23b1c ] CLOUDSTACK-3665:KVM specific issue in create volume from snapshot. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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-3741) Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719117#comment-13719117
]
ASF subversion and git services commented on CLOUDSTACK-3741:
-
Commit 44cae460147898186a56d7d022c734e3ac86e4dc in branch refs/heads/master
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=44cae46 ]
CLOUDSTACK-3741: generate template.properties so that KVM processor will
not fail with FileNotFound.
> Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
> --
>
> Key: CLOUDSTACK-3741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3741
> 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: Chandan Purushothama
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.0
>
>
>
> Steps to Reproduce:
>
> 1. On an Advanced Zone KVM Setup, Create a Template from a Snapshot of a ROOT
> disk of a linux VM.
>
> Observations:
>
> ---
> Management Server Log:
> ---
> Exception:
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-1039532081: Processing: { Ans: , MgmtId:
> 7471666038533, via: 3, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.io.FileNotFoundException:
>
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)","wait":0}}] }
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Seq
> 3-1039532081: Received: { Ans: , MgmtId: 7471666038533, via: 3, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-23 10:54:51,508 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Failed to
> create templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> 2013-07-23 10:54:51,620 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-23 10:54:51,640 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Complete
> async job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> Create Template Job Information:
> [root@asfmgmt ~]# grep -i "job-44"
> /var/log/cloudstack/management/management-server.log
> 2013-07-23 10:53:40,592 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-44 = [
> 5439372e-dfea-42fc-875a-8c16c1588914 ], details: AsyncJobVO {id:44, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 203,
> cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOri
[jira] [Commented] (CLOUDSTACK-3741) Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719115#comment-13719115
]
ASF subversion and git services commented on CLOUDSTACK-3741:
-
Commit bfe5a7c6ffb3b5d27d75f1d62da66c489f7b1fe7 in branch refs/heads/4.2 from
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bfe5a7c ]
CLOUDSTACK-3741: generate template.properties so that KVM processor will
not fail with FileNotFound.
> Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
> --
>
> Key: CLOUDSTACK-3741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3741
> 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: Chandan Purushothama
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.0
>
>
>
> Steps to Reproduce:
>
> 1. On an Advanced Zone KVM Setup, Create a Template from a Snapshot of a ROOT
> disk of a linux VM.
>
> Observations:
>
> ---
> Management Server Log:
> ---
> Exception:
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-1039532081: Processing: { Ans: , MgmtId:
> 7471666038533, via: 3, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.io.FileNotFoundException:
>
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)","wait":0}}] }
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Seq
> 3-1039532081: Received: { Ans: , MgmtId: 7471666038533, via: 3, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-23 10:54:51,508 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Failed to
> create templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> 2013-07-23 10:54:51,620 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-23 10:54:51,640 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Complete
> async job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> Create Template Job Information:
> [root@asfmgmt ~]# grep -i "job-44"
> /var/log/cloudstack/management/management-server.log
> 2013-07-23 10:53:40,592 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-44 = [
> 5439372e-dfea-42fc-875a-8c16c1588914 ], details: AsyncJobVO {id:44, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 203,
> cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOrigin
[jira] [Commented] (CLOUDSTACK-3388) No error message shows when a dedicate operation failed during the creation of a pod/cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719103#comment-13719103 ] ASF subversion and git services commented on CLOUDSTACK-3388: - Commit e8f1ce3aa4b5a30cc94626b16cbe1e5b002e2b37 in branch refs/heads/4.2 from [~isaacchi...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e8f1ce3 ] CLOUDSTACK-3388:No error message shows when a dedicate operation failed during the creation of a pod/cluster > No error message shows when a dedicate operation failed during the creation > of a pod/cluster > > > Key: CLOUDSTACK-3388 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3388 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI > Environment: Master >Reporter: Isaac Chiang >Assignee: Isaac Chiang > Labels: ui > Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png > > > There should be a error message when trying to make an explicit dedication to > a nonexistent account during the creation of a pod/cluster. -- 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-3700) The dedication process should be listed as a step through zone wizard
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719100#comment-13719100 ] ASF subversion and git services commented on CLOUDSTACK-3700: - Commit 4730e5593c71afe1e23297409c1b8029a8685bd7 in branch refs/heads/4.2 from [~isaacchi...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4730e55 ] CLOUDSTACK-3700: The dedication process should be listed as a step through zone wizard > The dedication process should be listed as a step through zone wizard > - > > Key: CLOUDSTACK-3700 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3700 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI > Environment: Master >Reporter: Isaac Chiang >Assignee: Isaac Chiang > Labels: ui > Fix For: 4.2.0 > > > In current UI code, the zone wizard isn't aware of the failure of zone > dedication. The dedication process should be listed as a step while the zone > wizard is setting up the entire zone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-3759:
Attachment: CLOUDSTACK-3759.rar
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --
>
> Key: CLOUDSTACK-3759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.2.0
> Environment: KVM
> Automation
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3759.rar
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> This issue is reproducible manually;
> Steps to reproduce
> --
> Step 1 : Create a VM
> Step 2 : Stop VM
> Step 3 : Create a volume and attach the volume to stoped VM
> Actual Result
> Volume attachment failed;
> Observed below error automation test log
>
> attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py",
> line 611, in test_06_deploy_startvm_attach_detach
> self.fail("Attach volume failed!")
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> Attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang Wang updated CLOUDSTACK-3759:
--
Assignee: Fang Wang
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --
>
> Key: CLOUDSTACK-3759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.2.0
> Environment: KVM
> Automation
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> This issue is reproducible manually;
> Steps to reproduce
> --
> Step 1 : Create a VM
> Step 2 : Stop VM
> Step 3 : Create a volume and attach the volume to stoped VM
> Actual Result
> Volume attachment failed;
> Observed below error automation test log
>
> attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py",
> line 611, in test_06_deploy_startvm_attach_detach
> self.fail("Attach volume failed!")
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> Attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2904) After volume migration on Vmware, taking a snapshot, and then volume migration fails on this new volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fang Wang updated CLOUDSTACK-2904: -- Assignee: Sateesh Chodapuneedi (was: Fang Wang) > After volume migration on Vmware, taking a snapshot, and then volume > migration fails on this new volume > --- > > Key: CLOUDSTACK-2904 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2904 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: master build, or vmware-storage-migration branch with > Vmware host >Reporter: Fang Wang >Assignee: Sateesh Chodapuneedi >Priority: Critical > > Create a simple VM with a root volume. > Migrate the root volume to another primary storage. > we see four vmdk files getting created in the VM folder on the new primary. > Two are uuid-delta.vmdk and uuid.vmdk style files. The other two are the > ROOT-x-y-delta.vmdk and ROOT-x-y.vmdk files. > take a snapshot of the root volume via the cloudstack GUI. What we see is > that the ROOT-x-y* files are getting deleted from the VM folder in the new > primary. Additionally, the VM’s root disk is getting changed to the other > uuid.vmdk file. > when we now attempt to migrate this volume again, it will fail saying that it > cannot find the ROOT-x-y disk. -- 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-3788) [KVM] Weekly Snapshot got stuck in "Allocated State"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fang Wang updated CLOUDSTACK-3788: -- Assignee: Fang Wang > [KVM] Weekly Snapshot got stuck in "Allocated State" > > > Key: CLOUDSTACK-3788 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3788 > 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: Chandan Purushothama >Assignee: Fang Wang >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.2013-07-23.gz, > mysql_cloudstack_dump.zip > > > Weekly Snapshot stuck in Allocated State: > mysql> select * from snapshots where name like > "Atoms-VM-1_ROOT-6_20130723235146"; > ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+ > | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id > | status| path | name | uuid >| snapshot_type | type_description | size | created >| removed | backup_snap_id | swift_id | sechost_id | prev_snap_id | > hypervisor_type | version | s3_id | > ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+ > | 24 | 1 | 3 | 1 | 6 |1 > | Destroyed | NULL | Atoms-VM-1_ROOT-6_20130723235146 | > 08a0d2aa-9635-41cd-ba54-5367303bceac | 3 | HOURLY | > 147456 | 2013-07-23 23:51:46 | NULL| NULL | NULL | > NULL | NULL | KVM | 2.2 | NULL | > | 25 | 1 | 3 | 1 | 6 |1 > | Allocated | NULL | Atoms-VM-1_ROOT-6_20130723235146 | > 1e24a056-be38-4b55-845b-a5672b9fa93c | 5 | WEEKLY | > 147456 | 2013-07-23 23:51:46 | NULL| NULL | NULL | > NULL | NULL | KVM | 2.2 | NULL | > ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+ > 2 rows in set (0.04 sec) > Attached Management Server logs and cloud database 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] [Updated] (CLOUDSTACK-3677) VMSnapshot on XenServer: RevertToVMSnapshot failed to revert VM to Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-3677:
-
Priority: Critical (was: Major)
> VMSnapshot on XenServer: RevertToVMSnapshot failed to revert VM to Snapshot
> ---
>
> Key: CLOUDSTACK-3677
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3677
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, XenServer
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip, xensource.zip
>
>
> Setup: Advanced Zone, XenServer 6.2
> =
> Steps to Reproduce:
> =
> 1. Deploy Vm. Attach muiltiple data disks to this VM.
> 2. Log in to the Vm and create few directories and files on the root volume.
> Create few more directories on each of the data disks.
> 3. Stop the VM. Create VMSnapshot for this VM with "vm_snapshot_type" set to
> "Disk".
> 4. Revert to the VMSnapshot and observe the failure
>
> Management Server Log:
>
> 2013-07-19 13:50:52,918 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===START=== 10.252.121.104 -- GET
> command=revertToVMSnapshot&vmsnapshotid=b7832d89-de57-4f94-b1e9-a93e7975ef0e&response=json&sessionkey=UXTrrcPGpFO1xH15V%2FhI8SByX1c%3D&_=1374267435422
> 2013-07-19 13:50:52,943 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-20:null) submit async job-45 = [
> e8ffdd72-0c4d-4b47-8106-7181b54ac06c ], details: AsyncJobVO {id:45, userId:
> 4, accountId: 4, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","sessionkey":"UXTrrcPGpFO1xH15V/hI8SByX1c\u003d","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"4","httpmethod":"GET","_":"1374267435422","vmsnapshotid":"b7832d89-de57-4f94-b1e9-a93e7975ef0e","ctxAccountId":"4","ctxStartEventId":"192"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7471666038533,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-19 13:50:52,945 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===END=== 10.252.121.104 -- GET
> command=revertToVMSnapshot&vmsnapshotid=b7832d89-de57-4f94-b1e9-a93e7975ef0e&response=json&sessionkey=UXTrrcPGpFO1xH15V%2FhI8SByX1c%3D&_=1374267435422
> 2013-07-19 13:50:52,947 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Executing
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd for
> job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]
> 2013-07-19 13:50:52,966 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Access to
> com.cloud.vm.snapshot.VMSnapshotVO$$EnhancerByCGLIB$$956acea7@7ece4609
> granted to Acct[4-atoms] by DomainChecker_EnhancerByCloudStack_2fa3ef51
> 2013-07-19 13:50:52,985 DEBUG [agent.transport.Request]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Seq
> 4-110170392: Sending { Cmd , MgmtId: 7471666038533, via: 4, Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"volumeTOs":[{"id":13,"name":"New
> Volume
> 1","path":"67e644ac-5792-4007-9eb6-ac298e0c42f3","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":2},{"id":14,"name":"ROOT-11","path":"374a56ac-19a1-4885-8a95-51142be064c1","size":8589934592,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":0},{"id":15,"name":"DATA-11","path":"5c0d41f7-dcab-4a51-aaa8-36729fb4c338","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":1}],"target":{"id":4,"snapshotName":"i-4-11-VMSNAPSHOT_VS_20130719203659","type":"Disk","createTime":137426622,"current":false,"description":"VM-Snapshot-5"},"vmName":"i-4-11-VMSNAPSHOT","guestOSType":"CentOS
> 5.3 (64-bit)","wait":0}}] }
> 2013-07-19 13:50:52,986 DEBUG [agent.transport.Request]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Seq
> 4-110170392: Executing: { Cmd , MgmtId: 7471666038533, via: 4, Ver: v1,
> Flags: 100011,
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"volumeTOs":[{"id":13,"name":"New
> Volume
> 1","path":"67e644ac-5792-4007-9eb6-ac298e0c42f3",
[jira] [Commented] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719021#comment-13719021 ] Animesh Chaturvedi commented on CLOUDSTACK-3612: Chandan can you check off which ones are done and log separate defects for remaining items? > 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded > Setup > --- > > Key: CLOUDSTACK-3612 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3612 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Priority: Critical > Fix For: 4.2.0 > > > Table 1: baremetal_dhcp_devices > On ASF 4.2 Setup: > `nsp_id` bigint(20) UNSIGNED DEFAULT NULL, > `pod_id` bigint(20) UNSIGNED DEFAULT NULL, > `device_type` varchar(255) DEFAULT NULL, > `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL, > `host_id` bigint(20) UNSIGNED DEFAULT NULL, > On the 4.2 Upgraded Setup: > `nsp_id` bigint(20) UNSIGNED NOT NULL, > `pod_id` bigint(20) UNSIGNED NOT NULL, > `device_type` varchar(255) NOT NULL, > `physical_network_id` bigint(20) UNSIGNED NOT NULL, > `host_id` bigint(20) UNSIGNED NOT NULL, > Table 2: baremetal_pxe_devices > On ASF 4.2 Setup: > `nsp_id` bigint(20) UNSIGNED DEFAULT NULL, > `device_type` varchar(255) DEFAULT NULL, > `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL, > `host_id` bigint(20) UNSIGNED DEFAULT NULL, > On the 4.2 Upgraded Setup: > `nsp_id` bigint(20) UNSIGNED NOT NULL, > `device_type` varchar(255) NOT NULL, > `physical_network_id` bigint(20) UNSIGNED NOT NULL, > `host_id` bigint(20) UNSIGNED NOT NULL, > Table 3: netscaler_pod_ref > On ASF 4.2 Setup: > Present on the Setup > Missing on the Upgraded Setup. > Table 4: nicira_nvp_nic_map > On ASF 4.2 Setup: > Constraint: > ALTER TABLE `cloud`.`nicira_nvp_nic_map` ADD CONSTRAINT > `fk_nicira_nvp_nic_map__nic` > FOREIGN KEY ( `nic` ) REFERENCES `nics` ( `uuid` ) ON DELETE CASCADE; > On the 4.2 Upgraded Setup: > No such constraint > Table 5: router_network_ref > On ASF 4.2 Setup: > Constraint: > ALTER TABLE `cloud`.`router_network_ref` ADD CONSTRAINT > `fk_router_network_ref__router_id` > FOREIGN KEY ( `router_id` ) REFERENCES `domain_router` ( `id` ) ON DELETE > CASCADE; > On the 4.2 Upgraded Setup: > No such constraint > Table 6: sync_queue > On ASF 4.2 Setup: > `queue_size` smallint(6) NOT NULL DEFAULT '0', > `queue_size_limit` smallint(6) NOT NULL DEFAULT '1', > On the 4.2 Upgraded Setup: > `queue_size` smallint(6) DEFAULT '0', > `queue_size_limit` smallint(6) DEFAULT '1', > Table 7: usage_event > On ASF 4.2 Setup: > no virtual_size column > On the 4.2 Upgraded Setup: > `virtual_size` bigint(20) UNSIGNED DEFAULT NULL, > Table 8: volumes > On ASF 4.2 Setup: > no iso_id column > On the 4.2 Upgraded Setup: > `iso_id` bigint(20) UNSIGNED DEFAULT 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
[jira] [Created] (CLOUDSTACK-3792) [Automation] Test case test_internal_lb.TestInternalLb.test_internallb failed in VMware
Rayees Namathponnan created CLOUDSTACK-3792:
---
Summary: [Automation] Test case
test_internal_lb.TestInternalLb.test_internallb failed in VMware
Key: CLOUDSTACK-3792
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3792
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation
Affects Versions: 4.2.0
Environment: Automation
VMware
Reporter: Rayees Namathponnan
Fix For: 4.2.0
Test case test_internal_lb.TestInternalLb.test_internallb failed in VMware,
observed below error in automation log; need more analysis on this defect
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Failed
to add specified loadbalancerruleid for vms [45]'}
>> begin captured logging <<
testclient.testcase.TestInternalLb: DEBUG: Successfully created account:
test-OT0WV0, id:e3f37887-d808-4be0-b0b6-96851e943910
testclient.testcase.TestInternalLb: DEBUG: Network
9a675d91-947f-40e9-bb39-8e9db8b17cac created in VPC
b30322b2-7c08-4c59-8f48-0d5d5f3b7eb9
testclient.testcase.TestInternalLb: DEBUG: VM
76b8096a-f525-424f-8b7c-5e40242bac94 deployed in VPC
b30322b2-7c08-4c59-8f48-0d5d5f3b7eb9
- >> end captured logging << -
Stacktrace
File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
testMethod()
File "/data/Repo2/qa/cloudstack/test/integration/smoke/test_internal_lb.py",
line 173, in test_internallb
applb.assign(self.apiclient, vms=[vm])
File "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py",
line 1543, in assign
apiclient.assignToLoadBalancerRule(cmd)
File
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
line 994, in assignToLoadBalancerRule
response = self.connection.marvin_request(command, response_type=response,
method=method)
File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
line 230, in marvin_request
response = self.poll(asyncJobId, response_type)
File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
line 91, in poll
"asyncquery", asyncResonse.jobresult)
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Failed
to add specified loadbalancerruleid for vms [45]'}
--
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-3792) [Automation] Test case test_internal_lb.TestInternalLb.test_internallb failed in VMware
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-3792:
Component/s: API
> [Automation] Test case test_internal_lb.TestInternalLb.test_internallb failed
> in VMware
> ---
>
> Key: CLOUDSTACK-3792
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3792
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Automation
>Affects Versions: 4.2.0
> Environment: Automation
> VMware
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
>
> Test case test_internal_lb.TestInternalLb.test_internallb failed in VMware,
> observed below error in automation log; need more analysis on this defect
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Failed to add specified loadbalancerruleid for vms [45]'}
> >> begin captured logging <<
> testclient.testcase.TestInternalLb: DEBUG: Successfully created account:
> test-OT0WV0, id:e3f37887-d808-4be0-b0b6-96851e943910
> testclient.testcase.TestInternalLb: DEBUG: Network
> 9a675d91-947f-40e9-bb39-8e9db8b17cac created in VPC
> b30322b2-7c08-4c59-8f48-0d5d5f3b7eb9
> testclient.testcase.TestInternalLb: DEBUG: VM
> 76b8096a-f525-424f-8b7c-5e40242bac94 deployed in VPC
> b30322b2-7c08-4c59-8f48-0d5d5f3b7eb9
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/data/Repo2/qa/cloudstack/test/integration/smoke/test_internal_lb.py", line
> 173, in test_internallb
> applb.assign(self.apiclient, vms=[vm])
> File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line
> 1543, in assign
> apiclient.assignToLoadBalancerRule(cmd)
> File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 994, in assignToLoadBalancerRule
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line
> 230, in marvin_request
> response = self.poll(asyncJobId, response_type)
> File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line
> 91, in poll
> "asyncquery", asyncResonse.jobresult)
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Failed to add specified loadbalancerruleid for vms [45]'}
--
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-3289) StorageSubsystem: cannot add image store of a different provider in a different zone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719014#comment-13719014
]
Animesh Chaturvedi commented on CLOUDSTACK-3289:
Prasanna can you also mark it as Improvement
> StorageSubsystem: cannot add image store of a different provider in a
> different zone
>
>
> Key: CLOUDSTACK-3289
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3289
> 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: Future
>
>
> The storage code right now restricts usage of multiple image store providers
> in the same zone. But it restricts this even when the image store may be in a
> different zone/region.
> From StorageManagerImpl.java:
> // check if we have already image stores from other different
> providers,
> // we currently are not supporting image stores from different
> // providers co-existing
> List imageStores = _imageStoreDao.listImageStores();
> for (ImageStoreVO store : imageStores) {
> if (!store.getProviderName().equalsIgnoreCase(providerName)) {
> throw new InvalidParameterValueException("You can only add
> new image stores from the same provider " + store.getProviderName()
> + " already added");
> }
> }
> search criteria lists all add images stores:
> @Override
> public List listImageStores() {
> SearchCriteria sc = createSearchCriteria();
> sc.addAnd("role", SearchCriteria.Op.EQ, DataStoreRole.Image);
> return listBy(sc);
> }
--
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-3725) [Automation] BVT Volume test case need to wait for vm to up before attaching and dettaching disk
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-3725: --- Assignee: Rayees Namathponnan > [Automation] BVT Volume test case need to wait for vm to up before attaching > and dettaching disk > - > > Key: CLOUDSTACK-3725 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3725 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Test >Affects Versions: 4.2.0 > Environment: Automation >Reporter: Rayees Namathponnan >Assignee: Rayees Namathponnan >Priority: Blocker > Fix For: 4.2.0 > > > Below two test case failing from BVT > integration.smoke.test_volumes.TestVolumes.test_08_resize_volume > integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume > WE need to updated this test case; test case need to wait vm to running state > before attaching 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-1019) Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719002#comment-13719002 ] Animesh Chaturvedi commented on CLOUDSTACK-1019: I will move it out to 4.3 if no one claims it by 7/29 > Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do > the upgrades > > > Key: CLOUDSTACK-1019 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1019 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: branch: javelin (or master if merge happens) >Reporter: Rohit Yadav >Priority: Critical > Fix For: Future > > > A new tool/class called DatabaseCreator is introduced in javelin, the idea is > that DatabaseCreator can be used by mgmt server, cloud-setup-database script, > maven (developer/pom.xml) and possibly by plugins in future to: > 1. Initialize database using db.properties file > 2. Run sql scripts > 3. Run database upgrades > Presently, this has been fixed in javelin, in cloud-server and is used by > maven to deploydb, the task is to fix that same for cloud-setup-databases. > Current help doc, usage and options: > DatabaseCreator creates the database schema by removing the > previous schema, creating the schema, and running > through the database updaters. > Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] > [database upgrade class] > Options: >--database=a,b comma separate databases to initialize, use the db name in > db.properties defined as db.xyz.host, xyz should be passed >--rootpassword=password, by default it will try with an empty password >--dry or -d, this would not run any process, just does a dry run >--verbose or -v to print running sql commands, by default it won't print > them >--help or -h for help > The issue now is to make cloudstack-setup-databases use DatabaseCreator and > remove db upgrading logic from mgmt server and move it to DatabaseCreator. > Let's talk about the present database deployment and the issues: > - We've two different routes to deploydb, for developers it's > DatabaseCreator now (used to be a maven plugin), for sysadmins it's > cloudstack-setup-database > - Upgrades are done by mgmt server, this has issues when there is a > clustered mgmt server, i.e. multiple mgmt servers sharing the same > database, we do upgrade by: > a. Turn down one mgmt server, upgrade it, start it. This mgmt > server checks in db the cloudstack version, upgrades the db > b. Sysadmins meanwhile upgrades all the other mgmt server > c. When all mgmt servers are upgraded, they ask the cluster > manager to run the cleanup. The whole process is automated, an error > can introduce whole sets of issues. > How will DatabaseCreator help: > - Would give a single tool used by both developer and sysadmins. Agony > of the sysadmins would be much better understood by developers. > Sysadmins would still use cloudstack-setup-database which would be > wrapper around DatabaseCreator > - Upgrade would be driven by sysadmin, giving them explicit power to > backup database, deploy etc. For example in case of multiple > (clustered) mgmt server, the upgrade would be like: >a. Upgrade database using DatabaseCreator, this step do a backup > and would just upgrade the db such that it's backward compatible to > the old database and old mgmt servers can still run on it. When this > succeeds, system can proceed. Transaction update would provide a way > to rollback. >b. Sysadmins would stop, upgrade and start mgmt server one by one. >c. Sysadmins would run the final cleanup operation, this would do a > final round of cleaning up. If everything goes well, they just did a > rolling CloudStack upgrade with little to no downtime (no downtime as > at least one mgmt server was running :) > TODOs for 4.1: > - We stick to major db version as 4.0, create-schema is not touched > unless it's a major version. So, next change is to be done only for > 5.0. > - We move out any 4.1 changes to 4041 upgrade sql file and have a > upgrade path (a upgrading logic/class). > - Fix cloudstack-setup-databases, fix packaging. > For 4.2/future: > - Refactor out code that does upgrading in mgmt server to a separate > artifact which would also have DatabaseCreator. > - Implement tool so it supports the operations as discussed above > - Replace the current pythonic implementation with DatabaseCreator, > have same routes for both developers and sysadmins > NOTE TO DEVELOPERS: > - WE NEVER CHANGE create-schema.sql > - WE TEST AND IMPLEMENT UPGRADE PATHS from version a to version b > - WE CLEANUP PROPERL
[jira] [Assigned] (CLOUDSTACK-2397) Not able to deploy a Vm with userdata in Shared network/Isolated Network.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheng Yang reassigned CLOUDSTACK-2397:
--
Assignee: Sheng Yang (was: Venkata Siva Vijayendra Bhamidipati)
> Not able to deploy a Vm with userdata in Shared network/Isolated Network.
> -
>
> Key: CLOUDSTACK-2397
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2397
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, XenServer
>Affects Versions: 4.2.0
> Environment: Build from pvlan
>Reporter: Sangeetha Hariharan
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.rar
>
>
> Steps to reproduce the problem:
> Advanced zone with Xen 6.1 hosts.
> Create a Shared network by passing private Vlan.
> Deploy a Vm in this network by passing userdata.
> Vm deployment errors out.
> GET
> command=deployVirtualMachine&zoneId=b5b71f7b-19a4-4f32-9512-d9b0eac382f3&templateId=b79f666e-b760-11e2-a38a-06f4b42b&hypervisor=XenServer&serviceOfferingId=4480e764-0d39-4950-86a9-a422e7ae3b7d&networkIds=a2fb9fda-f6a1-4348-beb1-4e29367b3dbd&displayname=yo-userdata&name=yo-userdata&response=json&sessionkey=LqAvWj%2BQ0xeg3eqoKXMhOoA%2B53E%3D&userdata=Y2F0Y2ggbWUgaWYgeW91IGNhbg==
> 200 { "deployvirtualmachineresponse" :
> {"id":"05f1426d-6650-470f-8f6e-36b18b3bcd8c","jobid":"e3bd77a2-aca2-4c39-b85f-9f928c7af000"}
> }
> Following exception seen in management server log:
> 2013-05-08 13:47:27,815 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-39) Seq 1-1674709490: Executing: { Cmd , MgmtId:
> 7647994577963, via: 1, Ver: v1, Flags: 100111,
> [{"routing.SavePasswordCommand":{"password":"fnirq_cnffjbeq","vmIpAddress":"10.223.161.116","vmName":"yo-userdata","accessDetails":{"router.guest.ip":"10.223.161.110","zone.network.type":"Advanced","router.ip":"169.254.0.235","router.name":"r-13-VM"},"wait":0}},{"routing.VmDataCommand":{"vmIpAddress":"10.223.161.116","vmName":"yo-userdata","accessDetails":{"router.guest.ip":"10.223.161.110","zone.network.type":"Advanced","router.ip":"169.254.0.235","router.name":"r-13-VM"},"wait":0}}]
> }
> 2013-05-08 13:47:27,815 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-164:null) Seq 1-1674709490: Executing request
> 2013-05-08 13:47:29,899 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-05-08 13:47:30,039 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-05-08 13:47:33,199 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-08 13:47:33,200 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-08 13:47:33,280 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-05-08 13:47:33,281 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-05-08 13:47:37,894 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-164:null) Seq 1-1674709490: Response Received:
> 2013-05-08 13:47:37,895 DEBUG [agent.transport.Request]
> (DirectAgent-164:null) Seq 1-1674709490: Processing: { Ans: , MgmtId:
> 7647994577963, via: 1, Ver: v1, Flags: 110,
> [{"Answer":{"result":true,"wait":0}},{"Answer":{"result":false,"details":"vm_data
> failed","wait":0}}] }
> 2013-05-08 13:47:37,895 DEBUG [agent.manager.AgentAttache]
> (DirectAgent-164:null) Seq 1-1674709490: No more commands found
> 2013-05-08 13:47:37,895 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-39) Seq 1-1674709490: Received: { Ans: , MgmtId:
> 7647994577963, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
> 2013-05-08 13:47:37,895 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-18:job-39) Unable to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unreachable: Unable to apply userdata and password entry on router
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3496)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2790)
> at
> com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:861)
> at
> com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManage
[jira] [Updated] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-3759:
Description:
Test cases failed from integration.component.test_stopped_vm.TestDeployVM
This issue is reproducible manually;
Steps to reproduce
--
Step 1 : Create a VM
Step 2 : Stop VM
Step 3 : Create a volume and attach the volume to stoped VM
Actual Result
Volume attachment failed;
Observed below error automation test log
attach volume failed!
>> begin captured logging <<
testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
c90e1365-702a-4a68-86d6-f5d75437b623
- >> end captured logging << -
Stacktrace
File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
testMethod()
File
"/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py", line
611, in test_06_deploy_startvm_attach_detach
self.fail("Attach volume failed!")
File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
raise self.failureException(msg)
Attach volume failed!
>> begin captured logging <<
testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
c90e1365-702a-4a68-86d6-f5d75437b623
- >> end captured logging << -
was:
Test cases failed from integration.component.test_stopped_vm.TestDeployVM
Look like, its a product issue; need more analysis
ttach volume failed!
>> begin captured logging <<
testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
c90e1365-702a-4a68-86d6-f5d75437b623
- >> end captured logging << -
Stacktrace
File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
testMethod()
File
"/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py", line
611, in test_06_deploy_startvm_attach_detach
self.fail("Attach volume failed!")
File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
raise self.failureException(msg)
Attach volume failed!
>> begin captured logging <<
testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
c90e1365-702a-4a68-86d6-f5d75437b623
- >> end captured logging << -
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --
>
> Key: CLOUDSTACK-3759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.2.0
> Environment: KVM
>
[jira] [Resolved] (CLOUDSTACK-3681) [Automation][BVT][VMWare]Failed to delete template during first time
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-3681.
---
Resolution: Fixed
> [Automation][BVT][VMWare]Failed to delete template during first time
> -
>
> Key: CLOUDSTACK-3681
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3681
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
>Affects Versions: 4.2.0
> Environment: 4.2
> Vmware
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3681.rar
>
>
> BVT tets cases
> integration.smoke.test_templates.TestCreateTemplate.test_01_create_template
> failed with latest run
> Steps to reproduce
> Step 1 : Create a template "TemplateDeleteTest" from root volume
> Step 2 : Delete template "TemplateDeleteTest"
> Result
> Delete template failed, please the attached log (job-39)
> 013-07-19 20:58:02,470 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Sending { Cmd , Mgmt
> Id: 90928106758026, via: 8, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DeleteCommand":{"data":{"org.apache.cloudstack.storage.to.TemplateObj
> ectTO":{"path":"22d8d284a-d237-379b-af73-8631ac0d298b","uuid":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","id":202,"format":"OVA","accountId":2,"hvm":true,"displayText
> ":"TemplateDeleteTest","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1","_role":"I
> mage"}},"name":"22d8d284a-d237-379b-af73-8631ac0d298b"}},"wait":0}}] }
> 2013-07-19 20:58:02,766 DEBUG [agent.transport.Request]
> (AgentManager-Handler-12:null) Seq 8-640811237: Processing: { Ans: , MgmtId:
> 90928106758026, via: 8, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Unable to delete
> file template under Template path 22d8d284a-d237-379b-af73-8631ac0d298b
> ","wait":0}}] }
> 2013-07-19 20:58:02,767 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Received: { Ans: , M
> gmtId: 90928106758026, via: 8, Ver: v1, Flags: 10, { Answer } }
> 2013-07-19 20:58:02,781 WARN [cloud.template.HypervisorTemplateAdapter]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Failed to
> delete the
> template Tmpl[202-OVA-22d8d284a-d237-379b-af73-8631ac0d298b from the image
> store: nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1
> due to: Un
> able to delete file template under Template path
> 22d8d284a-d237-379b-af73-8631ac0d298b
> 2013-07-19 20:58:02,811 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Complete
> async job-39 = [ d534
> 1b65-45a2-45e7-bb60-58043720da15 ], jobStatus: 2, resultCode: 530, result:
> Error Code: 530 Error text: Failed to delete template
> Step 3 : Delete template "TemplateDeleteTest" again
> Result
> Template got deleted and observed below log in MS
> 2013-07-19 20:59:03,818 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
> ===START=== 10.216.51.171 -- GET
> command=deleteTemplate&id=e0d4421d-8bf5-4cb4-9792-5
> af13563ad76&zoneid=34e5d608-9f00-45b7-b808-4a4c47592636&response=json&sessionkey=kzg0H6VMwJZ1qk59pvUJssmIaaw%3D&_=1374293513274
> 2013-07-19 20:59:03,859 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-7:null) submit async job-40 = [
> b2a3496b-aac8-448d-8576-adbd84d0d77a ], details: As
> yncJobVO {id:40, userId: 2, accountId: 2, sessionKey: null, instanceType:
> Template, instanceId: 202, cmd:
> org.apache.cloudstack.api.command.user.template.DeleteTe
> mplateCmd, cmdOriginator: null, cmdInfo:
> {"response":"json","id":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","sessionkey":"kzg0H6VMwJZ1qk59pvUJssmIaaw\u003d","cmdEvent
> Type":"TEMPLATE.DELETE","ctxUserId":"2","zoneid":"34e5d608-9f00-45b7-b808-4a4c47592636","httpmethod":"GET","_":"1374293513274","ctxAccountId":"2","ctxStartEventId
> ":"167"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90928106758026,
> completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-19 20:59:03,861 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
> ===END=== 10.216.51.171 -- GET
> command=deleteTemplate&id=e0d4421d-8bf5-4cb4-9792-5af13563ad76&zoneid=34e5d608-9f00-45b7-b808-4a4c47592636&response=json&sessionkey=kzg0H6VMwJZ1qk59pvUJssmIaaw%3D&_=1374293513274
> 2013-07-19 20:59:03,862 DEBUG [cloud.asyn
[jira] [Commented] (CLOUDSTACK-3681) [Automation][BVT][VMWare]Failed to delete template during first time
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718976#comment-13718976
]
ASF subversion and git services commented on CLOUDSTACK-3681:
-
Commit bfe30cd2e31906365a306d87fe331ccdcec5c33c in branch refs/heads/4.2 from
[~edison]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bfe30cd ]
CLOUDSTACK-3681: fix bunch of bugs related to vmware, regarding to snapshot
> [Automation][BVT][VMWare]Failed to delete template during first time
> -
>
> Key: CLOUDSTACK-3681
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3681
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template, VMware
>Affects Versions: 4.2.0
> Environment: 4.2
> Vmware
>Reporter: Rayees Namathponnan
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3681.rar
>
>
> BVT tets cases
> integration.smoke.test_templates.TestCreateTemplate.test_01_create_template
> failed with latest run
> Steps to reproduce
> Step 1 : Create a template "TemplateDeleteTest" from root volume
> Step 2 : Delete template "TemplateDeleteTest"
> Result
> Delete template failed, please the attached log (job-39)
> 013-07-19 20:58:02,470 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Sending { Cmd , Mgmt
> Id: 90928106758026, via: 8, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DeleteCommand":{"data":{"org.apache.cloudstack.storage.to.TemplateObj
> ectTO":{"path":"22d8d284a-d237-379b-af73-8631ac0d298b","uuid":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","id":202,"format":"OVA","accountId":2,"hvm":true,"displayText
> ":"TemplateDeleteTest","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1","_role":"I
> mage"}},"name":"22d8d284a-d237-379b-af73-8631ac0d298b"}},"wait":0}}] }
> 2013-07-19 20:58:02,766 DEBUG [agent.transport.Request]
> (AgentManager-Handler-12:null) Seq 8-640811237: Processing: { Ans: , MgmtId:
> 90928106758026, via: 8, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"Unable to delete
> file template under Template path 22d8d284a-d237-379b-af73-8631ac0d298b
> ","wait":0}}] }
> 2013-07-19 20:58:02,767 DEBUG [agent.transport.Request]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Seq
> 8-640811237: Received: { Ans: , M
> gmtId: 90928106758026, via: 8, Ver: v1, Flags: 10, { Answer } }
> 2013-07-19 20:58:02,781 WARN [cloud.template.HypervisorTemplateAdapter]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Failed to
> delete the
> template Tmpl[202-OVA-22d8d284a-d237-379b-af73-8631ac0d298b from the image
> store: nfs://10.223.110.232:/export/home/automation/SC-CLOUD-QA03/secondary1
> due to: Un
> able to delete file template under Template path
> 22d8d284a-d237-379b-af73-8631ac0d298b
> 2013-07-19 20:58:02,811 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-45:job-39 = [ d5341b65-45a2-45e7-bb60-58043720da15 ]) Complete
> async job-39 = [ d534
> 1b65-45a2-45e7-bb60-58043720da15 ], jobStatus: 2, resultCode: 530, result:
> Error Code: 530 Error text: Failed to delete template
> Step 3 : Delete template "TemplateDeleteTest" again
> Result
> Template got deleted and observed below log in MS
> 2013-07-19 20:59:03,818 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
> ===START=== 10.216.51.171 -- GET
> command=deleteTemplate&id=e0d4421d-8bf5-4cb4-9792-5
> af13563ad76&zoneid=34e5d608-9f00-45b7-b808-4a4c47592636&response=json&sessionkey=kzg0H6VMwJZ1qk59pvUJssmIaaw%3D&_=1374293513274
> 2013-07-19 20:59:03,859 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-7:null) submit async job-40 = [
> b2a3496b-aac8-448d-8576-adbd84d0d77a ], details: As
> yncJobVO {id:40, userId: 2, accountId: 2, sessionKey: null, instanceType:
> Template, instanceId: 202, cmd:
> org.apache.cloudstack.api.command.user.template.DeleteTe
> mplateCmd, cmdOriginator: null, cmdInfo:
> {"response":"json","id":"e0d4421d-8bf5-4cb4-9792-5af13563ad76","sessionkey":"kzg0H6VMwJZ1qk59pvUJssmIaaw\u003d","cmdEvent
> Type":"TEMPLATE.DELETE","ctxUserId":"2","zoneid":"34e5d608-9f00-45b7-b808-4a4c47592636","httpmethod":"GET","_":"1374293513274","ctxAccountId":"2","ctxStartEventId
> ":"167"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90928106758026,
> completeMsid:
> null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-19
[jira] [Updated] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rayees Namathponnan updated CLOUDSTACK-3759:
Summary: [Automation] Failed to attach volume to VM, while vm are in
stopped state (was: [Automation] test_stopped_vm.py test case failed while
attaching volume in KVM)
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --
>
> Key: CLOUDSTACK-3759
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, Test
>Affects Versions: 4.2.0
> Environment: KVM
> Automation
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> Look like, its a product issue; need more analysis
> ttach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
> Stacktrace
> File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
> testMethod()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py",
> line 611, in test_06_deploy_startvm_attach_detach
> self.fail("Attach volume failed!")
> File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
> raise self.failureException(msg)
> Attach volume failed!
> >> begin captured logging <<
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response
> for virtual machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account:
> test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance:
> c90e1365-702a-4a68-86d6-f5d75437b623
> - >> end captured logging << -
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718964#comment-13718964
]
Fang Wang commented on CLOUDSTACK-2725:
---
Delay will not help. Delay is to make sure the VM are in the correct state,
which is already checked in the code.
We should add tis in the doc, so that with this libvirt exception, users know
to check the hotplug on the VM.
> [Automation] Re-attaching volume on VM failing in KVM
> -
>
> Key: CLOUDSTACK-2725
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
> 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: Automation environment KVM
> Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2725.rar
>
>
> Below two test case failing from BVT
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
> integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
> Steps to reproduce
> Step 1 : Create an account, service offering, create volume, create VM
> Step 2 : Attach volume to VM ,
> Step 3 : Detach volume
> Step 4 : Attach volume to VM again
> Actual result
> Attachment failed with below error
> 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
> (Job-Executor-98:job-1246) Seq 5-258539658: Rec
> eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
> AttachAnswer } }
> 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Unexpected e
> xception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
> TestDiskServ to VM: ce79edb6-
> a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
> unable to execute QEMU comman
> d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> at
> com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
> t(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
> 22)
> 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-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Complete asy
> nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
> text: Failed to attach volume
> : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
> org.libvirt.LibvirtException: internal erro
>
--
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-3667) [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to Exception: java.lang.Exception Message: secondary storage for dc 3 is not ready yet?
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Min Chen reassigned CLOUDSTACK-3667:
Assignee: Min Chen
> [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to
> Exception: java.lang.Exception Message: secondary storage for dc 3 is not
> ready yet?
> --
>
> Key: CLOUDSTACK-3667
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3667
> 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: Latest build from ACS 4.2 Branch.
> Zone: Advanced with VMWare cluster
> Storage: S3 and ISCSI(Primary)
>Reporter: Sanjeev N
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> [Object_Store_Refactor][VMWare] System VMs StartCommand failed due to
> Exception: java.lang.Exception Message: secondary storage for dc 3 is not
> ready yet?
> System VMs failed to start in case of VMWare cluster due to NULL in URL for
> S3 image store in image_store table with role Image.
> I looked at the following code in
> incubator-cloudstack/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
> :
> // prepare systemvm patch ISO
> if (vmSpec.getType() != VirtualMachine.Type.User) {
> // attach ISO (for patching of system VM)
> String secStoreUrl =
> mgr.getSecondaryStorageStoreUrl(Long.parseLong(_dcId));
> if(secStoreUrl == null) {
> String msg = "secondary storage for dc " + _dcId + " is
> not ready yet?";
> throw new Exception(msg);
> }
> mgr.prepareSecondaryStorageStore(secStoreUrl);
> Since secStoreUrl is matching with null , system vms starting failing with
> following exception message:
> java.lang.Exception: secondary storage for dc 3 is not ready yet?
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with vmware cluster
> 2.Add S3 image store and NFS cache store in the zone
> 3.Enable the zone
> Observations:
> ===
> 2013-07-19 11:50:10,861 WARN [vmware.resource.VmwareResource]
> (DirectAgent-97:10.147.40.13) StartCommand failed due to Exception:
> java.lang.Exception
> Message: secondary storage for dc 3 is not ready yet?
> java.lang.Exception: secondary storage for dc 3 is not ready yet?
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2628)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Enabled TRACE in log4j-cloud.xml and found the following sql statements
> executed before the exception:
> mysql> SELECT image_store.id, image_store.name, image_store.uuid,
> image_store.protocol, image_store.url, image_store.image_provider_name,
> image_store.data_center_id, image_store.scope, image_store.created,
> image_store.removed, image_store.role, image_store.parent,
> image_store.total_size, image_store.used_bytes FROM image_store WHERE
> image_store.role = 'Image' AND (image_store.scope = 'REGION' OR
> image_store.data_center_id = 3 ) AND image_store.removed IS NULL;
> +++--+--+--+-+++-+-+---++++
> | id | name | uuid | protocol | url |
> image_provider_name | data_center_id | scope | created | removed
> | role | parent | total_size | used_bytes |
> +++--+--+--+
[jira] [Commented] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718942#comment-13718942
]
edison su commented on CLOUDSTACK-3616:
---
Somehow the following code has problem, I don't know how it works before:
VmwareHypervisorHost hyperHost = hostService.getHyperHost(context, cmd);
VirtualMachineMO vmMo =
hyperHost.findVmOnHyperHost(volume.getVmName());
if (vmMo == null) {
if(s_logger.isDebugEnabled())
s_logger.debug("Unable to find the
owner VM for CreatePrivateTemplateFromVolumeCommand on host " +
hyperHost.getHyperHostName() + ", try within datacenter");
vmMo =
hyperHost.findVmOnPeerHyperHost(volume.getVmName());
if(vmMo == null) {
String msg = "Unable to find the owner
VM for volume operation. vm: " + volume.getVmName();
s_logger.error(msg);
throw new Exception(msg);
}
}
The vm is already stopped before creating template from volume, then above code
can't find the vm,
> [VMware] Failed to create template from volume (volume is created from
> snapshot of data volume)
> ---
>
> Key: CLOUDSTACK-3616
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller, VMware
>Affects Versions: 4.2.0
> Environment: VMware ESXi 5.0
> ACS master branch
>Reporter: Sateesh Chodapuneedi
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When tried to created template from volume created from snapshot we see
> following error in Cloudstack deployed over VMware.
> 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create template
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:258)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538)
> 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)
--
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-3651) Viewing Zone Details Causes an Error Dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-3651. -- Resolution: Fixed John, This bug is not producible in latest code of 4.2/master branch on my machine. I suspect it's caused by browser cache on your machine. Please clear your browser cache and try again. If you still see this bug after clearing browser cache, please provide your cloudstack web site URL/username/password on your machine. I'll take a look. Jessica > Viewing Zone Details Causes an Error Dialog > --- > > Key: CLOUDSTACK-3651 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3651 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: devcloud >Reporter: John Burwell >Assignee: Jessica Wang >Priority: Blocker > > When view zone details through the user interface, an error dialog with the > "Unknown API command: listVmwareDcs" message pops-up. The following are the > reproduction steps for this error: >1. Click "Infrastructure" in the sidebar >2. Click "Zones" in the main field >3. Click a zone in the table > These steps will cause the error dialog to displayed. -- 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-3729) Management Server stopped responding in a Multinode Management Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718895#comment-13718895 ] Alena Prokharchyk commented on CLOUDSTACK-3729: --- At the moment I can connect to both of your management servers with no problem, using both UI and API through port 8096 mysql> select service_ip from mshost; ++ | service_ip | ++ | 10.102.192.207 | | 10.102.192.117 | ++ > Management Server stopped responding in a Multinode Management Setup > > > Key: CLOUDSTACK-3729 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3729 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log, > MS2-apilog.log, MS2-management-server.log > > > Setup : Adv Configuration with VMWARE (Stadard vSwitch with 2 clusters ) & > Zone wide Primary storage > Steps: > 1. Configure Multinode Management setup (MS1 & MS2) > 2. Enable agent.lb.enabled to true > 3. DB is available locally to MS1 > 4. Create new accounts and deployed VM's > Observation: > 1. Tried to access Management server (MS1/MS2 ). Both servers are very slow > to respond and finally they stopped to respond > 2. Restarting Management servers also did not help here : > DB Statistics : > mysql> SHOW STATUS WHERE `variable_name` = 'Threads_connected'; > +---+---+ > | Variable_name | Value | > +---+---+ > | Threads_connected | 38| > +---+---+ > 1 row in set (0.00 sec) > mysql> show status like '%onn%'; > +--+---+ > | Variable_name| Value | > +--+---+ > | Aborted_connects | 6 | > | Connections | 1461 | > | Max_used_connections | 41| > | Ssl_client_connects | 0 | > | Ssl_connect_renegotiates | 0 | > | Ssl_finished_connects| 0 | > | Threads_connected| 38| > +--+---+ > 7 rows in set (0.00 sec) > [root@ec2 management]# mysqladmin -u root -ppassword processlist > +--+---+--+-+-+--+---+--+ > | Id | User | Host | db | Command | Time | State > | Info | > +--+---+--+-+-+--+---+--+ > | 35 | cloud | localhost:32999 | cloud | Sleep | 708 | > | | > | 40 | cloud | localhost:33004 | cloud | Sleep | 708 | > | | > | 43 | cloud | localhost:33007 | cloudbridge | Sleep | 715 | > | | > | 81 | cloud | localhost:33310 | cloud_usage | Sleep | 872 | > | | > | 959 | cloud | 10.102.192.117:48041 | cloud | Sleep | 11 | > | | > | 965 | cloud | 10.102.192.117:48049 | cloud | Query | 0| > | commit | > | 1015 | cloud | 10.102.192.117:48294 | cloud_usage | Sleep | 186 | > | | > | 1406 | cloud | localhost:60220 | cloud | Sleep | 725 | > | | > | 1410 | cloud | 10.102.192.117:54646 | cloud | Sleep | 93 | > | | > | 1412 | cloud | 10.102.192.117:54648 | cloud | Sleep | 173 | > | | > | 1413 | cloud | localhost:60352 | cloud | Sleep | 725 | > | | > | 1415 | cloud | 10.102.192.117:54704 | cloud | Sleep | 133 | > | | > | 1418 | cloud | localhost:60445 | cloud | Sleep | 709 | > | | > | 1419 | cloud | localhost:60463 | cloud | Sleep | 853 | > | | > | 1420 | cloud | localhost:60467 | cloud | Sleep | 851 | > | | > | 1421 | cloud | localhost:60468 | cloud | Sleep | 820 | > | | > | 1422 | cloud | 10.102.192.117:54799 | cloud | Sleep | 35 | > | | > | 1423 | cloud | localhost:60472 | cloud | Sleep | 846 | > | | > | 1424 | cloud | localhost:60473 | cloud | Sleep | 725 | > | | > | 1425 | cloud | localhost:60474 | cloud | Sleep | 733 | > | | > |
[jira] [Commented] (CLOUDSTACK-3741) Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718894#comment-13718894
]
ASF subversion and git services commented on CLOUDSTACK-3741:
-
Commit 7799f6482fe8c16923554cd6515cc8783be363d2 in branch refs/heads/master
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7799f64 ]
CLOUDSTACK-3741: a typo in adding .qcow2 extension.
> Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
> --
>
> Key: CLOUDSTACK-3741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3741
> 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: Chandan Purushothama
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.0
>
>
>
> Steps to Reproduce:
>
> 1. On an Advanced Zone KVM Setup, Create a Template from a Snapshot of a ROOT
> disk of a linux VM.
>
> Observations:
>
> ---
> Management Server Log:
> ---
> Exception:
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-1039532081: Processing: { Ans: , MgmtId:
> 7471666038533, via: 3, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.io.FileNotFoundException:
>
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)","wait":0}}] }
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Seq
> 3-1039532081: Received: { Ans: , MgmtId: 7471666038533, via: 3, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-23 10:54:51,508 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Failed to
> create templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> 2013-07-23 10:54:51,620 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-23 10:54:51,640 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Complete
> async job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> Create Template Job Information:
> [root@asfmgmt ~]# grep -i "job-44"
> /var/log/cloudstack/management/management-server.log
> 2013-07-23 10:53:40,592 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-44 = [
> 5439372e-dfea-42fc-875a-8c16c1588914 ], details: AsyncJobVO {id:44, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 203,
> cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"280DZaD
[jira] [Resolved] (CLOUDSTACK-3739) UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have the same icon
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3739. --- Resolution: Fixed > UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have > the same icon > --- > > Key: CLOUDSTACK-3739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3739 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture26.PNG > > > Attached screenshot to the bug report. -- 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-3729) Management Server stopped responding in a Multinode Management Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718893#comment-13718893 ] Alena Prokharchyk commented on CLOUDSTACK-3729: --- Sailaja, can you please point out: * which command got timed out? Async Job Id would be useful for debugging. * did you see any error/exception in the management log when the timeout happened. If so, please elaborate. * the logs you've included to the bug, don't cover the management startup process. I need this information in order to see if the startup was done properly with no errors. Or just give me the credentials to your management servers. > Management Server stopped responding in a Multinode Management Setup > > > Key: CLOUDSTACK-3729 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3729 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log, > MS2-apilog.log, MS2-management-server.log > > > Setup : Adv Configuration with VMWARE (Stadard vSwitch with 2 clusters ) & > Zone wide Primary storage > Steps: > 1. Configure Multinode Management setup (MS1 & MS2) > 2. Enable agent.lb.enabled to true > 3. DB is available locally to MS1 > 4. Create new accounts and deployed VM's > Observation: > 1. Tried to access Management server (MS1/MS2 ). Both servers are very slow > to respond and finally they stopped to respond > 2. Restarting Management servers also did not help here : > DB Statistics : > mysql> SHOW STATUS WHERE `variable_name` = 'Threads_connected'; > +---+---+ > | Variable_name | Value | > +---+---+ > | Threads_connected | 38| > +---+---+ > 1 row in set (0.00 sec) > mysql> show status like '%onn%'; > +--+---+ > | Variable_name| Value | > +--+---+ > | Aborted_connects | 6 | > | Connections | 1461 | > | Max_used_connections | 41| > | Ssl_client_connects | 0 | > | Ssl_connect_renegotiates | 0 | > | Ssl_finished_connects| 0 | > | Threads_connected| 38| > +--+---+ > 7 rows in set (0.00 sec) > [root@ec2 management]# mysqladmin -u root -ppassword processlist > +--+---+--+-+-+--+---+--+ > | Id | User | Host | db | Command | Time | State > | Info | > +--+---+--+-+-+--+---+--+ > | 35 | cloud | localhost:32999 | cloud | Sleep | 708 | > | | > | 40 | cloud | localhost:33004 | cloud | Sleep | 708 | > | | > | 43 | cloud | localhost:33007 | cloudbridge | Sleep | 715 | > | | > | 81 | cloud | localhost:33310 | cloud_usage | Sleep | 872 | > | | > | 959 | cloud | 10.102.192.117:48041 | cloud | Sleep | 11 | > | | > | 965 | cloud | 10.102.192.117:48049 | cloud | Query | 0| > | commit | > | 1015 | cloud | 10.102.192.117:48294 | cloud_usage | Sleep | 186 | > | | > | 1406 | cloud | localhost:60220 | cloud | Sleep | 725 | > | | > | 1410 | cloud | 10.102.192.117:54646 | cloud | Sleep | 93 | > | | > | 1412 | cloud | 10.102.192.117:54648 | cloud | Sleep | 173 | > | | > | 1413 | cloud | localhost:60352 | cloud | Sleep | 725 | > | | > | 1415 | cloud | 10.102.192.117:54704 | cloud | Sleep | 133 | > | | > | 1418 | cloud | localhost:60445 | cloud | Sleep | 709 | > | | > | 1419 | cloud | localhost:60463 | cloud | Sleep | 853 | > | | > | 1420 | cloud | localhost:60467 | cloud | Sleep | 851 | > | | > | 1421 | cloud | localhost:60468 | cloud | Sleep | 820 | > | | > | 1422 | cloud | 10.102.192.117:54799 | cloud | Sleep | 35 | > | | > | 1423 | cloud | localhost:60472 | cloud | Sleep | 846 | > | | > | 1424 | cloud | localhost
[jira] [Commented] (CLOUDSTACK-3739) UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have the same icon
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718889#comment-13718889 ] ASF subversion and git services commented on CLOUDSTACK-3739: - Commit ddbe5338d7696aa725173a88d1e4189afb8c7056 in branch refs/heads/master from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ddbe533 ] CLOUDSTACK-3739: Add text label to 'add VMware DC' action for clarity > UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have > the same icon > --- > > Key: CLOUDSTACK-3739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3739 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture26.PNG > > > Attached screenshot to the bug report. -- 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-3739) UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have the same icon
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718890#comment-13718890 ] ASF subversion and git services commented on CLOUDSTACK-3739: - Commit f27ca638c3d9be3af509db00097c9ef57af771b3 in branch refs/heads/4.2 from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f27ca63 ] CLOUDSTACK-3739: Add text label to 'add VMware DC' action for clarity > UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have > the same icon > --- > > Key: CLOUDSTACK-3739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3739 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture26.PNG > > > Attached screenshot to the bug report. -- 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-3741) Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718887#comment-13718887
]
ASF subversion and git services commented on CLOUDSTACK-3741:
-
Commit 837f10111fe06c8eb600a8b44412bbc54c1aff07 in branch refs/heads/4.2 from
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=837f101 ]
CLOUDSTACK-3741: a typo in adding .qcow2 extension.
> Object_Store_Refactor - [KVM] Creation of Template from Snapshot Fails
> --
>
> Key: CLOUDSTACK-3741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3741
> 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: Chandan Purushothama
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.2.0
>
>
>
> Steps to Reproduce:
>
> 1. On an Advanced Zone KVM Setup, Create a Template from a Snapshot of a ROOT
> disk of a linux VM.
>
> Observations:
>
> ---
> Management Server Log:
> ---
> Exception:
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 3-1039532081: Processing: { Ans: , MgmtId:
> 7471666038533, via: 3, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.io.FileNotFoundException:
>
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)","wait":0}}] }
> 2013-07-23 10:54:51,493 DEBUG [agent.transport.Request]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Seq
> 3-1039532081: Received: { Ans: , MgmtId: 7471666038533, via: 3, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-23 10:54:51,508 DEBUG [cloud.template.TemplateManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Failed to
> create templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> 2013-07-23 10:54:51,620 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> at
> com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-23 10:54:51,640 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-15:job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ]) Complete
> async job-44 = [ 5439372e-dfea-42fc-875a-8c16c1588914 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Failed to create
> templatejava.io.FileNotFoundException:
> /mnt/SecStorage/5aac6a6b-cfe3-35bb-9e20-4b2988244554/template/tmpl/3/203/template.properties
> (No such file or directory)
> Create Template Job Information:
> [root@asfmgmt ~]# grep -i "job-44"
> /var/log/cloudstack/management/management-server.log
> 2013-07-23 10:53:40,592 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) submit async job-44 = [
> 5439372e-dfea-42fc-875a-8c16c1588914 ], details: AsyncJobVO {id:44, userId:
> 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 203,
> cmd: org.apache.cloudstack.api.command.user.template.CreateTemplateCmd,
> cmdOriginator: null, cmdInfo:
> {"sessionkey":"280DZaDeR8
[jira] [Commented] (CLOUDSTACK-3563) UI: Shared Networks creation from Networks Tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718885#comment-13718885 ] ASF subversion and git services commented on CLOUDSTACK-3563: - Commit fee5fce5cdbb06b147aa7312b44aa3dc472f3185 in branch refs/heads/4.2 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fee5fce ] CLOUDSTACK-3563: UI > Add Guest Network Dialog (only available for root-admin in Network menu and Infrastructure menu) > change Network Offering field to depend on both zone field and scope field. > UI: Shared Networks creation from Networks Tab > --- > > Key: CLOUDSTACK-3563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.2.0 > > Attachments: login_as_regularUser.jpg, login_as_rootAdmin.jpg > > > Make root-admin able to create shared networks from Network Tab > http://bugs-ccp.citrix.com/browse/CS-16490 -- 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-3563) UI: Shared Networks creation from Networks Tab
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718882#comment-13718882 ] ASF subversion and git services commented on CLOUDSTACK-3563: - Commit 09dde8bf1cbf3d0dc2480081ed09c91e8df5c85f in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09dde8b ] CLOUDSTACK-3563: UI > Add Guest Network Dialog (only available for root-admin in Network menu and Infrastructure menu) > change Network Offering field to depend on both zone field and scope field. > UI: Shared Networks creation from Networks Tab > --- > > Key: CLOUDSTACK-3563 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3563 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.2.0 > > Attachments: login_as_regularUser.jpg, login_as_rootAdmin.jpg > > > Make root-admin able to create shared networks from Network Tab > http://bugs-ccp.citrix.com/browse/CS-16490 -- 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-3677) VMSnapshot on XenServer: RevertToVMSnapshot failed to revert VM to Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-3677:
-
Priority: Major (was: Critical)
> VMSnapshot on XenServer: RevertToVMSnapshot failed to revert VM to Snapshot
> ---
>
> Key: CLOUDSTACK-3677
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3677
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, XenServer
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
> Fix For: 4.2.0
>
> Attachments: management-server.zip, xensource.zip
>
>
> Setup: Advanced Zone, XenServer 6.2
> =
> Steps to Reproduce:
> =
> 1. Deploy Vm. Attach muiltiple data disks to this VM.
> 2. Log in to the Vm and create few directories and files on the root volume.
> Create few more directories on each of the data disks.
> 3. Stop the VM. Create VMSnapshot for this VM with "vm_snapshot_type" set to
> "Disk".
> 4. Revert to the VMSnapshot and observe the failure
>
> Management Server Log:
>
> 2013-07-19 13:50:52,918 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===START=== 10.252.121.104 -- GET
> command=revertToVMSnapshot&vmsnapshotid=b7832d89-de57-4f94-b1e9-a93e7975ef0e&response=json&sessionkey=UXTrrcPGpFO1xH15V%2FhI8SByX1c%3D&_=1374267435422
> 2013-07-19 13:50:52,943 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-20:null) submit async job-45 = [
> e8ffdd72-0c4d-4b47-8106-7181b54ac06c ], details: AsyncJobVO {id:45, userId:
> 4, accountId: 4, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","sessionkey":"UXTrrcPGpFO1xH15V/hI8SByX1c\u003d","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"4","httpmethod":"GET","_":"1374267435422","vmsnapshotid":"b7832d89-de57-4f94-b1e9-a93e7975ef0e","ctxAccountId":"4","ctxStartEventId":"192"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7471666038533,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-19 13:50:52,945 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===END=== 10.252.121.104 -- GET
> command=revertToVMSnapshot&vmsnapshotid=b7832d89-de57-4f94-b1e9-a93e7975ef0e&response=json&sessionkey=UXTrrcPGpFO1xH15V%2FhI8SByX1c%3D&_=1374267435422
> 2013-07-19 13:50:52,947 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Executing
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCmd for
> job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]
> 2013-07-19 13:50:52,966 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Access to
> com.cloud.vm.snapshot.VMSnapshotVO$$EnhancerByCGLIB$$956acea7@7ece4609
> granted to Acct[4-atoms] by DomainChecker_EnhancerByCloudStack_2fa3ef51
> 2013-07-19 13:50:52,985 DEBUG [agent.transport.Request]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Seq
> 4-110170392: Sending { Cmd , MgmtId: 7471666038533, via: 4, Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"volumeTOs":[{"id":13,"name":"New
> Volume
> 1","path":"67e644ac-5792-4007-9eb6-ac298e0c42f3","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":2},{"id":14,"name":"ROOT-11","path":"374a56ac-19a1-4885-8a95-51142be064c1","size":8589934592,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":0},{"id":15,"name":"DATA-11","path":"5c0d41f7-dcab-4a51-aaa8-36729fb4c338","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"5a0dfa0c-0476-3013-8bb2-a140e3f467c2","deviceId":1}],"target":{"id":4,"snapshotName":"i-4-11-VMSNAPSHOT_VS_20130719203659","type":"Disk","createTime":137426622,"current":false,"description":"VM-Snapshot-5"},"vmName":"i-4-11-VMSNAPSHOT","guestOSType":"CentOS
> 5.3 (64-bit)","wait":0}}] }
> 2013-07-19 13:50:52,986 DEBUG [agent.transport.Request]
> (Job-Executor-30:job-45 = [ e8ffdd72-0c4d-4b47-8106-7181b54ac06c ]) Seq
> 4-110170392: Executing: { Cmd , MgmtId: 7471666038533, via: 4, Ver: v1,
> Flags: 100011,
> [{"com.cloud.agent.api.RevertToVMSnapshotCommand":{"volumeTOs":[{"id":13,"name":"New
> Volume
> 1","path":"67e644ac-5792-4007-9eb6-ac298e0c42f3","size":5368709120,"type":"DATADI
[jira] [Assigned] (CLOUDSTACK-3739) UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have the same icon
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3739: - Assignee: Brian Federle > UI: "Add VMWare Datacenter " and "Edit" buttons on the Zone details page have > the same icon > --- > > Key: CLOUDSTACK-3739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3739 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture26.PNG > > > Attached screenshot to the bug report. -- 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-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718878#comment-13718878
]
Rayees Namathponnan commented on CLOUDSTACK-2725:
-
This issue still reproducible even after adding delay; i checked manually VM's
state; vm was running and during attach disk ; then failed with same error
reported above.
As per Edison, we dont have any resolution from product perspective; he will
bring this issue again to community; and based on input decide next.
I can disable these test case from KVM; since there is no point in running this
test; untill fix this issue.
> [Automation] Re-attaching volume on VM failing in KVM
> -
>
> Key: CLOUDSTACK-2725
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
> 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: Automation environment KVM
> Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2725.rar
>
>
> Below two test case failing from BVT
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
> integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
> Steps to reproduce
> Step 1 : Create an account, service offering, create volume, create VM
> Step 2 : Attach volume to VM ,
> Step 3 : Detach volume
> Step 4 : Attach volume to VM again
> Actual result
> Attachment failed with below error
> 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
> (Job-Executor-98:job-1246) Seq 5-258539658: Rec
> eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
> AttachAnswer } }
> 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Unexpected e
> xception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
> TestDiskServ to VM: ce79edb6-
> a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
> unable to execute QEMU comman
> d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> at
> com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
> t(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
> 22)
> 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-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Complete asy
> nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
> text: Failed to attach volume
> : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
> org.libvirt.LibvirtException: internal erro
>
--
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-3752) UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the operations due to the Icons used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718874#comment-13718874 ] ASF subversion and git services commented on CLOUDSTACK-3752: - Commit 782ece6b6039b28960302f1434175da33b12a7ac in branch refs/heads/4.2 from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=782ece6 ] CLOUDSTACK-3752: Add text label to 'reset VM' to avoid confusion > UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the > operations due to the Icons used > -- > > Key: CLOUDSTACK-3752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3752 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture27.PNG > > > I have seen Users using the restore VM button instead of the reboot VM button > and lose all the data on the VM. This is dangerous and hence filed it as a > critical bug. I attached the corresponding screenshot to the bug report. -- 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-3752) UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the operations due to the Icons used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3752. --- Resolution: Fixed > UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the > operations due to the Icons used > -- > > Key: CLOUDSTACK-3752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3752 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture27.PNG > > > I have seen Users using the restore VM button instead of the reboot VM button > and lose all the data on the VM. This is dangerous and hence filed it as a > critical bug. I attached the corresponding screenshot to the bug report. -- 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-3752) UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the operations due to the Icons used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718873#comment-13718873 ] ASF subversion and git services commented on CLOUDSTACK-3752: - Commit c8b3086702768e8944a279431e64a070ac33beb1 in branch refs/heads/master from [~bfederle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c8b3086 ] CLOUDSTACK-3752: Add text label to 'reset VM' to avoid confusion > UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the > operations due to the Icons used > -- > > Key: CLOUDSTACK-3752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3752 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture27.PNG > > > I have seen Users using the restore VM button instead of the reboot VM button > and lose all the data on the VM. This is dangerous and hence filed it as a > critical bug. I attached the corresponding screenshot to the bug report. -- 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-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718868#comment-13718868 ] ASF subversion and git services commented on CLOUDSTACK-3665: - Commit 13a9b941930160a9634e27865a03cdc8aed6d6c3 in branch refs/heads/master from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13a9b94 ] CLOUDSTACK-3665:Failed to create volume from snapshot. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718864#comment-13718864 ] ASF subversion and git services commented on CLOUDSTACK-3665: - Commit 5e42d93b6f14ce407ed9527c29fb9262d90ce07b in branch refs/heads/4.2 from [~minchen07] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5e42d93 ] CLOUDSTACK-3665:Failed to create volume from snapshot. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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] [Assigned] (CLOUDSTACK-3729) Management Server stopped responding in a Multinode Management Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-3729: - Assignee: Alena Prokharchyk > Management Server stopped responding in a Multinode Management Setup > > > Key: CLOUDSTACK-3729 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3729 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log, > MS2-apilog.log, MS2-management-server.log > > > Setup : Adv Configuration with VMWARE (Stadard vSwitch with 2 clusters ) & > Zone wide Primary storage > Steps: > 1. Configure Multinode Management setup (MS1 & MS2) > 2. Enable agent.lb.enabled to true > 3. DB is available locally to MS1 > 4. Create new accounts and deployed VM's > Observation: > 1. Tried to access Management server (MS1/MS2 ). Both servers are very slow > to respond and finally they stopped to respond > 2. Restarting Management servers also did not help here : > DB Statistics : > mysql> SHOW STATUS WHERE `variable_name` = 'Threads_connected'; > +---+---+ > | Variable_name | Value | > +---+---+ > | Threads_connected | 38| > +---+---+ > 1 row in set (0.00 sec) > mysql> show status like '%onn%'; > +--+---+ > | Variable_name| Value | > +--+---+ > | Aborted_connects | 6 | > | Connections | 1461 | > | Max_used_connections | 41| > | Ssl_client_connects | 0 | > | Ssl_connect_renegotiates | 0 | > | Ssl_finished_connects| 0 | > | Threads_connected| 38| > +--+---+ > 7 rows in set (0.00 sec) > [root@ec2 management]# mysqladmin -u root -ppassword processlist > +--+---+--+-+-+--+---+--+ > | Id | User | Host | db | Command | Time | State > | Info | > +--+---+--+-+-+--+---+--+ > | 35 | cloud | localhost:32999 | cloud | Sleep | 708 | > | | > | 40 | cloud | localhost:33004 | cloud | Sleep | 708 | > | | > | 43 | cloud | localhost:33007 | cloudbridge | Sleep | 715 | > | | > | 81 | cloud | localhost:33310 | cloud_usage | Sleep | 872 | > | | > | 959 | cloud | 10.102.192.117:48041 | cloud | Sleep | 11 | > | | > | 965 | cloud | 10.102.192.117:48049 | cloud | Query | 0| > | commit | > | 1015 | cloud | 10.102.192.117:48294 | cloud_usage | Sleep | 186 | > | | > | 1406 | cloud | localhost:60220 | cloud | Sleep | 725 | > | | > | 1410 | cloud | 10.102.192.117:54646 | cloud | Sleep | 93 | > | | > | 1412 | cloud | 10.102.192.117:54648 | cloud | Sleep | 173 | > | | > | 1413 | cloud | localhost:60352 | cloud | Sleep | 725 | > | | > | 1415 | cloud | 10.102.192.117:54704 | cloud | Sleep | 133 | > | | > | 1418 | cloud | localhost:60445 | cloud | Sleep | 709 | > | | > | 1419 | cloud | localhost:60463 | cloud | Sleep | 853 | > | | > | 1420 | cloud | localhost:60467 | cloud | Sleep | 851 | > | | > | 1421 | cloud | localhost:60468 | cloud | Sleep | 820 | > | | > | 1422 | cloud | 10.102.192.117:54799 | cloud | Sleep | 35 | > | | > | 1423 | cloud | localhost:60472 | cloud | Sleep | 846 | > | | > | 1424 | cloud | localhost:60473 | cloud | Sleep | 725 | > | | > | 1425 | cloud | localhost:60474 | cloud | Sleep | 733 | > | | > | 1426 | cloud | localhost:60475 | cloud | Sleep | 852 | > | | > | 1427 | cloud | localhost:60476 | cloud | Sleep | 734 | > | | > | 1429 | cloud | localhost:60478 | cloud | Sleep | 725 | > | |
[jira] [Assigned] (CLOUDSTACK-3752) UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the operations due to the Icons used
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reassigned CLOUDSTACK-3752: - Assignee: Brian Federle > UI: "Reboot VM" and "Restore VM" buttons might confuse the User about the > operations due to the Icons used > -- > > Key: CLOUDSTACK-3752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3752 > 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: Chandan Purushothama >Assignee: Brian Federle >Priority: Critical > Fix For: 4.2.0 > > Attachments: UICapture27.PNG > > > I have seen Users using the restore VM button instead of the reboot VM button > and lose all the data on the VM. This is dangerous and hence filed it as a > critical bug. I attached the corresponding screenshot to the bug report. -- 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-3791) Download Template Fails with NPE
John Burwell created CLOUDSTACK-3791:
Summary: Download Template Fails with NPE
Key: CLOUDSTACK-3791
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3791
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: John Burwell
Priority: Blocker
When registering a template, the download fails with the following NPE from the
SSVM:
2013-07-24 17:26:31,364 DEBUG [agent.transport.Request]
(AgentManager-Handler-1:null) Seq 2-1900150803: Processing: { Ans: , MgmtId:
1, via: 2, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
GetRootDir for null failed due to java.lang.NullPointerException\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1806)\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:1560)\n\tat
org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:186)\n\tat
com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat
com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat
com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
java.lang.Thread.run(Thread.java:679)\n","wait":0}}] }
Secondary storage is configured as NFS on devcloud
(nfs://192.168.56.15/opt/storage/secondary). The following is the information
for the template being registered:
Name: CentOS 5.x
Description: CentOS 5.x
URL: http://bhaisaab.org/vms/cent.vhd
Zone: All Zones
Hypervisor: XenServer
Format: VHD
Extractable: false
Password Enabled: false
Dynamically Scalable: false
Public: true
Featured: false
--
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-3560) UI: extend dependsOn property in dialog widget to accept an array of string
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle closed CLOUDSTACK-3560. - > UI: extend dependsOn property in dialog widget to accept an array of string > --- > > Key: CLOUDSTACK-3560 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3560 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Brian Federle > Fix For: 4.2.0 > > > Currently, dependsOn property in dialog widget only accept a string, > e.g. dependsOn: ‘scope’ > But a dialog field may depend on multiple other dialog fields, > e.g. dependsOn: [‘scope’, ‘zoneId’] > (i.e. the field should change when scope field changes or when zoneId field > changes). -- 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-3560) UI: extend dependsOn property in dialog widget to accept an array of string
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718851#comment-13718851
]
ASF subversion and git services commented on CLOUDSTACK-3560:
-
Commit 7c5b48425f2d01439331c0426731815dbaebb047 in branch refs/heads/master
from [~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c5b484 ]
CLOUDSTACK-3560: UI createForm: Support multiple dependsOn targets
Support passing list of dependsOn targets for form fields. This will
trigger a change if any items specified in list are changed.
Example:
fieldA: {...},
fieldB: {...},
fieldC: { dependsOn: ['fieldA', 'fieldB'] }
> UI: extend dependsOn property in dialog widget to accept an array of string
> ---
>
> Key: CLOUDSTACK-3560
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3560
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Reporter: Jessica Wang
>Assignee: Brian Federle
> Fix For: 4.2.0
>
>
> Currently, dependsOn property in dialog widget only accept a string,
> e.g. dependsOn: ‘scope’
> But a dialog field may depend on multiple other dialog fields,
> e.g. dependsOn: [‘scope’, ‘zoneId’]
> (i.e. the field should change when scope field changes or when zoneId field
> changes).
--
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-3560) UI: extend dependsOn property in dialog widget to accept an array of string
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle resolved CLOUDSTACK-3560. --- Resolution: Fixed > UI: extend dependsOn property in dialog widget to accept an array of string > --- > > Key: CLOUDSTACK-3560 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3560 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Brian Federle > Fix For: 4.2.0 > > > Currently, dependsOn property in dialog widget only accept a string, > e.g. dependsOn: ‘scope’ > But a dialog field may depend on multiple other dialog fields, > e.g. dependsOn: [‘scope’, ‘zoneId’] > (i.e. the field should change when scope field changes or when zoneId field > changes). -- 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-2725) [Automation] Re-attaching volume on VM failing in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718848#comment-13718848
]
Animesh Chaturvedi commented on CLOUDSTACK-2725:
Rayees how much delay was added?
> [Automation] Re-attaching volume on VM failing in KVM
> -
>
> Key: CLOUDSTACK-2725
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
> 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: Automation environment KVM
> Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
>Reporter: Rayees Namathponnan
>Assignee: Fang Wang
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2725.rar
>
>
> Below two test case failing from BVT
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume
> integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume
> Steps to reproduce
> Step 1 : Create an account, service offering, create volume, create VM
> Step 2 : Attach volume to VM ,
> Step 3 : Detach volume
> Step 4 : Attach volume to VM again
> Actual result
> Attachment failed with below error
> 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request]
> (Job-Executor-98:job-1246) Seq 5-258539658: Rec
> eived: { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, {
> AttachAnswer } }
> 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Unexpected e
> xception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume:
> TestDiskServ to VM: ce79edb6-
> a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error
> unable to execute QEMU comman
> d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
> at
> com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
> t(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
> 22)
> 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-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-98:job-1246) Complete asy
> nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
> text: Failed to attach volume
> : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e;
> org.libvirt.LibvirtException: internal erro
>
--
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-3560) UI: extend dependsOn property in dialog widget to accept an array of string
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718846#comment-13718846
]
ASF subversion and git services commented on CLOUDSTACK-3560:
-
Commit 7ce17fa3b8cd8fb4e424e001d159a66dc31d9491 in branch refs/heads/4.2 from
[~bfederle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7ce17fa ]
CLOUDSTACK-3560: UI createForm: Support multiple dependsOn targets
Support passing list of dependsOn targets for form fields. This will
trigger a change if any items specified in list are changed.
Example:
fieldA: {...},
fieldB: {...},
fieldC: { dependsOn: ['fieldA', 'fieldB'] }
> UI: extend dependsOn property in dialog widget to accept an array of string
> ---
>
> Key: CLOUDSTACK-3560
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3560
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Reporter: Jessica Wang
>Assignee: Brian Federle
> Fix For: 4.2.0
>
>
> Currently, dependsOn property in dialog widget only accept a string,
> e.g. dependsOn: ‘scope’
> But a dialog field may depend on multiple other dialog fields,
> e.g. dependsOn: [‘scope’, ‘zoneId’]
> (i.e. the field should change when scope field changes or when zoneId field
> changes).
--
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-3651) Viewing Zone Details Causes an Error Dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell reopened CLOUDSTACK-3651: -- I am still seeing this error in a build from revision 743d35cae4985a8d898da06e5768ae282b32adb2 (Wed Jul 24 18:06:22 2013 +0530). > Viewing Zone Details Causes an Error Dialog > --- > > Key: CLOUDSTACK-3651 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3651 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: devcloud >Reporter: John Burwell >Assignee: Jessica Wang >Priority: Blocker > > When view zone details through the user interface, an error dialog with the > "Unknown API command: listVmwareDcs" message pops-up. The following are the > reproduction steps for this error: >1. Click "Infrastructure" in the sidebar >2. Click "Zones" in the main field >3. Click a zone in the table > These steps will cause the error dialog to displayed. -- 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-3163) KVM Virtual Router startup time is painfully long
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen closed CLOUDSTACK-3163. --- Resolution: Fixed Fix Version/s: 4.2.0 Assignee: Marcus Sorensen Thanks for all of the feedback and testing! > KVM Virtual Router startup time is painfully long > - > > Key: CLOUDSTACK-3163 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3163 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: pre-4.0.0 > Environment: CloudPlatform 3.0.3, but I don't see any changes to the > relevant code (I think) on master >Reporter: Andrew Bayer >Assignee: Marcus Sorensen >Priority: Critical > Fix For: 4.2.0 > > > When you've got a couple thousand instances, spread across 10 or so pods, > virtual router startup time is near crippling - actually, if you don't enable > the option to have virtual routers only populated with instances in their > pod, it *is* crippling, in that the virtual routers don't finish starting > before the management server decides they've timed out and tries to start a > new one. > This seems to be the result of a few painful inefficiencies: > - The same codepath is followed whether you're adding a new instance to an > already running VR, or adding two hundred already running instances to a new > VR. So each ssh/scp/sed/cp/chmod/etc command is replicated for each instance, > rather than finding efficiencies by doing things across the whole set of > instances. > - But what really eats up the time is the population of vm data - for each > piece of vm data (which, from a rough look at the code, seems to be something > like 10 or 11 data files), there are something like 7 ssh calls and an scp > call. So that means that per instance, we have somewhere around 80 to 90 > ssh/scp calls, plus the single ssh call for dhcp_entry.sh. So with 200 > instances, that's 1600 to 1800 ssh/scp calls on a single VR, with all the > overhead entailed in opening that many ssh connections, starting bash, etc, > etc... Given that in my experience, a VR with ~200 instances takes ~90 > minutes to start up (I may be misremembering slightly - it could be ~200 > instances takes closer to 60 minutes, and ~300 takes closer to 90), that > works out to 3 seconds or so per ssh/scp, which doesn't seem implausible to > me. > So, this shouldn't be this way. At a minimum, there's no reason not to > offload the whole process from a script run on the host making repeated ssh > calls to the VR to a script on the VR that gets called from the host, albeit > possibly a temporary one that's generated on the fly and copied over to the > VR. That alone would probably save most of the VR startup time, just by > dropping the number of ssh/scp connections per instance from 80-90 to 3 > (dhcp_entry.sh call, scp of temporary script, execution of temporary script). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3302) [Multiple_IP_Ranges][VmWare] VM deployement failed due to dnsmasq configuration issue in case of multiple subnets in a vlan
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718814#comment-13718814
]
ASF subversion and git services commented on CLOUDSTACK-3302:
-
Commit d09a088093568f167921597825110d5517ac535b in branch refs/heads/4.2 from
[~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d09a088 ]
CLOUDSTACK-3302: [Multiple_IP_Ranges][VmWare] VM deployement failed due to
dnsmasq configuration issue in case of multiple subnets in a vlan
Signed-off-by: Abhinandan Prateek
> [Multiple_IP_Ranges][VmWare] VM deployement failed due to dnsmasq
> configuration issue in case of multiple subnets in a vlan
> ---
>
> Key: CLOUDSTACK-3302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3302
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: Latest build from master_6-17-stable branch
>Reporter: Sanjeev N
>Assignee: Harikrishna Patnala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> [Multiple_IP_Ranges][VmWare] VM deployement failed due to dnsmasq
> configuration issue in case of multiple subnets in a vlan
> Steps to Reproduce:
> =
> 1.Bring up CS in advanced zone with vmware cluster
> 2.Create a shared network and add IP range
> 3.Deploy vms so that all ip ranges should be exhausted from the IP range
> 4.And another IP range in a new CIDR in the same shared network created at
> step2
> 5.Deploy guest vm
> Expected Result:
> ==
> 1.Deploying guest vm at step5 should create ip alias on VR, should regenerate
> dnsmasq.conf file with new CIDR information
> Actual Result:
> ===
> Since regenerating dnsmasq.conf failed, vm could not get the IP Address from
> the new CIDR using dhcp service from VR.
> Observations:
>
> Following is the log snippet from management server log file:
> 2013-07-01 11:57:11,214 DEBUG [agent.transport.Request]
> (Job-Executor-4:job-176) Seq 10-134086950: Sending { Cmd , MgmtId:
> 7332683579487, via: 10, Ver: v1, Flags: 100011,
> [{"routing.CreateIpAliasCommand":{"routerip":"10.147.33.11","ipAliasTOs":[{"routerip":"10.147.33.132","netmask":"255.255.255.192","alias_count":"44"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}},{"routing.DnsMasqConfigCommand":{"domain":"cs1cloud.internal","dns1":"10.103.128.16","internal_dns1":"10.103.128.16","dnsmasqTOs":[{"routerIp":"10.147.33.11","gateway":"10.147.33.1","netmask":"255.255.255.128","startIpOfSubnet":"10.147.33.1"},{"routerIp":"10.147.33.132","gateway":"10.147.33.129","netmask":"255.255.255.192","startIpOfSubnet":"10.147.33.129"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}}]
> }
> 2013-07-01 11:57:11,215 DEBUG [agent.transport.Request]
> (Job-Executor-4:job-176) Seq 10-134086950: Executing: { Cmd , MgmtId:
> 7332683579487, via: 10, Ver: v1, Flags: 100011,
> [{"routing.CreateIpAliasCommand":{"routerip":"10.147.33.11","ipAliasTOs":[{"routerip":"10.147.33.132","netmask":"255.255.255.192","alias_count":"44"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}},{"routing.DnsMasqConfigCommand":{"domain":"cs1cloud.internal","dns1":"10.103.128.16","internal_dns1":"10.103.128.16","dnsmasqTOs":[{"routerIp":"10.147.33.11","gateway":"10.147.33.1","netmask":"255.255.255.128","startIpOfSubnet":"10.147.33.1"},{"routerIp":"10.147.33.132","gateway":"10.147.33.129","netmask":"255.255.255.192","startIpOfSubnet":"10.147.33.129"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}}]
> }
> 2013-07-01 11:57:11,216 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-171:null) Seq 10-134086950: Executing request
> 2013-07-01 11:57:11,216 INFO [vmware.resource.VmwareResource]
> (DirectAgent-171:10.147.40.18) Executing createIpAlias command:
> {"routerip":"10.147.33.11","ipAliasTOs":[{"routerip":"10.147.33.132","netmask":"255.255.255.192","alias_count":"44"}],"accessDetails":{"router.guest.ip":"10.147.33.11","zone.network.type":"Advanced","router.name":"r-34-VM","router.ip":"10.147.40.249"},"wait":0}
> 2013-07-01 11:57:11,217 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-171:10.147.40.18) Run com
[jira] [Commented] (CLOUDSTACK-3665) Failed to create volume from snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718812#comment-13718812 ] Min Chen commented on CLOUDSTACK-3665: -- This is a regression caused by commit cb96d70967832d50af0350ca896b011519b66755 in fixing a NPE bug for zone wide primary storage. > Failed to create volume from snapshot > - > > Key: CLOUDSTACK-3665 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3665 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Storage Controller, VMware, XenServer >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Min Chen >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup.dmp, management-server.log > > > Steps: > 1. Configure Adv zone with VMWARE with Zone wide primary storage > 2. Deploy VM using default template > 3. Create Snapshot from ROOT volume > 4. Tried to create volume from thos snapshot . > Observation: > It failed to create volume from snapshot saying Storage is unavailable. But > storage is available and i was able to create and attach DATA volumes to the > instance. Only while creating volume from snapshot this failure is observed > (Attached logs and DB) > 2013-07-19 16:20:15,918 INFO [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) There are > no available storage pools to store the volume in > 2013-07-19 16:20:15,919 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Failed to > create volume: 14 > com.cloud.exception.StorageUnavailableException: Resource [StoragePool:-1] is > unreachable: There are no available storage pools to store the volume in > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:558) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolumeFromSnapshot(VolumeManagerImpl.java:614) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:1072) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:188) > at > org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd.execute(CreateVolumeCmd.java:189) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-19 16:20:15,983 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-30:job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ]) Complete > async job-46 = [ 8d88b415-e4e5-453e-865d-48c37a640e7b ], jobStatus: 2, > resultCode: 530, result: Error Code: 530 Error text: Failed to create a volume > 2013-07-19 16:20:17,115 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage 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-3790) KVM - Fail to create recurring snapshot : pool is already active
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angeline shen updated CLOUDSTACK-3790:
--
Attachment: management-server.log.gz
management-server.log.2013-07-23.gz
Screenshot-CloudPlatform™ - Mozilla Firefox-1.png
Screenshot-CloudPlatform™ - Mozilla Firefox-1.png
> KVM - Fail to create recurring snapshot : pool is already active
>
>
> Key: CLOUDSTACK-3790
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3790
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS build
> CloudPlatform-4.2-246-rhel6.3.tar.gz
> host KVM buildCloudPlatform-4.2-246-rhel6.3.tar.gz
>Reporter: angeline shen
>Assignee: edison su
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.2013-07-23.gz,
> management-server.log.gz, Screenshot-CloudPlatform™ - Mozilla Firefox-1.png,
> Screenshot-CloudPlatform™ - Mozilla Firefox-1.png
>
>
> 1. advance zone. domain: d1domain admin: d1domain domain: d2
> user : d2user
> 2. login : admin . create VPC network & VMs with DATA disk
>login: d1domain. create VPC network & VMs with DATA disk
>login: d2user. create VPC network & VMs with DATA disk
> 3. login as each of above users.
> setup hourly recurring snapshots for all ROOT and DATA disks to same
> recurring schedule,
> for example , all at 9 minutes pass the hour.
>
> Result:
> there are some snapshots generated with status CreateOnPrimary , Failed to
> create snapshot due to pool is already active :
> 2013-07-23 22:04:49,920 DEBUG [agent.transport.Request]
> (Job-Executor-42:job-56 = [ 3def22de-176e-45a7-b72b-98aaef57b906 ]) Seq
> 1-1490617925: Sending { Cmd , MgmtId: 6655051826959, via: 1, Ver: v1, Flags:
> 100011, [{"or
> g.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"/mnt/79884886-a3ee-31a7-856c-805e18c48f88/b52e5c2b-fc3e-4292-bda5-cb961efb94c7/c733fc4e-4d16-481f-9
> e20-2ed2519d6b3d","volume":{"uuid":"a39f007b-b014-4e6c-a3fa-8bce7a9ba213","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"79884886-a3ee-31a7-856c-805e18c48f88","id":1,"poo
> lType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvm63","port":2049}},"name":"ROOT-13","size":147456,"path":"b52e5c2b-fc3e-4292-bda5-cb961efb94c7","volumeId":15,"vmName":"i-4-13-VM",
> "accountId":4,"format":"QCOW2","id":15},"parentSnapshotPath":"/mnt/79884886-a3ee-31a7-856c-805e18c48f88/b52e5c2b-fc3e-4292-bda5-cb961efb94c7/29669eb5-1525-4745-81c4-6ca6ad239af0","dataStore":{"org.apache.cloudstack.stor
> age.to.PrimaryDataStoreTO":{"uuid":"79884886-a3ee-31a7-856c-805e18c48f88","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvm63","port":2049}},"vmName":"i-4-13-VM","name"
> :"z1vpc3G3d2userV32_ROOT-13_20130724050449","hypervisorType":"None","id":28}},"destTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/4/15","volume":{"uuid":"a39f007b-b014-4e6c-a3fa-8bce7a9ba213
> ","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"79884886-a3ee-31a7-856c-805e18c48f88","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/
> angie/primary/kvm63","port":2049}},"name":"ROOT-13","size":147456,"path":"b52e5c2b-fc3e-4292-bda5-cb961efb94c7","volumeId":15,"vmName":"i-4-13-VM","accountId":4,"format":"QCOW2","id":15},"parentSnapshotPath":"snapshots/
> 4/15/29669eb5-1525-4745-81c4-6ca6ad239af0","dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232/export/home/angie/secondary/kvm63","_role":"Image"}},"vmName":"i-4-13-VM","name":"z1vpc3G3d2userV32_RO
> OT-13_20130724050449","hypervisorType":"None","id":28}},"executeInSequence":false,"wait":21600}}]
> }
> 2013-07-23 22:04:50,085 DEBUG [agent.transport.Request]
> (AgentManager-Handler-6:null) Seq 1-1490617925: Processing: { Ans: , MgmtId:
> 6655051826959, via: 1, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.C
> opyCmdAnswer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Requested operation is not valid: pool is
> already active as '83602b3b-9b52-3016-871d-10883d294c18'"
> ,"wait":0}}] }
> 2013-07-23 22:04:50,085 DEBUG [agent.transport.Request]
> (Job-Executor-42:job-56 = [ 3def22de-176e-45a7-b72b-98aaef57b906 ]) Seq
> 1-1490617925: Received: {
