[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147358#comment-14147358
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
You've been very helpful.
I will try your advice.
Best regards,
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>Assignee: Likitha Shetty
> Attachments: management-server.log.0521
>
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
> `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
> vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
> pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
> at
> com.cloud.stor
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147181#comment-14147181
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
Thank you for your comment.
Yes, both are true in my case.
Is this cloudstack's bug?
If I set vm.allocation.algorithm in global settings to "random", I can attach
a volume to a VM?
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>Assignee: Likitha Shetty
> Attachments: management-server.log.0521
>
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
> `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
> vol.pool_id WHERE pool.data_center
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004417#comment-14004417
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/21/14 6:36 AM:
---
Attached the management-server log.
1. created "TESTVOL0521" volume
2. tried to attach "TESTVOL0521" to "x00" VM
modified IP address(xxx.xxx) and domain name(xxx)
was (Author: itokaz):
1. created "TESTVOL0521" volume
2. tried to attach "TESTVOL0521" to "x00" VM
modified IP address(xxx.xxx) and domain name(xxx)
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
> Attachments: management-server.log.0521
>
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(
[jira] [Updated] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kazuhiro Ito updated CLOUDSTACK-6631:
-
Attachment: management-server.log.0521
1. created "TESTVOL0521" volume
2. tried to attach "TESTVOL0521" to "x00" VM
modified IP address(xxx.xxx) and domain name(xxx)
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
> Attachments: management-server.log.0521
>
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
> `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
> vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
> pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
>
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004364#comment-14004364
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
>What storage backend are you using?
Shared mount point(GPFS) for primary of two zones
NFS for primary of one zone and secondary of three zones
>Are you using tagging for the disks?
Yes.
But when I don't use tagging for the disks, the same result.
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
> `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
> vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id
[jira] [Created] (CLOUDSTACK-6711) unable to set proper domain via createVolume API
Kazuhiro Ito created CLOUDSTACK-6711: Summary: unable to set proper domain via createVolume API Key: CLOUDSTACK-6711 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6711 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.1 Environment: CloudStack 4.2.1 + KVM on CentOS 6.4 Reporter: Kazuhiro Ito I tested createVolume API as the followings. [root@01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520-a account=Remote-Users domainid=2 diskofferingid=30 zoneid=1 SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolume&name=TESTVOL0520-a&account=Remote-Users&domainid=2&diskofferingid=30&zoneid=1&apikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyA&signature=qYanjN9AW7eMF6A%2FVg5iVjfrYU0%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0949 0 --:--:-- --:--:-- --:--:-- 1370 971ead2e-cea5-4d3f-b45a-4270d64d63f2 89bc3ef4-0146-4cef-a15e-3ccb2ba6d987 domainid "2" is not root domain. but when I check on UI, the volume's domain is "ROOT". I tried uuid as domainid, but the same result. "createVolume" API of 4.2.1 cannot set "domain" properly? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002698#comment-14002698 ] Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/20/14 1:47 AM: --- At first, I tried as both a user and a root admin, the same result. And I tried via both UI and createVolume API, but the same result. "pool_id" and "path" is "NULL". See the followings. [root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520 diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242 zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolume&name=TESTVOL0520&diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242&zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d&apikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyA&signature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250 889fff9b-833d-423d-b295-ae16ed9a10da c5a2a669-98da-4cc6-bad0-d37f63111e86 | id | account_id | domain_id | pool_id | last_pool_id | instance_id | device_id | name| uuid | size | folder | path | pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type | disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable | created | attached| updated | removed | state | chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops | | 1727 | 2 | 1 |NULL | NULL |NULL | NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da | 10995116277760 | NULL| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL | 29 |NULL | NULL | 0 | 2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL | Allocated | NULL |0 | NULL | NULL | NULL | 1 | NULL | NULL | NULL | was (Author: itokaz): At first, I tried as both a user and a root admin, the same result. And I tried via both UI and createVolume API, but the same result. [root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520 diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242 zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d SEND URL: https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolume&name=TESTVOL0520&diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242&zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d&apikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyA&signature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250 889fff9b-833d-423d-b295-ae16ed9a10da c5a2a669-98da-4cc6-bad0-d37f63111e86 | id | account_id | domain_id | pool_id | last_pool_id | instance_id | device_id | name| uuid | size | folder | path | pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type | disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable | created | attached| updated | removed | state | chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops | | 1727 | 2 | 1 |NULL | NULL |NULL | NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da | 10995116277760 | NULL| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL | 29 |NULL | NULL | 0 | 2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL | Allocated | NULL |0 | NULL | NULL | NULL | 1 | NULL | NULL | NULL | > unable to attach new Volume to VM > - > > Key: CLOUDSTACK-6631 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631 > Project: CloudStack > Issue Type: Bug > Se
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002698#comment-14002698
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
At first, I tried as both a user and a root admin, the same result.
And I tried via both UI and createVolume API, but the same result.
[root@x01 ~]# ./kick_api.sh command=createVolume name=TESTVOL0520
diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242
zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d
SEND URL:
https://xxx.xxx.xxx.xxx:6443/client/api?command=createVolume&name=TESTVOL0520&diskofferingid=d6e4e46d-d094-49dd-98b2-302839576242&zoneid=a08090a5-0dc1-49f6-a1a5-9c314c6f7b5d&apikey=ggaCbJLgRvejLkkyAaJaFwEeKE9ujwNZq3YdUz61EzXblZYeUGCaVSyjwpWWZ7ehCfdP838CYilxejy-7SxtyA&signature=mFAoQ5bAfuIjV07A%2BSP%2FE6AVELg%3D
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
103 207 103 2070 0 1334 0 --:--:-- --:--:-- --:--:-- 2250
889fff9b-833d-423d-b295-ae16ed9a10da
c5a2a669-98da-4cc6-bad0-d37f63111e86
| id | account_id | domain_id | pool_id | last_pool_id | instance_id |
device_id | name| uuid | size
| folder | path |
pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type |
disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
created | attached| updated | removed
| state | chain_info | update_count | disk_type |
vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops
|
| 1727 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL0520 | 889fff9b-833d-423d-b295-ae16ed9a10da |
10995116277760 | NULL| NULL
| NULL | 1 | NULL | NULL| DATADISK| NULL
| 29 |NULL | NULL | 0 |
2014-05-20 01:40:58 | NULL| 2014-05-20 01:40:58 | NULL
| Allocated | NULL |0 | NULL |
NULL | NULL | 1 | NULL | NULL | NULL |
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001323#comment-14001323
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/19/14 7:05 AM:
---
Thank you for your support.
I have three zones. I tested on each zone with Small Disk, 5GB disk offering ,
but the same results.
Additional info; when I create an instance(ROOT DISK) and a volume(DATA DISK)
simultaneously, the volume(DATA DISK) is created correctly. And I can attach
and detach the volume to any instance.
was (Author: itokaz):
Thank you for your support.
I have three zones. I tested on each zone with Small Disk, 5GB disk offering ,
but the same results.
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolume
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001323#comment-14001323
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
Thank you for your support.
I have three zones. I tested on each zone with Small Disk, 5GB disk offering ,
but the same results.
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
> SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
> `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
> vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
> pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
> at
> com.cloud.storage.dao.VolumeDaoImpl.list
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999622#comment-13999622
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/16/14 7:06 AM:
---
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
right behavior?
was (Author: itokaz):
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
true?
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f
[jira] [Commented] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999622#comment-13999622
]
Kazuhiro Ito commented on CLOUDSTACK-6631:
--
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
true?
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
> to VM[User|TEST-A2-VM01] granted to
> Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
> DomainChecker_EnhancerByCloudStack_9b413459
> 2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> LocalStoragePoolAllocator trying to find storage pool to fit the vm
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> ClusterScopeStoragePoolAllocator looking for storage pool
> 2014-05-12 11:29:47,212 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Looking for pools in dc: 1 pod:1 cluster:null having tags:[MPI]
> 2014-05-12 11:29:47,216 DEBUG
> [storage.allocator.ClusterScopeStoragePoolAllocator]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No
> storage pools available for shared volume allocation, returning
> 2014-05-12 11:29:47,234 ERROR [cloud
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999622#comment-13999622
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/16/14 7:25 AM:
---
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| id | account_id | domain_id | pool_id | last_pool_id | instance_id |
device_id | name| uuid | size
| folder | path |
pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type |
disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
created | attached| updated | removed
| state | chain_info | update_count | disk_type |
vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops
|
| 1680 | 3 | 2 |NULL | NULL |NULL |
NULL | TESTVOL | 692b67f5-efdb-4995-8643-a19afec8fc34 |
107374182400 | NULL| NULL
| NULL | 1 | NULL | NULL| DATADISK| NULL |
5 |NULL | NULL | 0 |
2014-05-16 07:24:13 | NULL| 2014-05-16 07:24:13 | NULL
| Allocated | NULL |0 | NULL |
NULL | NULL | 1 | NULL | NULL | NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
right behavior?
was (Author: itokaz):
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| id | account_id | domain_id | pool_id | last_pool_id | instance_id |
device_id | name| uuid | size
| folder | path |
pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type |
disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
created | attached| updated | removed
| state | chain_info | update_count | disk_type |
vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops
|
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
right behavior?
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled:
[jira] [Comment Edited] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999622#comment-13999622
]
Kazuhiro Ito edited comment on CLOUDSTACK-6631 at 5/16/14 7:09 AM:
---
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| id | account_id | domain_id | pool_id | last_pool_id | instance_id |
device_id | name| uuid | size
| folder | path |
pod_id | data_center_id | iscsi_name | host_ip | volume_type | pool_type |
disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
created | attached| updated | removed
| state | chain_info | update_count | disk_type |
vm_snapshot_chain_size | iso_id | display_volume | format | min_iops | max_iops
|
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
right behavior?
was (Author: itokaz):
Sorry, I cannot test on 4.4 because I have to resolve the problem on 4.2.1.
The following is "volumes" of the new volume on mysql.
| 1677 | 2 | 1 |NULL | NULL |NULL |
NULL | TESTVOL | d646d4c6-ccc1-402c-b9fa-e24f3e8314f8 | 107374182400 | NULL
| NULL | NULL | 1 | NULL | NULL| DATADISK| NULL
|5 |NULL | NULL | 0 |
2014-05-16 05:37:25 | NULL | 2014-05-16 05:37:25 | NULL|
Allocated | NULL |0 | NULL | NULL |
NULL |
I wonder "path" is "NULL".
When I create new volume, I cannot see the image on primary storage. Is this
right behavior?
> unable to attach new Volume to VM
> -
>
> Key: CLOUDSTACK-6631
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> 1. I added new volume.
> 2. I tried to attach the volume to a VM on UI.
> 3. It failed and the following log appeared.
> 2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===START=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
> (http-6443-exec-116:null) submit async job-4916 = [
> dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
> 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543,
> cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
> Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
> job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
> 2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet]
> (http-6443-exec-116:null) ===END=== 133.xx.xxx.xxx -- GET
> command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
> 2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32c
[jira] [Created] (CLOUDSTACK-6632) Template disappears when download cleanedup
Kazuhiro Ito created CLOUDSTACK-6632:
Summary: Template disappears when download cleanedup
Key: CLOUDSTACK-6632
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6632
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.1
Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
Reporter: Kazuhiro Ito
As reported in CLOUDSTACK-6254, in my environment(my template files are QCOW2
format), the template file disappears without any regularity when the secondary
storage server is cleaning up the symlink in /var/www/html/.
When the template file disappeared, I could see the following.
[root@x01 ~]# less
/var/log/cloudstack/management/management-server.log.2014-05-10.gz | grep
DeleteEntityDownloadURLCommand
2014-05-10 10:35:11,898 DEBUG [agent.transport.Request]
(StorageManager-Scavenger-1:null) Seq 3-1917789705: Sending { Cmd , MgmtId:
90520731085572, via: 3, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.storage.DeleteEntityDownloadURLCommand":{"path":"template/tmpl/5/313/c9d50f4c-ec19-424a-b15c-84570d814b92.qcow2","extractUrl":"https://133-58-97-11.realhostip.com/userdata/a1cc6fb1-ec9d-4a20-9ea6-45215f7361d4.qcow2","type":"VOLUME","parentPath":"0826041d-d3c0-3566-ad55-b5a9882cff4a","accountId":0,"wait":0}}]
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kazuhiro Ito updated CLOUDSTACK-6631:
-
Description:
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===START=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543, cmd:
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator:
null, cmdInfo:
{"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===END=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-ISM-C-admin] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) ClusterScopeStoragePoolAllocator
looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Looking for pools in dc: 1 pod:1
cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No storage pools available for
shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
`cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
at
com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:480)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reorderPoolsByNumberOfVolumes(AbstractStoragePoolAllocator.java:122)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reOrder(AbstractStoragePoolAllocator.java:161)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:110)
at
com.cloud.storage.StorageManagerImpl.findStoragePool(StorageManagerImpl.java:433)
at
com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl
[jira] [Updated] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kazuhiro Ito updated CLOUDSTACK-6631:
-
Description:
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===START=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543, cmd:
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator:
null, cmdInfo:
{"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===END=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) ClusterScopeStoragePoolAllocator
looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Looking for pools in dc: 1 pod:1
cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No storage pools available for
shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
`cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
at
com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:480)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reorderPoolsByNumberOfVolumes(AbstractStoragePoolAllocator.java:122)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reOrder(AbstractStoragePoolAllocator.java:161)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:110)
at
com.cloud.storage.StorageManagerImpl.findStoragePool(StorageManagerImpl.java:433)
at
com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl
[jira] [Updated] (CLOUDSTACK-6631) unable to attach new Volume to VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kazuhiro Ito updated CLOUDSTACK-6631:
-
Description:
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===START=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543, cmd:
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator:
null, cmdInfo:
{"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===END=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-x] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) ClusterScopeStoragePoolAllocator
looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Looking for pools in dc: 1 pod:1
cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No storage pools available for
shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
`cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
at
com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:480)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reorderPoolsByNumberOfVolumes(AbstractStoragePoolAllocator.java:122)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reOrder(AbstractStoragePoolAllocator.java:161)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:110)
at
com.cloud.storage.StorageManagerImpl.findStoragePool(StorageManagerImpl.java:433)
at
com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImp
[jira] [Updated] (CLOUDSTACK-6632) Template disappears when download cleanedup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kazuhiro Ito updated CLOUDSTACK-6632:
-
Description:
As reported in CLOUDSTACK-6254, in my environment(my template files are QCOW2
format), the template file disappears without any regularity when the secondary
storage server is cleaning up the symlink in /var/www/html/.
When the template file disappeared, I could see the following.
[root@x01 ~]# less
/var/log/cloudstack/management/management-server.log.2014-05-10.gz | grep
DeleteEntityDownloadURLCommand
2014-05-10 10:35:11,898 DEBUG [agent.transport.Request]
(StorageManager-Scavenger-1:null) Seq 3-1917789705: Sending { Cmd , MgmtId:
90520731085572, via: 3, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.storage.DeleteEntityDownloadURLCommand":{"path":"template/tmpl/5/313/c9d50f4c-ec19-424a-b15c-84570d814b92.qcow2","extractUrl":"https://xxx-xx-xx-xx.realhostip.com/userdata/a1cc6fb1-ec9d-4a20-9ea6-45215f7361d4.qcow2","type":"VOLUME","parentPath":"0826041d-d3c0-3566-ad55-b5a9882cff4a","accountId":0,"wait":0}}]
}
was:
As reported in CLOUDSTACK-6254, in my environment(my template files are QCOW2
format), the template file disappears without any regularity when the secondary
storage server is cleaning up the symlink in /var/www/html/.
When the template file disappeared, I could see the following.
[root@x01 ~]# less
/var/log/cloudstack/management/management-server.log.2014-05-10.gz | grep
DeleteEntityDownloadURLCommand
2014-05-10 10:35:11,898 DEBUG [agent.transport.Request]
(StorageManager-Scavenger-1:null) Seq 3-1917789705: Sending { Cmd , MgmtId:
90520731085572, via: 3, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.storage.DeleteEntityDownloadURLCommand":{"path":"template/tmpl/5/313/c9d50f4c-ec19-424a-b15c-84570d814b92.qcow2","extractUrl":"https://133-58-97-11.realhostip.com/userdata/a1cc6fb1-ec9d-4a20-9ea6-45215f7361d4.qcow2","type":"VOLUME","parentPath":"0826041d-d3c0-3566-ad55-b5a9882cff4a","accountId":0,"wait":0}}]
}
> Template disappears when download cleanedup
> ---
>
> Key: CLOUDSTACK-6632
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6632
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.1
> Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
>Reporter: Kazuhiro Ito
>
> As reported in CLOUDSTACK-6254, in my environment(my template files are QCOW2
> format), the template file disappears without any regularity when the
> secondary storage server is cleaning up the symlink in /var/www/html/.
> When the template file disappeared, I could see the following.
> [root@x01 ~]# less
> /var/log/cloudstack/management/management-server.log.2014-05-10.gz | grep
> DeleteEntityDownloadURLCommand
> 2014-05-10 10:35:11,898 DEBUG [agent.transport.Request]
> (StorageManager-Scavenger-1:null) Seq 3-1917789705: Sending { Cmd , MgmtId:
> 90520731085572, via: 3, Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.storage.DeleteEntityDownloadURLCommand":{"path":"template/tmpl/5/313/c9d50f4c-ec19-424a-b15c-84570d814b92.qcow2","extractUrl":"https://xxx-xx-xx-xx.realhostip.com/userdata/a1cc6fb1-ec9d-4a20-9ea6-45215f7361d4.qcow2","type":"VOLUME","parentPath":"0826041d-d3c0-3566-ad55-b5a9882cff4a","accountId":0,"wait":0}}]
> }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-6631) unable to attach new Volume to VM
Kazuhiro Ito created CLOUDSTACK-6631:
Summary: unable to attach new Volume to VM
Key: CLOUDSTACK-6631
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6631
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.1
Environment: Cloudstack 4.2.1 + KVM on CentOS 6.4
Reporter: Kazuhiro Ito
1. I added new volume.
2. I tried to attach the volume to a VM on UI.
3. It failed and the following log appeared.
2014-05-12 11:29:47,096 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===START=== 133.xx.xxx.xxx -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,143 DEBUG [cloud.async.AsyncJobManagerImpl]
(http-6443-exec-116:null) submit async job-4916 = [
dd8fab57-96aa-446f-8ebd-53c32ce4501a ], details: AsyncJobVO {id:4916, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: 1543, cmd:
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator:
null, cmdInfo:
{"response":"json","id":"ac7099fb-ac66-4c63-bf1e-ed0e1429f412","sessionkey":"TDcTy/QRb5/+k28wsjg6BWd6pcA\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"3","virtualMachineId":"ecdc2c1d-e21e-4c04-962a-4efac1a69a74","httpmethod":"GET","_":"1399861774316","ctxAccountId":"3","ctxStartEventId":"34276"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 90520731085572,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-05-12 11:29:47,144 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for
job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]
2014-05-12 11:29:47,147 DEBUG [cloud.api.ApiServlet] (http-6443-exec-116:null)
===END=== 133.58.108.201 -- GET
command=attachVolume&id=ac7099fb-ac66-4c63-bf1e-ed0e1429f412&virtualMachineId=ecdc2c1d-e21e-4c04-962a-4efac1a69a74&response=json&sessionkey=TDcTy%2FQRb5%2F%2Bk28wsjg6BWd6pcA%3D&_=1399861774316
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to org.apache.cloudstack.storage.volume.VolumeObject@17178a01 granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-ISM-C-admin] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,192 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Access
to VM[User|TEST-A2-VM01] granted to
Acct[0bea1cc1-ac60-4fb2-990b-f2dd04a5a329-xxx-x-] by
DomainChecker_EnhancerByCloudStack_9b413459
2014-05-12 11:29:47,212 DEBUG [storage.allocator.LocalStoragePoolAllocator]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
LocalStoragePoolAllocator trying to find storage pool to fit the vm
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) ClusterScopeStoragePoolAllocator
looking for storage pool
2014-05-12 11:29:47,212 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) Looking for pools in dc: 1 pod:1
cluster:null having tags:[MPI]
2014-05-12 11:29:47,216 DEBUG
[storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-146:job-4916
= [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ]) No storage pools available for
shared volume allocation, returning
2014-05-12 11:29:47,234 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-146:job-4916 = [ dd8fab57-96aa-446f-8ebd-53c32ce4501a ])
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM
`cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes` vol ON pool.id =
vol.pool_id WHERE pool.data_center_id = ? AND pool.pod_id = ? AND
pool.cluster_id = ? GROUP BY pool.id ORDER BY 2 ASC
at
com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:480)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reorderPoolsByNumberOfVolumes(AbstractStoragePoolAllocator.java:122)
at
org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reOrder(AbstractStoragePoolAllocator.j
