[jira] [Updated] (CLOUDSTACK-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-3489:
--
Attachment: management-server.rar
Attached management server log file.
> Failed to start VR due to error in finalizeStart with KVM hypervisor
>
>
> Key: CLOUDSTACK-3489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
> 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 ACS 4.2 branch.
> Zone: Advanced with KVM cluster
> Stoarage: S3 and Local storage
>Reporter: Sanjeev N
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Failed to start VR due to error in finalizeStart with KVM hypervisor:
> KVM routing template being used:
> systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with KVM cluster
> 2.Use s3 as the secondary storage and Local storage as the primary storage
> 3.Use default cent os template to deploy guest vm
> Observations:
> ===
> VR was started as part of vm deployment process and it remained in starting
> state for a while. However later it was stopped with following exceptions:
> com.cloud.exception.AgentUnavailableException: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: com.cloud.utils.exception.ExecutionException: Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
> ... 19 more
> 2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete
> async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> Few more log snippets from mgmt server log file:
> 2013-07-12 02:36:21,128 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 4-691668978: Processing: { Ans: , MgmtId:
> 6615759585382, via: 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"r-13-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP name=r-13-VM
> eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1
> eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1
> eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=router disable_rp_filter=true
> dns1=10.103.128.16","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynam
[jira] [Created] (CLOUDSTACK-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor
Sanjeev N created CLOUDSTACK-3489:
-
Summary: Failed to start VR due to error in finalizeStart with KVM
hypervisor
Key: CLOUDSTACK-3489
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
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 ACS 4.2 branch.
Zone: Advanced with KVM cluster
Stoarage: S3 and Local storage
Reporter: Sanjeev N
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.rar
Failed to start VR due to error in finalizeStart with KVM hypervisor:
KVM routing template being used:
systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
Steps to Reproduce:
1.Bring up CS in advanced zone with KVM cluster
2.Use s3 as the secondary storage and Local storage as the primary storage
3.Use default cent os template to deploy guest vm
Observations:
===
VR was started as part of vm deployment process and it remained in starting
state for a while. However later it was stopped with following exceptions:
com.cloud.exception.AgentUnavailableException: Resource [Host:4] is
unreachable: Host 4: Unable to start instance due to Unable to start
VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: com.cloud.utils.exception.ExecutionException: Unable to start
VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
... 19 more
2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete
async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2,
resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is
unreachable: Host 4: Unable to start instance due to Unable to start
VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
Few more log snippets from mgmt server log file:
2013-07-12 02:36:21,128 DEBUG [agent.transport.Request]
(AgentManager-Handler-4:null) Seq 4-691668978: Processing: { Ans: , MgmtId:
6615759585382, via: 4, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"r-13-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP name=r-13-VM
eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1
eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1
eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=router disable_rp_filter=true
dns1=10.103.128.16","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"2ef0b4b5e400c38","vncAddr":"10.147.40.14","params":{},"uuid":"9da5edbc-d99e-4a86-ac08-cc3772d7a31c","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"494baea3-d999-4baf-9f6a-9649e700fdc3","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"cd48bacb-ebb7-41a9-8617-67567c1bce71","id":2,"poolType":"Filesystem","host"
[jira] [Closed] (CLOUDSTACK-2452) Usage:F5:SRX:usage manager failed with db exception due to undefiled field "account.default" (cloud_usage.account.default field is missing)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-2452. verified the issue and now not seen any dbexception and account table has missing column.so closing the issue. mysql> desc account -> ; +-+-+--+-+-+---+ | Field | Type| Null | Key | Default | Extra | +-+-+--+-+-+---+ | id | bigint(20) unsigned | NO | PRI | NULL| | | account_name| varchar(100)| YES | | NULL| | | uuid| varchar(40) | YES | UNI | NULL| | | type| int(1) unsigned | NO | | NULL| | | domain_id | bigint(20) unsigned | YES | | NULL| | | state | varchar(10) | NO | | enabled | | | removed | datetime| YES | MUL | NULL| | | cleanup_needed | tinyint(1) | NO | | 0 | | | network_domain | varchar(100)| YES | | NULL| | | default_zone_id | bigint(20) unsigned | YES | | NULL| | | default | int(1) unsigned | NO | | 0 | | +-+-+--+-+ > Usage:F5:SRX:usage manager failed with db exception due to undefiled field > "account.default" (cloud_usage.account.default field is missing) > --- > > Key: CLOUDSTACK-2452 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2452 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: sadhu suresh >Assignee: Kishan Kavala >Priority: Critical > > Noticed usage manager failed with runtime exception: a undefined filed > "account.default" exits in the request sql query by the usage manager , due > to this usage statistics job fail with > i.e account.default field is missing in the cloud_usage.account table. > 1.install the usage server > 2.configure the usage serve to query the usage statistics for every 10 min > 3.configure the lb and generate the load form VM > 4.observe the usage statistics. > actual results: > usage job failed with runtime exception > 013-05-13 10:45:09,191 ERROR [cloud.usage.UsageManagerImpl] > (Usage-Job-1:null) Exception in usage manager > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@5508e44d: SELECT account.id, > account.account_name, account.type, account.domain_id, account.state, > account.removed, account.cleanup_needed, account.network_domain, > account.uuid, account.default_zone_id, account.default FROM account WHERE > account.id = 2 > at com.cloud.utils.db.GenericDaoBase.findById(GenericDaoBase.java:979) > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findById$35() > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke() > at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findById() > at > com.cloud.utils.db.GenericDaoBase.findByIdIncludingRemoved(GenericDaoBase.java:939) > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findByIdIncludingRemoved$36() > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke() > at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findByIdIncludingRemoved() > at > com.cloud.usage.UsageManagerImpl.createVolumeHelperEvent(UsageManagerImpl.java:1075) > at > com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:764) > at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:509) > at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:323) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureT
[jira] [Resolved] (CLOUDSTACK-3340) [Automation] Failed to create network due to: errorCode: 431, errorText:StartIp/endIp/gateway/netmask are required when create network of type Shared and network of
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Girish Shilamkar resolved CLOUDSTACK-3340.
--
Resolution: Fixed
Test was invalid.
> [Automation] Failed to create network due to: errorCode: 431,
> errorText:StartIp/endIp/gateway/netmask are required when create network of
> type Shared and network of type Isolated with service SourceNat disabled
> --
>
> Key: CLOUDSTACK-3340
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3340
> 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: Master
>Reporter: Parth Jagirdar
>Assignee: Girish Shilamkar
>Priority: Blocker
>
> Test Network offering with Conserve mode off and VR - All services ... ok
> Test Network offering with Conserve mode ON and VR - All services ... ok
> Test deployVM in shared network without startIp/endIp ... ERROR
> ==
> ERROR: Test deployVM in shared network without startIp/endIp
> --
> Traceback (most recent call last):
> File
> "/Users/Parth/cloudstack/test/integration/component/test_network_offering.py",
> line 1927, in test_deployVmSharedNetworkWithoutIpRange
> zoneid=self.zone.id
> File "/Library/Python/2.7/site-packages/marvin/integration/lib/base.py",
> line 1831, in create
> return Network(apiclient.createNetwork(cmd).__dict__)
> File
> "/Library/Python/2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 1539, in createNetwork
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File "/Library/Python/2.7/site-packages/marvin/cloudstackConnection.py",
> line 215, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
> File "/Library/Python/2.7/site-packages/marvin/jsonHelper.py", line 128, in
> getResultObj
> raise
> cloudstackException.cloudstackAPIException(responseName.replace("response",
> ""), errMsg)
> cloudstackAPIException: Execute cmd: createnetwork failed, due to: errorCode:
> 431, errorText:StartIp/endIp/gateway/netmask are required when create network
> of type Shared and network of type Isolated with service SourceNat disabled
> >> begin captured logging <<
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=XmVCQhRCBS%2B01pIMFP4TF72hguc%3D&apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=deleteServiceOffering&id=bcd7dea2-fcb4-4399-9348-f93a736e0f48&response=json
> HTTP/1.1" 200 60
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=listDomains&signature=pZAoTagbtkv%2FIsx0OhvMu%2Bwj1Q8%3D&response=json
> HTTP/1.1" 200 1629
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=listZones&signature=7ZMjupfEOO2ii4bMH99AfUS5xPE%3D&response=json
> HTTP/1.1" 200 749
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&description=CentOS+5.3+%2864-bit%29&command=listOsTypes&signature=q300ePjyZOXldG214ljTmGlTDvA%3D&response=json
> HTTP/1.1" 200 194
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&templatefilter=featured&command=listTemplates&signature=R%2BEXf7TPecJYZPoBGuxglVkHOuA%3D&zoneid=bfcac7d1-3919-4c8d-a817-0a0b1bd83822&response=json
> HTTP/1.1" 200 819
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.
[jira] [Closed] (CLOUDSTACK-3340) [Automation] Failed to create network due to: errorCode: 431, errorText:StartIp/endIp/gateway/netmask are required when create network of type Shared and network of t
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Girish Shilamkar closed CLOUDSTACK-3340.
> [Automation] Failed to create network due to: errorCode: 431,
> errorText:StartIp/endIp/gateway/netmask are required when create network of
> type Shared and network of type Isolated with service SourceNat disabled
> --
>
> Key: CLOUDSTACK-3340
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3340
> 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: Master
>Reporter: Parth Jagirdar
>Assignee: Girish Shilamkar
>Priority: Blocker
>
> Test Network offering with Conserve mode off and VR - All services ... ok
> Test Network offering with Conserve mode ON and VR - All services ... ok
> Test deployVM in shared network without startIp/endIp ... ERROR
> ==
> ERROR: Test deployVM in shared network without startIp/endIp
> --
> Traceback (most recent call last):
> File
> "/Users/Parth/cloudstack/test/integration/component/test_network_offering.py",
> line 1927, in test_deployVmSharedNetworkWithoutIpRange
> zoneid=self.zone.id
> File "/Library/Python/2.7/site-packages/marvin/integration/lib/base.py",
> line 1831, in create
> return Network(apiclient.createNetwork(cmd).__dict__)
> File
> "/Library/Python/2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 1539, in createNetwork
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File "/Library/Python/2.7/site-packages/marvin/cloudstackConnection.py",
> line 215, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
> File "/Library/Python/2.7/site-packages/marvin/jsonHelper.py", line 128, in
> getResultObj
> raise
> cloudstackException.cloudstackAPIException(responseName.replace("response",
> ""), errMsg)
> cloudstackAPIException: Execute cmd: createnetwork failed, due to: errorCode:
> 431, errorText:StartIp/endIp/gateway/netmask are required when create network
> of type Shared and network of type Isolated with service SourceNat disabled
> >> begin captured logging <<
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?signature=XmVCQhRCBS%2B01pIMFP4TF72hguc%3D&apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=deleteServiceOffering&id=bcd7dea2-fcb4-4399-9348-f93a736e0f48&response=json
> HTTP/1.1" 200 60
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=listDomains&signature=pZAoTagbtkv%2FIsx0OhvMu%2Bwj1Q8%3D&response=json
> HTTP/1.1" 200 1629
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&command=listZones&signature=7ZMjupfEOO2ii4bMH99AfUS5xPE%3D&response=json
> HTTP/1.1" 200 749
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&description=CentOS+5.3+%2864-bit%29&command=listOsTypes&signature=q300ePjyZOXldG214ljTmGlTDvA%3D&response=json
> HTTP/1.1" 200 194
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK41CI4Zwmi5FK2CR5Ux5VAWCxEeBIQITPcQ2f9iVkDbAVhKD7n6loKjfJ_a0DpHanj0lReFtdcdZ8lg&templatefilter=featured&command=listTemplates&signature=R%2BEXf7TPecJYZPoBGuxglVkHOuA%3D&zoneid=bfcac7d1-3919-4c8d-a817-0a0b1bd83822&response=json
> HTTP/1.1" 200 819
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 10.223.49.197
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?apiKey=k9DlXgrK
[jira] [Created] (CLOUDSTACK-3490) [VMware]Router VM failed to start with VMware hypervisor .
manasaveloori created CLOUDSTACK-3490: - Summary: [VMware]Router VM failed to start with VMware hypervisor . Key: CLOUDSTACK-3490 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3490 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: 4.2 stable build Reporter: manasaveloori Priority: Blocker Fix For: 4.2.0 Steps: 1. Have CS with VMware hypervisor. 2. Create primary storage –local .Secondary storage-NFS. 3. Deploy a user VM. Observations: Observed that the Router VM fails to start with following exception 2013-07-12 18:25:49,696 DEBUG [vmware.mo.HostMO] (DirectAgent-16:10.147.40.29) VM r-18-VM found in host cache 2013-07-12 18:25:49,766 INFO [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) Configure VNC port for VM r-18-VM, port: 5926, host: 10.147.40.29 2013-07-12 18:25:50,224 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1 is ready to launch secondary storage VM 2013-07-12 18:25:50,265 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is ready to launch secondary storage VM 2013-07-12 18:25:50,626 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1 is ready to launch console proxy 2013-07-12 18:25:50,643 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is ready to launch console proxy 2013-07-12 18:25:51,048 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===START=== 10.252.192.69 -- GET command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789 2013-07-12 18:25:51,087 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) ===END=== 10.252.192.69 -- GET command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789 2013-07-12 18:25:51,693 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status. 2013-07-12 18:25:51,696 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. 2013-07-12 18:25:51,808 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 3 routers to update status. 2013-07-12 18:25:51,811 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. 2013-07-12 18:25:53,411 WARN [vmware.resource.VmwareResource] (DirectAgent-16:10.147.40.29) StartCommand failed due to Exception: java.lang.RuntimeException Message: A specified parameter was not correct. java.lang.RuntimeException: A specified parameter was not correct. at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2834) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:507) 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-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq 4-676266156: Cancelling because one of the answers is false and it is stop on error. 2013-07-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-16:null) Seq Attaching the Ms logs -- 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-2456) usage:usage parser throws runtime exception while parsing networkoffering usage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-2456. verified the issue and found to be ok. IST 2013, endDate: Fri Jul 12 18:35:00 IST 2013, for account: 2 2013-07-12 13:05:00,313 DEBUG [usage.parser.PortForwardingUsageParser] (Usage-Job-1:null) Parsing all PortForwardingRule usage events for account: 2 2013-07-12 13:05:00,314 DEBUG [usage.parser.PortForwardingUsageParser] (Usage-Job-1:null) No port forwarding usage events for this period 2013-07-12 13:05:00,314 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Parsing all NetworkOffering usage events for account: 2 2013-07-12 13:05:00,315 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Total running time 599892ms 2013-07-12 13:05:00,316 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Creating network offering:10 usage record for Vm : 9, usage: 0.166637, startDate: Fri Jul 12 18:25:00 IST 2013, endDate: Fri Jul 12 18:35:00 IST 2013, for account: 2 2013-07-12 13:05:00,317 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Total running time 599892ms 2013-07-12 13:05:00,318 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Creating network offering:10 usage record for Vm : 4, usage: 0.166637, startDate: Fri Jul 12 18:25:00 IST 2013, endDate: Fri Jul 12 18:35:00 IST 2013, for account: 2 2013-07-12 13:05:00,319 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Total running time 599892ms 2013-07-12 13:05:00,320 DEBUG [usage.parser.NetworkOfferingUsageParser] (Usage-Job-1:null) Creating network offering:10 usage record for Vm : 6, usage: 0.166637, startDate: Fri Jul 12 18:25:00 IST 2013, endDate: Fri Jul 12 18:35:00 IST 2013, for account: 2 2013-07-12 13:05:00,321 DEBUG [usage.parser.IPAddressUsageParser] (Usage-Job-1:null) Parsing IP Address usage for account: 2 2013-07-12 13:05:00,323 DEBUG [usage.parser.IPAddressUsageParser] (Usage-Job-1:null) Total usage time 599892ms > usage:usage parser throws runtime exception while parsing networkoffering > usage > - > > Key: CLOUDSTACK-2456 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2456 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: sadhu suresh >Priority: Critical > > Noticed runtime exception in the usage log due to usage parser failed while > parsing network-offering usage due to invalid date format > steps: > 1.install the usage server > 2.configure the usage serve to query the usage statistics for every 10 min > 3.configure the lb and generate the load form VM > 4.check the usage events > actual results: > Noticed runtime exception in the usage log due to usage parser failed while > parsing networkoffering usage due to Unparseable date > content of usage log: > *** > 2013-05-13 14:05:04,367 DEBUG [usage.parser.PortForwardingUsageParser] > (Usage-Job-1:null) Parsing all PortForwardingRule usage events for account: 23 > 2013-05-13 14:05:04,368 DEBUG [usage.parser.PortForwardingUsageParser] > (Usage-Job-1:null) No port forwarding usage events for this period > 2013-05-13 14:05:04,368 DEBUG [usage.parser.NetworkOfferingUsageParser] > (Usage-Job-1:null) Parsing all NetworkOffering usage events for account: 23 > 2013-05-13 14:05:04,370 WARN [usage.dao.UsageNetworkOfferingDaoImpl] > (Usage-Job-1:null) Error getting usage records > com.cloud.utils.exception.CloudRuntimeException: why why > at com.cloud.utils.DateUtil.parseDateString(DateUtil.java:55) > at com.cloud.utils.DateUtil.parseDateString(DateUtil.java:45) > at > com.cloud.usage.dao.UsageNetworkOfferingDaoImpl.getUsageRecords(UsageNetworkOfferingDaoImpl.java:136) > at > com.cloud.usage.dao.UsageNetworkOfferingDaoImpl_EnhancerByCloudStack_4853ba17.CGLIB$getUsageRecords$1() > at > com.cloud.usage.dao.UsageNetworkOfferingDaoImpl_EnhancerByCloudStack_4853ba17_FastClassByCloudStack_c905aa49.invoke() > at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.usage.dao.UsageNetworkOfferingDaoImpl_EnhancerByCloudStack_4853ba17.getUsageRecords() > at > com.cloud.usage.parser.NetworkOfferingUsageParser.parse(NetworkOfferingUsageParser.java:69) > at > com.cloud.usage.UsageManagerImpl.parseHelperTables(UsageManagerImpl.java:735) > at com.cloud.usage.UsageManagerImpl.parse(Usag
[jira] [Updated] (CLOUDSTACK-3490) [VMware]Router VM failed to start with VMware hypervisor .
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manasaveloori updated CLOUDSTACK-3490: -- Attachment: management-server.zip > [VMware]Router VM failed to start with VMware hypervisor . > --- > > Key: CLOUDSTACK-3490 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3490 > 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: 4.2 stable build >Reporter: manasaveloori >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Steps: > 1.Have CS with VMware hypervisor. > 2.Create primary storage –local .Secondary storage-NFS. > 3.Deploy a user VM. > Observations: > Observed that the Router VM fails to start with following exception > 2013-07-12 18:25:49,696 DEBUG [vmware.mo.HostMO] > (DirectAgent-16:10.147.40.29) VM r-18-VM found in host cache > 2013-07-12 18:25:49,766 INFO [vmware.resource.VmwareResource] > (DirectAgent-16:10.147.40.29) Configure VNC port for VM r-18-VM, port: 5926, > host: 10.147.40.29 > 2013-07-12 18:25:50,224 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage VM > 2013-07-12 18:25:50,265 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 2 is ready to launch secondary storage VM > 2013-07-12 18:25:50,626 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Zone 1 is ready to launch console proxy > 2013-07-12 18:25:50,643 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Zone 2 is ready to launch console proxy > 2013-07-12 18:25:51,048 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) > ===START=== 10.252.192.69 -- GET > command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789 > > 2013-07-12 18:25:51,087 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) > ===END=== 10.252.192.69 -- GET > command=queryAsyncJobResult&jobId=c5e0d5a6-f41f-4014-86f7-41f0d6d6c43a&response=json&sessionkey=B2dkl66uTrHsb5xkAC2urfO%2F7xo%3D&_=1373614297789 > 2013-07-12 18:25:51,693 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 3 routers to update status. > 2013-07-12 18:25:51,696 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-07-12 18:25:51,808 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 3 routers to update status. > 2013-07-12 18:25:51,811 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-07-12 18:25:53,411 WARN [vmware.resource.VmwareResource] > (DirectAgent-16:10.147.40.29) StartCommand failed due to Exception: > java.lang.RuntimeException > Message: A specified parameter was not correct. > java.lang.RuntimeException: A specified parameter was not correct. > at > com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290) > at > com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2834) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:507) > 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-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-16:null) Seq 4-676266156: Cancelling because one of the answers > is false and it is stop on error. > 2013-07-12 18:25:53,419 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-16:null) Seq > Attaching the Ms logs -- This message
[jira] [Updated] (CLOUDSTACK-3478) primary:iscsi:cleanupvolumes fail with runtime exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-3478: - Priority: Critical (was: Major) > primary:iscsi:cleanupvolumes fail with runtime exception > > > Key: CLOUDSTACK-3478 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3478 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: sadhu suresh >Priority: Critical > Attachments: management-server.rar > > > steps: > 1.configured the basic zone with network offering"defaultsharednetscalar > eip&elb n/w offering and with xen6.02 hyper-visor ,primary storage type iscsi > 2.deploy few vms > 3.added one more iscsi based primary storage > 4deployed few more deploys > 5.destroy the few vms > Actual result: > during expunging vms ,cleannup of volumes failed with runtime exception. > 2013-07-11 22:37:24,974 DEBUG [db.Transaction.Transaction] > (UserVm-Scavenger-1:null) Rolling back the transaction: Time = 7 Name = > cleanupVolumes; called by > -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-VirtualMachineManagerImpl.advanceExpunge:464-UserVmManagerImpl.expunge:1514-UserVmManagerImpl$ExpungeTask.run:1683-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165 > 2013-07-11 22:37:24,975 WARN [cloud.vm.UserVmManagerImpl] > (UserVm-Scavenger-1:null) Unable to expunge VM[User|sg1] > com.cloud.utils.exception.CloudRuntimeException: Failed to update > state:com.cloud.utils.exception.CloudRuntimeException: Failed to transit > volume: 7, due to: com.cloud.utils.fsm.NoTransitionException: Unable to > transition to a new state from Expunging via DestroyRequested > at > org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:292) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.destroyVolume(VolumeServiceImpl.java:503) > at > com.cloud.storage.VolumeManagerImpl.cleanupVolumes(VolumeManagerImpl.java:2095) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:464) > at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1514) > at > com.cloud.vm.UserVmManagerImpl$ExpungeTask.run(UserVmManagerImpl.java:1683) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-11 22:37:24,976 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Stopped called on VM[User|sg2] but the state is > Expunging > 2013-07-11 22:37:24,985 DEBUG [cloud.capacity.CapacityManagerImpl] > (UserVm-Scavenger-1:null) VM state transitted from :Expunging to Expunging > with event: ExpungeOperationvm's original host id: 2 new host id: null host > id before state transition: null > 2013-07-11 22:37:24,985 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Destroying vm VM[User|sg2] > 2013-07-11 22:37:24,985 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Cleaning up NICS > 2013-07-11 22:37:24,985 DEBUG [cloud.network.NetworkManagerImpl] > (UserVm-Scavenger-1:null) Cleaning network for vm: 8 > 2013-07-11 22:37:24,990 DEBUG [cloud.storage.VolumeManagerImpl] > (UserVm-Scavenger-1:null) Cleaning storage for vm: 8 > 2013-07-11 22:37:24,999 DEBUG [storage.volume.VolumeObject] > (UserVm-Scavenger-1:null) Failed to transit volume: 8, due to: > com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new > state from Expunging via DestroyRequested > 2013-07-11 22:37:24,999 DEBUG [storage.volume.VolumeObject] > (UserVm-Scavenger-1:null) F
[jira] [Created] (CLOUDSTACK-3491) delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException
prashant kumar mishra created CLOUDSTACK-3491:
-
Summary: delete host resulting NPE; Exception caught while
handling disconnect: java.lang.NullPointerException
Key: CLOUDSTACK-3491
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3491
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.2.0
Environment: vmware esxi 5.1
Reporter: prashant kumar mishra
Priority: Minor
Fix For: 4.2.0
Steps to reproduce
---
1-prapare a CS setup with vmware esxi5.1
2-put host in maintenance mode
3-Remove host from CS
Expected
--
Host should get remove without any exception
Actual
--
remove host was successful with NPE
Logs
2013-07-12 08:58:04,530 ERROR [agent.manager.AgentManagerImpl]
(AgentTaskPool-4:null) Exception caught while handling disconnect:
java.lang.NullPointerException
at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:805)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:68)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:111)
at
com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1435)
at
com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1454)
at
com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:885)
at
com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnect(ClusteredAgentManagerImpl.java:291)
at
com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnectWithoutInvestigation(ClusteredAgentManagerImpl.java:280)
at
com.cloud.agent.manager.AgentManagerImpl$DisconnectTask.run(AgentManagerImpl.java:986)
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-12 08:58:05,541 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-1:null) SeqA 7-9828: Processing Seq 7-9828: { Cmd ,
MgmtId: -1, via: 7, Ver: v1, Flags: 11,
[{"ConsoleProxyLoadReportCommand":{"_proxyVmId":41,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3491) delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-3491:
--
Attachment: Logs_DB.rar
> delete host resulting NPE; Exception caught while handling disconnect:
> java.lang.NullPointerException
> -
>
> Key: CLOUDSTACK-3491
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3491
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: vmware esxi 5.1
>Reporter: prashant kumar mishra
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> ---
> 1-prapare a CS setup with vmware esxi5.1
> 2-put host in maintenance mode
> 3-Remove host from CS
> Expected
> --
> Host should get remove without any exception
> Actual
> --
> remove host was successful with NPE
> Logs
>
> 2013-07-12 08:58:04,530 ERROR [agent.manager.AgentManagerImpl]
> (AgentTaskPool-4:null) Exception caught while handling disconnect:
> java.lang.NullPointerException
> at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:805)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:68)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:111)
> at
> com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1435)
> at
> com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1454)
> at
> com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:885)
> at
> com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnect(ClusteredAgentManagerImpl.java:291)
> at
> com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnectWithoutInvestigation(ClusteredAgentManagerImpl.java:280)
> at
> com.cloud.agent.manager.AgentManagerImpl$DisconnectTask.run(AgentManagerImpl.java:986)
> 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-12 08:58:05,541 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-1:null) SeqA 7-9828: Processing Seq 7-9828: { Cmd ,
> MgmtId: -1, via: 7, Ver: v1, Flags: 11,
> [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":41,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706759#comment-13706759 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit 22c6df0ba25f1f1fd3cf489a29ed1f4f4097c89c in branch refs/heads/4.2 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=22c6df0 ] CLOUDSTACK-2823: try passCmdLine some times if kernel < 2.6.34 and qemu < 1.1.0 on hypervisor (for instance, CentOS 6.4) > SystemVMs start fail on CentOS 6.4 > -- > > Key: CLOUDSTACK-2823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4, KVM > CloudStack master >Reporter: Wei Zhou >Priority: Blocker > > Host: > [root@cs-kvm015 ~]# virsh version > Compiled against library: libvirt 0.10.2 > Using library: libvirt 0.10.2 > Using API: QEMU 0.10.2 > Running hypervisor: QEMU 0.12.1 > Network: > em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 > (Can not connect outside) > em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* > Issue descripion > (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, > management) > (2) After I destroyed SystemVM, no new SystemVM will be created automatically. > This issue only exists on master branch > Deploy 4.1 successfully, and SystemVms work well. -- 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-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706760#comment-13706760 ] ASF subversion and git services commented on CLOUDSTACK-2823: - Commit dc9f7290e87c3a8270a68f4d06ec43b4521005ba in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dc9f729 ] CLOUDSTACK-2823: try passCmdLine some times if kernel < 2.6.34 and qemu < 1.1.0 on hypervisor (for instance, CentOS 6.4) > SystemVMs start fail on CentOS 6.4 > -- > > Key: CLOUDSTACK-2823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4, KVM > CloudStack master >Reporter: Wei Zhou >Priority: Blocker > > Host: > [root@cs-kvm015 ~]# virsh version > Compiled against library: libvirt 0.10.2 > Using library: libvirt 0.10.2 > Using API: QEMU 0.10.2 > Running hypervisor: QEMU 0.12.1 > Network: > em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 > (Can not connect outside) > em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* > Issue descripion > (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, > management) > (2) After I destroyed SystemVM, no new SystemVM will be created automatically. > This issue only exists on master branch > Deploy 4.1 successfully, and SystemVms work well. -- 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-2843) Support parallel VM deployment with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706762#comment-13706762 ] ASF subversion and git services commented on CLOUDSTACK-2843: - Commit dd91974920c8a8c6b10010aaa95e5ac6987d4c35 in branch refs/heads/sdnextensions from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dd91974 ] CLOUDSTACK-2843: added CopyCommand to the list of the commands controlled by execute.in.sequence.hypervisor.commands global config. This command was introduced by the Storage refactoring, and used for volume creation on the primary storage > Support parallel VM deployment with CloudStack > -- > > Key: CLOUDSTACK-2843 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843 > 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: Alena Prokharchyk >Assignee: Alena Prokharchyk > Fix For: 4.2.0 > > > When a user deploys multiple instances concurrently, the deployment of these > VMs are in fact queued up, so although CloudStack reports that all > deployments have started to be created, it would appear in reality that until > the 1st instance is deployed, the second, third, etc are queued and waiting > to be executed. > CS should be able to support parallel VM deployment assuming the cluster > resources can handle it. > As a part of it, we have to: > 1) Set executeInSequence=false for Start/Stop commands (also might make it > false for PrimaryStorageDownload command as well) > 2) Identify possible implication of turning off the synchronization for those > commands, and fix the problematic places in the code. -- 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-2823) SystemVMs start fail on CentOS 6.4
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-2823. Resolution: Fixed Assignee: Wei Zhou Closed as a temporary workaround has been applied on master and 4.2 branch. > SystemVMs start fail on CentOS 6.4 > -- > > Key: CLOUDSTACK-2823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4, KVM > CloudStack master >Reporter: Wei Zhou >Assignee: Wei Zhou >Priority: Blocker > > Host: > [root@cs-kvm015 ~]# virsh version > Compiled against library: libvirt 0.10.2 > Using library: libvirt 0.10.2 > Using API: QEMU 0.10.2 > Running hypervisor: QEMU 0.12.1 > Network: > em0 -> cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 > (Can not connect outside) > em1.103 -> cloudbr1 (Management, Storage) , IP: 192.168.103.* > Issue descripion > (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, > management) > (2) After I destroyed SystemVM, no new SystemVM will be created automatically. > This issue only exists on master branch > Deploy 4.1 successfully, and SystemVms work well. -- 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-3427) UI for Cisco UCS (Unified Computing System)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706763#comment-13706763 ] ASF subversion and git services commented on CLOUDSTACK-3427: - Commit e93ef73e9f9b880e8311eef365940151a1e56a2b in branch refs/heads/sdnextensions from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e93ef73 ] CLOUDSTACK-3427: UI > UCS manager > implement associatesUcsProfileToBlade API. > UI for Cisco UCS (Unified Computing System) > --- > > Key: CLOUDSTACK-3427 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3427 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- 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-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala reopened CLOUDSTACK-2987: - Previous commit 7b6b8d7a077478620232ea1ac4ec2304289e8661 is working fine. Fixing this again due to some merges after this commit. > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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-3094) [Add network]Adding a shared network to already deployed VM is failing.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706761#comment-13706761
]
ASF subversion and git services commented on CLOUDSTACK-3094:
-
Commit bdc7e4ce337f2f7cba8320808755119a835de07c in branch
refs/heads/sdnextensions from [~saksham]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bdc7e4c ]
CLOUDSTACK-3094: Adding a shared network to already deployed VM is failing.
Signed-off-by: Mice Xia
> [Add network]Adding a shared network to already deployed VM is failing.
> ---
>
> Key: CLOUDSTACK-3094
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3094
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
>Reporter: manasaveloori
>Assignee: Saksham Srivastava
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip, management-server.zip,
> mysqldump1.dmp, mysqldump1.dmp
>
>
> Steps:
> 1.Have a CS with advanced zone.
> 2.Create a VPC and a tier network.
> 3.Create a VM using the tier network.
> 4.Create a shared network.
> 5.Go to the VPC VM ->NICs->Add network. Select the shared network from
> the dropdown and add the network.
> Observation:
> Adding the shared network is failing with unexpected exception.
> 013-06-20 22:37:18,984 DEBUG [network.guru.DirectNetworkGuru]
> (Job-Executor-16:job-184) remove nic 80 secondary ip
> 2013-06-20 22:37:19,000 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-16:job-184) Removed nic id=80
> 2013-06-20 22:37:19,002 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-16:job-184) Revoving nic secondary ip entry ...
> 2013-06-20 22:37:19,003 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-16:job-184) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to add NIC to
> VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:916)
> at
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109)
> 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-20 22:37:19,004 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-16:job-184) Complete async job-184, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Unable to add NIC to
> VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
> 2013-06-20 22:37:20,113 INFO [vmware.resource.VmwareResource]
> (DirectAgent-125:10.147.40.29) vm_data command on domain router 10.147.40.181
> completed
> 2013-06-20 22:37:20,115 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-125:null) Seq 1-563282274: Response Received:
> 2013-06-20 22:37:20,116 DEBUG [agent.transport.Request]
> (DirectAgent-125:null) Seq 1-563282274: Processing: { Ans: , MgmtId:
> 6805241462820, via: 1, Ver: v1, Flags: 110,
> [{"Answer":{"result":true,"wait":0}}] }
> UI is listing all the nics even though adding a nic is failing.(Ifconfig –a
> in the VM not showing the added shared network)
> We are able to add multiple shared networks while deploying the VM(instance
> creation), but same is not happening through “ Add network option”
> Attaching the MS logs and DB logs.
--
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-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706772#comment-13706772
]
Sanjeev N commented on CLOUDSTACK-3489:
---
I see libvirt process dieing quite frequently.:
[root@Rack1Pod1Host14 ~]# /etc/init.d/libvirtd status
libvirtd dead but pid file exists
> Failed to start VR due to error in finalizeStart with KVM hypervisor
>
>
> Key: CLOUDSTACK-3489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
> 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 ACS 4.2 branch.
> Zone: Advanced with KVM cluster
> Stoarage: S3 and Local storage
>Reporter: Sanjeev N
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Failed to start VR due to error in finalizeStart with KVM hypervisor:
> KVM routing template being used:
> systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with KVM cluster
> 2.Use s3 as the secondary storage and Local storage as the primary storage
> 3.Use default cent os template to deploy guest vm
> Observations:
> ===
> VR was started as part of vm deployment process and it remained in starting
> state for a while. However later it was stopped with following exceptions:
> com.cloud.exception.AgentUnavailableException: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: com.cloud.utils.exception.ExecutionException: Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
> ... 19 more
> 2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete
> async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> Few more log snippets from mgmt server log file:
> 2013-07-12 02:36:21,128 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 4-691668978: Processing: { Ans: , MgmtId:
> 6615759585382, via: 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"r-13-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP name=r-13-VM
> eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1
> eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1
> eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=rout
[jira] [Updated] (CLOUDSTACK-3468) Failed to Deploy Instances with multiple VMWARE clusters when DVS is enabled at the Zone enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3468:
-
Summary: Failed to Deploy Instances with multiple VMWARE clusters when DVS
is enabled at the Zone enabled (was: Failed to create Guest port groups while
deploying instances with Mixed VMWARE clusters of different switches with which
instances are failed to deploy (Default - DVS, second cluster- StandardvSwitch))
> Failed to Deploy Instances with multiple VMWARE clusters when DVS is enabled
> at the Zone enabled
>
>
> Key: CLOUDSTACK-3468
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3468
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Sateesh Chodapuneedi
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: apilog.log.2013-07-09.gz,
> management-server.log.2013-07-09
>
>
> Setup :
> Two VMWARE clusters : Cluster1 is with DVS , Cluster2 is with Standard switch
> 1. Enable vmware.use.dvswitch to true
> 2. Configure Zone with with
> a)Physical network 1 with Mgmt traffic - With Label as vSwitch0
> b)Physical network 2 with guest & public traffic - Label as
> newdv1,,vmwaredvs
> 3. Add Cluster 1 during Zone deployment without overriding Public/Guest
> traffic as the labels are configured at the zone level
> 4. Create new account and deploy VM's on DVS Enabled cluster
> 5. Add second cluster with Standard switch specifying the traffic label as
> vSwitch0 with override option selected with Standard switch.
> 6. Update host tag to the host added under this cluster
> 7. Tried to deploy new VM under this cluster - I already have one instance
> and Router with Account 1 with this guestnetwork created with DVS cluster.
> Now I am trying to create one more instance on standard switch cluster using
> host TAGS.
> Observation:
> Failed to create Guest port groups while deploying instances with Mixed
> VMWARE clusters of different switches with which instances are failed to
> deploy (Default - DVS, second cluster- StandardvSwitch)
> Instance is failing to start :
> 2013-07-09 20:19:58,948 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"2bb4d376-99e8-449b-9b18-ec2f6887daf6","ip":"10.1.1.144","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:79:e9:00:04","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://792","isolationUri":"vlan://792","isSecurityGroupEnabled":false,"name":"newdv1,,vmwaredvs"}
> 2013-07-09 20:19:58,953 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare network on vmwaresvs
> P[newdv1:untagged] with name prefix: cloud.guest
> 2013-07-09 20:19:58,981 ERROR [vmware.mo.HypervisorHostHelper]
> (DirectAgent-49:10.102.192.23) Unable to find vSwitchnewdv1
> 2013-07-09 20:19:58,981 WARN [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) StartCommand failed due to Exception:
> java.lang.Exception
> Message: Unable to find vSwitchnewdv1
> java.lang.Exception: Unable to find vSwitchnewdv1
> at
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
> 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-09 20:19:58,983 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-49:null) Seq 7-1447821361: Response Received
--
This mes
[jira] [Commented] (CLOUDSTACK-3468) Failed to Deploy Instances with multiple VMWARE clusters when DVS is enabled at the Zone enabled
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706775#comment-13706775
]
Sailaja Mada commented on CLOUDSTACK-3468:
--
Tried with two DVS clusters - Cluster1 with DVS 1 , Cluster2 with DVS 2.
Instances are failed to deploy :
2013-07-12 11:16:23,361 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare NIC device based on NicTO:
{"deviceId":3,"networkRateMbps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"10.102.196.1","mac":"02:00:79:4b:00:05","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://100","isolationUri":"vlan://100","isSecurityGroupEnabled":false}
2013-07-12 11:16:23,365 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare network on vmwaredvs
P[dvSwitch23host:untagged] with name prefix: cloud.public
2013-07-12 11:16:23,379 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@2a10081b
2013-07-12 11:16:23,385 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch23host
2013-07-12 11:16:23,405 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch23host
2013-07-12 11:16:23,440 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Added custom field : cloud.gc.dvp
2013-07-12 11:16:23,458 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Preparing NIC device on dvSwitch : d9 9b 2f 50
f8 68 ff f6-3a 1e 12 22 c4 c5 ee e7
2013-07-12 11:16:23,459 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare NIC at new device
{"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:79:4b:00:05","key":-6,"backing":{"port":{"switchUuid":"d9
9b 2f 50 f8 68 ff f6-3a 1e 12 22 c4 c5 ee
e7","portgroupKey":"dvportgroup-3984"}},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":3}}
2013-07-12 11:16:23,459 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare NIC device based on NicTO:
{"deviceId":4,"networkRateMbps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"10.102.196.1","mac":"02:00:1a:b6:00:06","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://100","isolationUri":"vlan://100","isSecurityGroupEnabled":false}
2013-07-12 11:16:23,464 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare network on vmwaredvs
P[dvSwitch23host:untagged] with name prefix: cloud.public
2013-07-12 11:16:23,478 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Found distributed vSwitch
com.vmware.vim25.ManagedObjectReference@4090b16e
2013-07-12 11:16:23,483 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Found Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch23host
2013-07-12 11:16:23,505 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Updating Distributed Virtual Port group
cloud.public.100.0.1-dvSwitch23host
2013-07-12 11:16:23,555 DEBUG [vmware.mo.HypervisorHostHelper]
(DirectAgent-112:10.102.192.23) Added custom field : cloud.gc.dvp
2013-07-12 11:16:23,573 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Preparing NIC device on dvSwitch : d9 9b 2f 50
f8 68 ff f6-3a 1e 12 22 c4 c5 ee e7
2013-07-12 11:16:23,574 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Prepare NIC at new device
{"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:1a:b6:00:06","key":-7,"backing":{"port":{"switchUuid":"d9
9b 2f 50 f8 68 ff f6-3a 1e 12 22 c4 c5 ee
e7","portgroupKey":"dvportgroup-3984"}},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":4}}
2013-07-12 11:16:23,575 DEBUG [vmware.mo.HostMO]
(DirectAgent-112:10.102.192.23) find VM r-4-VM on host
2013-07-12 11:16:23,575 DEBUG [vmware.mo.HostMO]
(DirectAgent-112:10.102.192.23) VM r-4-VM found in host cache
2013-07-12 11:16:23,592 INFO [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) Configure VNC port for VM r-4-VM, port: 5913,
host: 10.102.192.23
2013-07-12 11:16:23,657 WARN [vmware.resource.VmwareResource]
(DirectAgent-112:10.102.192.23) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: A specified parameter was not correct.
spec.deviceChange.device.port.switchUuid
java.lang.RuntimeException: A specified parameter was not correct.
spec.deviceChange.device.port.switchUuid
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.V
[jira] [Updated] (CLOUDSTACK-3468) Failed to Deploy Instances with multiple VMWARE clusters when DVS is enabled at the Zone level
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3468:
-
Summary: Failed to Deploy Instances with multiple VMWARE clusters when DVS
is enabled at the Zone level (was: Failed to Deploy Instances with multiple
VMWARE clusters when DVS is enabled at the Zone enabled)
> Failed to Deploy Instances with multiple VMWARE clusters when DVS is enabled
> at the Zone level
> --
>
> Key: CLOUDSTACK-3468
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3468
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Sateesh Chodapuneedi
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: apilog.log.2013-07-09.gz,
> management-server.log.2013-07-09
>
>
> Setup :
> Two VMWARE clusters : Cluster1 is with DVS , Cluster2 is with Standard switch
> 1. Enable vmware.use.dvswitch to true
> 2. Configure Zone with with
> a)Physical network 1 with Mgmt traffic - With Label as vSwitch0
> b)Physical network 2 with guest & public traffic - Label as
> newdv1,,vmwaredvs
> 3. Add Cluster 1 during Zone deployment without overriding Public/Guest
> traffic as the labels are configured at the zone level
> 4. Create new account and deploy VM's on DVS Enabled cluster
> 5. Add second cluster with Standard switch specifying the traffic label as
> vSwitch0 with override option selected with Standard switch.
> 6. Update host tag to the host added under this cluster
> 7. Tried to deploy new VM under this cluster - I already have one instance
> and Router with Account 1 with this guestnetwork created with DVS cluster.
> Now I am trying to create one more instance on standard switch cluster using
> host TAGS.
> Observation:
> Failed to create Guest port groups while deploying instances with Mixed
> VMWARE clusters of different switches with which instances are failed to
> deploy (Default - DVS, second cluster- StandardvSwitch)
> Instance is failing to start :
> 2013-07-09 20:19:58,948 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"2bb4d376-99e8-449b-9b18-ec2f6887daf6","ip":"10.1.1.144","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:79:e9:00:04","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://792","isolationUri":"vlan://792","isSecurityGroupEnabled":false,"name":"newdv1,,vmwaredvs"}
> 2013-07-09 20:19:58,953 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare network on vmwaresvs
> P[newdv1:untagged] with name prefix: cloud.guest
> 2013-07-09 20:19:58,981 ERROR [vmware.mo.HypervisorHostHelper]
> (DirectAgent-49:10.102.192.23) Unable to find vSwitchnewdv1
> 2013-07-09 20:19:58,981 WARN [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) StartCommand failed due to Exception:
> java.lang.Exception
> Message: Unable to find vSwitchnewdv1
> java.lang.Exception: Unable to find vSwitchnewdv1
> at
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
> 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-09 20:19:58,983 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-49:null) Seq 7-1447821361: Response Received
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA adminis
[jira] [Closed] (CLOUDSTACK-2893) The Agent attempts to re-create a already existing Libvirt Storage pool when creating a volume
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou closed CLOUDSTACK-2893.
Resolution: Duplicate
This duplicates CLOUDSTACK-2780 which is a libvirt issue and being worked on by
Redhat community. We need a temporary workaound in CloudStack.
> The Agent attempts to re-create a already existing Libvirt Storage pool when
> creating a volume
> --
>
> Key: CLOUDSTACK-2893
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2893
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
>Affects Versions: 4.1.0
> Environment: - Ubuntu 12.04.2
> - Libvirt 1.0.2 (Cloud Archive PPA from Canonical)
> - CloudStack 4.1
>Reporter: Wido den Hollander
>Assignee: Wei Zhou
> Fix For: 4.1.1
>
>
> When trying to deploy a new Instance I saw the following Exception in my logs:
> 2013-06-07 08:19:18,832 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-7:null) Processing command:
> com.cloud.agent.api.storage.CreateCommand
> 2013-06-07 08:19:18,840 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-7:null) Failed to create volume:
> com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted
> 2013-06-07 08:19:18,841 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-7:null) Seq 12-477959384: { Ans: , MgmtId:
> 207376724852, via: 12, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception:
> com.cloud.utils.exception.CloudRuntimeException\nMessage:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted\nStack:
> com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: Requested operation is not valid: Target
> '/mnt/52801816-fe44-3a2b-a147-bb768eeea295' is already mounted\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getStoragePool(LibvirtStorageAdaptor.java:427)\n\t
> at
> com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.getStoragePool(KVMStoragePoolManager.java:71)\n\t
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1271)\n\t
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1072)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:525)\n\t
> at 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}}] }
> The Agent seems to try and create the storage pool again and Libvirt will try
> to mount it, but it is already mounted.
> The Storage pool is actually already running on that Hypervisor, but there
> seems to be a miscommuncation between libvirt and the Agent.
--
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-3360) user can not Delete his own ISO in case of project
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-3360. - Resolution: Implemented Already implemented in the fix of https://issues.apache.org/jira/browse/CLOUDSTACK-3361. > user can not Delete his own ISO in case of project > --- > > Key: CLOUDSTACK-3360 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3360 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Projects >Affects Versions: 4.2.0 > Environment: build: > CloudPlatform-4.2-144-rhel6.3 >Reporter: shweta agarwal >Assignee: Sanjay Tripathi > Fix For: 4.2.0 > > > Repro steps: > 1. Create a domain and some accounts /user in that domain > 2. Create a project in that domain > 3. Create a private/ public ISO in the project > 4. Delete the self created ISO > Bug: gets message in case of public iso > Domain Admin and regular users can modify only their own Public templates > MS snippet: > 013-07-04 17:20:18,820 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-21:job-26) Executing > org.apache.cloudstack.api.command.user.iso.DeleteIsoCmd for job-26 > 2013-07-04 17:20:18,866 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-21:job-26) Unexpected exception while executing > org.apache.cloudstack.api.command.user.iso.DeleteIsoCmd > com.cloud.exception.PermissionDeniedException: Domain Admin and regular users > can modify only their own Public templates > at com.cloud.acl.DomainChecker.checkAccess(DomainChecker.java:113) > at > com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:403) > at > com.cloud.template.TemplateManagerImpl.deleteIso(TemplateManagerImpl.java:1478) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.iso.DeleteIsoCmd.execute(DeleteIsoCmd.java:110) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-07-04 17:20:18,868 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-21:job-26) Complete async job-26, jobStatus: 2, resultCode: > 530, result: Error Code: 530 Error text: Domain Admin and regular users can > modify only their own Public templates > 2013-07-04 17:20:20,607 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-323:null) Ping from 1 > 2013-07-04 17:20:22,077 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) > ===START=== 10.146.0.12 -- GET > command=queryAsyncJobResult&jobId=49e17cf5-d860-4b58-8c86-1867be1b22f4&response=json&sessionkey=8rczMjm4sfljFOEi6dL2xT631sc%3D&projectid=a548b266-18e5-4f36 > Bug : gets message in case of private iso :Unable to delete iso . Permission > denied. > 2013-07-04 17:23:17,383 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-23:job-28) Unexpected exception while executing > org.apache.cloudstack.api.command.user.iso.DeleteIsoCmd > com.cloud.exception.PermissionDeniedException: Unable to delete iso . > Permission denied. > at > com.cloud.template.TemplateAdapterBase.accountAndUserValidation(TemplateAdapterBase.java:302) > at > com.cloud.template.TemplateAdapterBase.prepareDelete(TemplateAdapterBase.java:372) > at > com.cloud.template.HypervisorTemplateAdapter.prepareDelete(HypervisorTemplateAdapter.java:419) > at > com.cloud.template.TemplateManagerImpl.deleteIso(TemplateManagerImpl.java:1494) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.iso.DeleteIsoCmd.execute(DeleteIsoCmd.java:110) > 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.Fut
[jira] [Updated] (CLOUDSTACK-3485) NPE while getting instance ID from Asyn Job when publishing async job events on eventbus
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy updated CLOUDSTACK-3485: - Summary: NPE while getting instance ID from Asyn Job when publishing async job events on eventbus (was: When RabbitMQ plugin enabled with the simulator, simulator setup results in Unable to schedule async job for command org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd) > NPE while getting instance ID from Asyn Job when publishing async job events > on eventbus > > > Key: CLOUDSTACK-3485 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3485 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: simulator >Reporter: Chip Childers >Assignee: Murali Reddy >Priority: Critical > > This may also effect 4.1, but I'm unsure. Was the RabbitMQ plugin tested in > a non-simulated environment (i.e.: did anyone enable this plugin and > configure a zone)? This may just be a simulator + rabbit combination issue. > Removing the rabbitMQ plugin and doing the steps below results in no errors. > Steps to reproduce on master: > I edit client/tomcatconf/simulatorComponentContext.xml.in to include the > rabbit mq plugin. > I then confirm that I see a login event published for a valid admin user > login to the gui. > I then restart and reset the mgmt server with: > mvn -Pdeveloper -Dsimulator clean install; mvn -Pdeveloper -pl developer > -Ddeploydb; mvn -Pdeveloper -pl developer -Ddeploydb-simulator; mvn -pl > client jetty:run > I then run the simulator setup as: > mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl > :cloud-marvin integration-test > Then I see the following errors in the console from the jetty:run command: > WARN [apache.cloudstack.alerts] (Cluster-Notification-1:) alertType:: 14 // > dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management > server node 127.0.0.1 is up > WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) Notifying > management server join event took 21 ms > WARN [cloud.async.AsyncJobManagerImpl] (507572448@qtp-656336336-3:) Unable > to schedule async job for command > org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd, > unexpected exception. > java.lang.NullPointerException > at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337) > at > com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at >
[jira] [Reopened] (CLOUDSTACK-728) Add support for Nicira NVP to VmWare hypervisor orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Trippaers reopened CLOUDSTACK-728: --- As it turns out, the support was limited to particular test cases. The current implementation need some refactoring to get done properly. > Add support for Nicira NVP to VmWare hypervisor orchestration > - > > Key: CLOUDSTACK-728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-728 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3485) NPE while getting instance ID from Asyn Job when publishing async job events on eventbus
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706782#comment-13706782 ] ASF subversion and git services commented on CLOUDSTACK-3485: - Commit b3fd25d45e4a361adb489eb3a09ec240a5edb438 in branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3fd25d ] CLOUDSTACK-3485: NPE while getting instance ID from Asyn Job when publishing async job events on eventbus handing case where instance id is null in the asyn job, while publishing asyn job events on to event bus > NPE while getting instance ID from Asyn Job when publishing async job events > on eventbus > > > Key: CLOUDSTACK-3485 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3485 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: simulator >Reporter: Chip Childers >Assignee: Murali Reddy >Priority: Critical > > This may also effect 4.1, but I'm unsure. Was the RabbitMQ plugin tested in > a non-simulated environment (i.e.: did anyone enable this plugin and > configure a zone)? This may just be a simulator + rabbit combination issue. > Removing the rabbitMQ plugin and doing the steps below results in no errors. > Steps to reproduce on master: > I edit client/tomcatconf/simulatorComponentContext.xml.in to include the > rabbit mq plugin. > I then confirm that I see a login event published for a valid admin user > login to the gui. > I then restart and reset the mgmt server with: > mvn -Pdeveloper -Dsimulator clean install; mvn -Pdeveloper -pl developer > -Ddeploydb; mvn -Pdeveloper -pl developer -Ddeploydb-simulator; mvn -pl > client jetty:run > I then run the simulator setup as: > mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl > :cloud-marvin integration-test > Then I see the following errors in the console from the jetty:run command: > WARN [apache.cloudstack.alerts] (Cluster-Notification-1:) alertType:: 14 // > dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management > server node 127.0.0.1 is up > WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) Notifying > management server join event took 21 ms > WARN [cloud.async.AsyncJobManagerImpl] (507572448@qtp-656336336-3:) Unable > to schedule async job for command > org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd, > unexpected exception. > java.lang.NullPointerException > at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337) > at > com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
[jira] [Assigned] (CLOUDSTACK-3454) [Automation] Basic zone - test case failed to create network
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3454:
--
Assignee: Jayapal Reddy
Jayapal, This issue could be probably with the test itself. Can you investigate.
> [Automation] Basic zone - test case failed to create network
> -
>
> Key: CLOUDSTACK-3454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3454
> 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: Basic Zone - automation
>Reporter: Rayees Namathponnan
>Assignee: Jayapal Reddy
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Basic zone test cases failed to create network with below error
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 208, in
> run
> self.setUp()
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 291, in
> setUp
> self.setupContext(ancestor)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 314, in
> setupContext
> try_run(context, names)
> File "/usr/local/lib/python2.7/site-packages/nose/util.py", line 469, in
> try_run
> return func()
> File
> "/Repo_30X/ipcl/cloudstack/test/integration/smoke/test_portable_publicip.py",
> line 189, in setUpClass
> cls.account.domainid
> File
> "/usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py", line
> 1851, in create
> return Network(apiclient.createNetwork(cmd).__dict__)
> File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
> line 1641, in createNetwork
> response = self.connection.marvin_request(command,
> response_type=response, method=method)
> File
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line
> 223, in marvin_request
> response = jsonHelper.getResultObj(response.json(), response_type)
> File "/usr/local/lib/python2.7/site-packages/marvin/jsonHelper.py", line
> 128, in getResultObj
> raise
> cloudstackException.cloudstackAPIException(responseName.replace("response",
> ""), errMsg)
> cloudstackAPIException: Execute cmd: createnetwork failed, due to: errorCode:
> 431, errorText:Only AclType=Domain can be specified for network creation in
> Basic zone
> Test cases failed
> 1) integration/smoke/test_portable_publicip.py
> 2)
--
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-3485) NPE while getting instance ID from Asyn Job when publishing async job events on eventbus
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706790#comment-13706790 ] ASF subversion and git services commented on CLOUDSTACK-3485: - Commit f3a2fc22bf21b8a7019d10f4a864f7427332a9b6 in branch refs/heads/4.2 from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f3a2fc2 ] CLOUDSTACK-3485: NPE while getting instance ID from Asyn Job when publishing async job events on eventbus handing case where instance id is null in the asyn job, while publishing asyn job events on to event bus > NPE while getting instance ID from Asyn Job when publishing async job events > on eventbus > > > Key: CLOUDSTACK-3485 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3485 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: simulator >Reporter: Chip Childers >Assignee: Murali Reddy >Priority: Critical > > This may also effect 4.1, but I'm unsure. Was the RabbitMQ plugin tested in > a non-simulated environment (i.e.: did anyone enable this plugin and > configure a zone)? This may just be a simulator + rabbit combination issue. > Removing the rabbitMQ plugin and doing the steps below results in no errors. > Steps to reproduce on master: > I edit client/tomcatconf/simulatorComponentContext.xml.in to include the > rabbit mq plugin. > I then confirm that I see a login event published for a valid admin user > login to the gui. > I then restart and reset the mgmt server with: > mvn -Pdeveloper -Dsimulator clean install; mvn -Pdeveloper -pl developer > -Ddeploydb; mvn -Pdeveloper -pl developer -Ddeploydb-simulator; mvn -pl > client jetty:run > I then run the simulator setup as: > mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl > :cloud-marvin integration-test > Then I see the following errors in the console from the jetty:run command: > WARN [apache.cloudstack.alerts] (Cluster-Notification-1:) alertType:: 14 // > dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management > server node 127.0.0.1 is up > WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) Notifying > management server join event took 21 ms > WARN [cloud.async.AsyncJobManagerImpl] (507572448@qtp-656336336-3:) Unable > to schedule async job for command > org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd, > unexpected exception. > java.lang.NullPointerException > at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337) > at > com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) >
[jira] [Resolved] (CLOUDSTACK-3485) NPE while getting instance ID from Asyn Job when publishing async job events on eventbus
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-3485. -- Resolution: Fixed handling the case where job's instance id could be null while getting the UUID of instance > NPE while getting instance ID from Asyn Job when publishing async job events > on eventbus > > > Key: CLOUDSTACK-3485 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3485 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: simulator >Reporter: Chip Childers >Assignee: Murali Reddy >Priority: Critical > > This may also effect 4.1, but I'm unsure. Was the RabbitMQ plugin tested in > a non-simulated environment (i.e.: did anyone enable this plugin and > configure a zone)? This may just be a simulator + rabbit combination issue. > Removing the rabbitMQ plugin and doing the steps below results in no errors. > Steps to reproduce on master: > I edit client/tomcatconf/simulatorComponentContext.xml.in to include the > rabbit mq plugin. > I then confirm that I see a login event published for a valid admin user > login to the gui. > I then restart and reset the mgmt server with: > mvn -Pdeveloper -Dsimulator clean install; mvn -Pdeveloper -pl developer > -Ddeploydb; mvn -Pdeveloper -pl developer -Ddeploydb-simulator; mvn -pl > client jetty:run > I then run the simulator setup as: > mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl > :cloud-marvin integration-test > Then I see the following errors in the console from the jetty:run command: > WARN [apache.cloudstack.alerts] (Cluster-Notification-1:) alertType:: 14 // > dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management > server node 127.0.0.1 is up > WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) Notifying > management server join event took 21 ms > WARN [cloud.async.AsyncJobManagerImpl] (507572448@qtp-656336336-3:) Unable > to schedule async job for command > org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd, > unexpected exception. > java.lang.NullPointerException > at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337) > at > com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > at > org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) > at > org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > ERROR [cloud.api.ApiServer] (507572448@qtp-656336336-3:) unhandled exception > executing api comman
[jira] [Created] (CLOUDSTACK-3492) [Regression]Update Resource Count for an account is updating the primary storage incorretly
Sailaja Mada created CLOUDSTACK-3492: Summary: [Regression]Update Resource Count for an account is updating the primary storage incorretly Key: CLOUDSTACK-3492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3492 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: Sailaja Mada Priority: Critical Steps: 1. Deploy instance with user account1 2. Get the primary storage is usage using ListAccounts- It is 10 GB same as ROOT disk size of this instance 3. Now tried Update Resource Count for this account. With this when verified the usage using listAccounts it increased to 11 GB 4. Added one DATA disk of 5 GB . With which usage has become 16 GB 5. Then tried Update Resource Count for this account. With this when verified the usage using listAccounts it decreased to 11 GB Observation : Update Resource Count for an account is updating the primary storage incorrectly (Attached API log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-3493:
--
Attachment: management-server.zip
> Attach volume to VM is failing in case of Primary-Localstorage .
>
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> 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: 4.2 stable build
>Reporter: manasaveloori
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-Xen.(System VMs not in local storage)
> 2.Deploy a VM with default template.
> 3.Create a Volume.
> 4.Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
> 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
> ===END=== 10.252.192.69 -- GET
> command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: CLUSTER and HOST
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Can't move volume between scope:
> CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> Attaching the MS logs.
--
This message is automatically generated by JIRA
[jira] [Created] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
manasaveloori created CLOUDSTACK-3493:
-
Summary: Attach volume to VM is failing in case of
Primary-Localstorage .
Key: CLOUDSTACK-3493
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
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: 4.2 stable build
Reporter: manasaveloori
Priority: Blocker
Fix For: 4.2.0
Attachments: management-server.zip
1. Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
Host-Xen.(System VMs not in local storage)
2. Deploy a VM with default template.
3. Create a Volume.
4. Attach the created volume to the VM.
Observed the following exception :
2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
cmdOriginator: null, cmdInfo:
{"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===END=== 10.252.192.69 -- GET
command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-10:job-96) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-10:job-96) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
scope: CLUSTER and HOST
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: Can't move volume between scope: CLUSTER
and HOST
2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===START=== 10.252.192.69 -- GET
command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-37:null) Ping from 1
2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-13:null) Async job-96 completed
2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
===END=== 10.252.192.69 -- GET
command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
Attaching the MS logs.
--
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-3482) primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and try to detach volume when VM is running state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706795#comment-13706795
]
sadhu suresh commented on CLOUDSTACK-3482:
--
It also fails in this another scenario :
attach a volume on running instance and reboot the instance and try to detach
the attach volume.
it failed with below error message
Failed to detach volume: xx from VM: vm3; Failed dettach volume:
6a5d2542-2333-4855-bd87-675c7ead26b5, due to The VM rejected the attempt to
detach the device.
> primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and
> try to detach volume when VM is running state
> ---
>
> Key: CLOUDSTACK-3482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
> Attachments: management-server.rar
>
>
> detachvolume is failed when we attach voulme on stopped vm and try to detach
> volume when VM is running state
> steps:
> 1. deploy a vm1
> 2. perform snapshot on root volume
> 3.create a volume from snapshot i,e vol1
> 4.deploy another vm2
> 5.attach/detach a volume created in step3
> 6 volume was successfully attached and detach and then .stop the vm2
> 7.attach the volume "vol1" to vm2
> 8.start the VM2
> 9 try to detach "vol1" from vm2
> Actual result:
> fail to detach the volume from vm and throws below error when we first try to
> detach the volume.
> and later if we try to detach volume again and its failing with "failed
> dettach volume: 960eba57-279b-48a6-b94d-44ef75fe134b, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"
> ** 49. row ***
> id: 67
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548167660","ctxAccountId":"2","ctxStartEventId":"261"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to The VM rejected the attempt to
> detach the device."}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:37:52
> last_updated: 2013-07-11 18:37:53
>last_polled: NULL
>removed: NULL
> uuid: e36c7928-3b6b-4cb5-90fb-44dc9378e740
>id: 68
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548256841","ctxAccountId":"2","ctxStartEventId":"264"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:39:22
> last_updated: 2013-07-11 18:49:22
>last_polled: 2013-07-11 18:49:19
>removed: 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] [Updated] (CLOUDSTACK-3482) primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and try to detach volume when VM is running state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sadhu suresh updated CLOUDSTACK-3482:
-
Priority: Critical (was: Major)
> primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and
> try to detach volume when VM is running state
> ---
>
> Key: CLOUDSTACK-3482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Priority: Critical
> Attachments: management-server.rar
>
>
> detachvolume is failed when we attach voulme on stopped vm and try to detach
> volume when VM is running state
> steps:
> 1. deploy a vm1
> 2. perform snapshot on root volume
> 3.create a volume from snapshot i,e vol1
> 4.deploy another vm2
> 5.attach/detach a volume created in step3
> 6 volume was successfully attached and detach and then .stop the vm2
> 7.attach the volume "vol1" to vm2
> 8.start the VM2
> 9 try to detach "vol1" from vm2
> Actual result:
> fail to detach the volume from vm and throws below error when we first try to
> detach the volume.
> and later if we try to detach volume again and its failing with "failed
> dettach volume: 960eba57-279b-48a6-b94d-44ef75fe134b, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"
> ** 49. row ***
> id: 67
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548167660","ctxAccountId":"2","ctxStartEventId":"261"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to The VM rejected the attempt to
> detach the device."}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:37:52
> last_updated: 2013-07-11 18:37:53
>last_polled: NULL
>removed: NULL
> uuid: e36c7928-3b6b-4cb5-90fb-44dc9378e740
>id: 68
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548256841","ctxAccountId":"2","ctxStartEventId":"264"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:39:22
> last_updated: 2013-07-11 18:49:22
>last_polled: 2013-07-11 18:49:19
>removed: 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] [Commented] (CLOUDSTACK-3362) upload Custom SSL Certificate failed on UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706802#comment-13706802
]
ASF subversion and git services commented on CLOUDSTACK-3362:
-
Commit 838cfa2bb6dadf848cf4f3090ef0ce338d0443c2 in branch refs/heads/4.2 from
[~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=838cfa2 ]
CLOUDSTACK-3362: use POST instead of GET and encode/decode cert/key in
uploadCustomCertificate
> upload Custom SSL Certificate failed on UI
> --
>
> Key: CLOUDSTACK-3362
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3362
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> I tried to use my SSL certificate, but failed.
> (1) When I input both certificate and private key, it returned "Failed to
> update SSL Certificate" message, without any log in management-server.log
> I think it is because of the length of keys. So I removed some characters
> from private key.
> (2) After I removed some characters from private key, it returned another
> message "Received value -BEGIN CERTIFICATE- *-END
> CERTIFICATE- for parameter certificate is invalid, contains illegal ASCII
> non-printable characters"
> I think it is because the url was not encoded, so I added todb in
> ui/scripts/ui-custom/physicalResources.js
> diff --git a/ui/scripts/ui-custom/physicalResources.js
> b/ui/scripts/ui-custom/physicalResources.js
> index 529adcf..7dc40ea 100644
> --- a/ui/scripts/ui-custom/physicalResources.js
> +++ b/ui/scripts/ui-custom/physicalResources.js
> @@ -82,8 +82,8 @@
> $.ajax({
>url: createURL('uploadCustomCertificate'),
>data: {
> -certificate: args.data.certificate,
> -privatekey: args.data.privatekey,
> +certificate: todb(args.data.certificate),
> +privatekey: todb(args.data.privatekey),
> domainsuffix: args.data.domainsuffix
>},
>dataType: 'json',
> After that, CLOUDSTACK-3244 appeared.
> I tested on master branch, but I think 4.1.0 and 4.2 have the same issue.
--
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-3368) download URLs of ISOs and templates become invalid after recreating SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706801#comment-13706801 ] ASF subversion and git services commented on CLOUDSTACK-3368: - Commit b3ac91ef6391533e72c5a7524403dad5e65dddbf in branch refs/heads/4.2 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3ac91e ] CLOUDSTACK-3368: clear download URLs when create SSVM and validate download URLs > download URLs of ISOs and templates become invalid after recreating SSVM > - > > Key: CLOUDSTACK-3368 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3368 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > > After destroy/create SSVM, the download URLs of ISOs and templates become > invalid, because > (1) the public ip of SSVM changes > (2) the path doesnot exist in SSVM even SSVM has the same public ip. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2168) configured LDAP values not shown in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sadhu suresh updated CLOUDSTACK-2168:
-
Priority: Blocker (was: Critical)
> configured LDAP values not shown in UI
> --
>
> Key: CLOUDSTACK-2168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2168
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Assignee: Pranav Saxena
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloudstack-2168.patch, screenshot_ldap.jpg
>
>
> Steps:
> 1.Configured the LDAP through API
> http://10.147.59.83:8096/client/api?command=ldapConfig&hostname=10.147.38.163&searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcom&queryfilter=%28%26%28mail%3D%25e%29%29&port=389&response=json
> 2.Open the CS web console and navigate to LDAP configuration section
> 3.check the displayed LDAP configured values
> Actual result:
> Even though LDAP configuration happens successfully but UI fail to display
> the Values.
> even firebug response shows the configured ldap values but UI fail to display
> the values.
> UI:
> ---
> Hostname Query FilterSearch Base LDAP Port SSL
> Quickview
> No data to show
> firebug response:
>
> http://10.147.59.83:8080/client/api?command=ldapConfig&listall=true&response=json&sessionkey=2G5uy2a4z%2F31Mi3yaVKmvXc10a4%3D&listAll=true&page=1&pagesize=20&_=1366791925255
> { "ldapconfigresponse" : { "ldapconfig" :
> {"hostname":"10.147.38.163","port":"389","ssl":"false","searchbase":"CN=Users,DC=hyd-qa,DC=com","queryfilter":"(&(mail=%e))","binddn":""}
> } }
--
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-1475) RegisterISO error after Update SSL Certificate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706800#comment-13706800 ] ASF subversion and git services commented on CLOUDSTACK-1475: - Commit b2a077dfff5ba71723187ce970a4aa040794fe82 in branch refs/heads/4.2 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b2a077d ] CLOUDSTACK-1475: fix RegisterISO error after Update SSL Certificate > RegisterISO error after Update SSL Certificate > -- > > Key: CLOUDSTACK-1475 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1475 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.1.1, 4.2.0 > > > After updating SSL Certificate, and restart cloud-management service. > whentry to registerISO from the url which is shown in "downloadISO", it will > fail with the error message "sun.security.validator.ValidatorException: PKIX > path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target". > Another problem is that, the url of DownloadISO always(!) be > **-**-**-**.realhostip.com -- 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-3492) [Regression]Update Resource Count for an account is updating the primary storage incorretly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3492: - Attachment: management-server.log apilog.log > [Regression]Update Resource Count for an account is updating the primary > storage incorretly > > > Key: CLOUDSTACK-3492 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3492 > 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: Sailaja Mada >Priority: Critical > Attachments: apilog.log, management-server.log > > > Steps: > 1. Deploy instance with user account1 > 2. Get the primary storage is usage using ListAccounts- It is 10 GB same as > ROOT disk size of this instance > 3. Now tried Update Resource Count for this account. With this when verified > the usage using listAccounts it increased to 11 GB > 4. Added one DATA disk of 5 GB . With which usage has become 16 GB > 5. Then tried Update Resource Count for this account. With this when > verified the usage using listAccounts it decreased to 11 GB > Observation : > Update Resource Count for an account is updating the primary storage > incorrectly (Attached API log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3492) [Regression]Update Resource Count for an account is updating the primary storage incorretly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reassigned CLOUDSTACK-3492: --- Assignee: Sanjay Tripathi > [Regression]Update Resource Count for an account is updating the primary > storage incorretly > > > Key: CLOUDSTACK-3492 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3492 > 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: Sailaja Mada >Assignee: Sanjay Tripathi >Priority: Critical > Attachments: apilog.log, management-server.log > > > Steps: > 1. Deploy instance with user account1 > 2. Get the primary storage is usage using ListAccounts- It is 10 GB same as > ROOT disk size of this instance > 3. Now tried Update Resource Count for this account. With this when verified > the usage using listAccounts it increased to 11 GB > 4. Added one DATA disk of 5 GB . With which usage has become 16 GB > 5. Then tried Update Resource Count for this account. With this when > verified the usage using listAccounts it decreased to 11 GB > Observation : > Update Resource Count for an account is updating the primary storage > incorrectly (Attached API log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3493:
--
Assignee: Koushik Das
> Attach volume to VM is failing in case of Primary-Localstorage .
>
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> 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: 4.2 stable build
>Reporter: manasaveloori
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-Xen.(System VMs not in local storage)
> 2.Deploy a VM with default template.
> 3.Create a Volume.
> 4.Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
> 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
> ===END=== 10.252.192.69 -- GET
> command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: CLUSTER and HOST
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Can't move volume between scope:
> CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> Attaching the MS logs.
--
This mes
[jira] [Commented] (CLOUDSTACK-3376) NPE: resource count calculation from the account manager on account cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706808#comment-13706808 ] Sanjay Tripathi commented on CLOUDSTACK-3376: - Fix is available for review at: https://reviews.apache.org/r/12499/ > NPE: resource count calculation from the account manager on account cleanup > --- > > Key: CLOUDSTACK-3376 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3376 > 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: Prasanna Santhanam >Assignee: Sanjay Tripathi > Fix For: 4.2.0 > > Attachments: 483.tar.bz2 > > > During account cleanup on one of the accounts the following NPE was > encountered on a template that had failed to delete. > Attaching complete logs. This was an XCP 1.6 setup of cloudstack master > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 > 06:46:44,066 DEBUG [db.Transaction.Transaction] (AccountChecker-1:null) > Rolling back the transaction: Time = 2 Name = > -AccountManagerImpl$AccountCleanupTask.run:1481-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679; > called by > -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-ResourceLimitManagerImpl.recalculateResourceCount:702-HypervisorTemplateAdapter.delete:277-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-TemplateManagerImpl.delete:748-AccountManagerImpl.cleanupAccount:592-AccountManagerImpl$AccountCleanupTask.run:1488-Executors$RunnableAdapter.call:471 > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 > 06:46:44,066 WARN [cloud.user.AccountManagerImpl] (AccountChecker-1:null) > Failed to delete template while removing account: Public template-5D26S2 due > to: > Jul 4 23:46:44 java.lang.NullPointerException > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:277) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:748) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.lang.T
[jira] [Updated] (CLOUDSTACK-3376) NPE: resource count calculation from the account manager on account cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-3376: Status: Ready To Review (was: In Progress) > NPE: resource count calculation from the account manager on account cleanup > --- > > Key: CLOUDSTACK-3376 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3376 > 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: Prasanna Santhanam >Assignee: Sanjay Tripathi > Fix For: 4.2.0 > > Attachments: 483.tar.bz2 > > > During account cleanup on one of the accounts the following NPE was > encountered on a template that had failed to delete. > Attaching complete logs. This was an XCP 1.6 setup of cloudstack master > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 > 06:46:44,066 DEBUG [db.Transaction.Transaction] (AccountChecker-1:null) > Rolling back the transaction: Time = 2 Name = > -AccountManagerImpl$AccountCleanupTask.run:1481-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679; > called by > -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-ResourceLimitManagerImpl.recalculateResourceCount:702-HypervisorTemplateAdapter.delete:277-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-TemplateManagerImpl.delete:748-AccountManagerImpl.cleanupAccount:592-AccountManagerImpl$AccountCleanupTask.run:1488-Executors$RunnableAdapter.call:471 > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 2013-07-05 > 06:46:44,066 WARN [cloud.user.AccountManagerImpl] (AccountChecker-1:null) > Failed to delete template while removing account: Public template-5D26S2 due > to: > Jul 4 23:46:44 java.lang.NullPointerException > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateAccountResourceCount(ResourceLimitManagerImpl.java:814) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:702) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.template.HypervisorTemplateAdapter.delete(HypervisorTemplateAdapter.java:277) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.template.TemplateManagerImpl.delete(TemplateManagerImpl.java:748) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:592) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1488) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com at > java.lang.Thread.run(Thread.java:679) > Jul 4 23:46:44 cloudstack-centos63.fmt.vmops.com local0: 20
[jira] [Updated] (CLOUDSTACK-3492) [Regression]Update Resource Count for an account is updating the primary storage incorretly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-3492: Fix Version/s: 4.2.0 > [Regression]Update Resource Count for an account is updating the primary > storage incorretly > > > Key: CLOUDSTACK-3492 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3492 > 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: Sailaja Mada >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log, management-server.log > > > Steps: > 1. Deploy instance with user account1 > 2. Get the primary storage is usage using ListAccounts- It is 10 GB same as > ROOT disk size of this instance > 3. Now tried Update Resource Count for this account. With this when verified > the usage using listAccounts it increased to 11 GB > 4. Added one DATA disk of 5 GB . With which usage has become 16 GB > 5. Then tried Update Resource Count for this account. With this when > verified the usage using listAccounts it decreased to 11 GB > Observation : > Update Resource Count for an account is updating the primary storage > incorrectly (Attached API log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706809#comment-13706809
]
Koushik Das commented on CLOUDSTACK-3493:
-
In step 3 check if the volume is created using a disk offering that uses local
storage. If not then attch would fail.
> Attach volume to VM is failing in case of Primary-Localstorage .
>
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> 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: 4.2 stable build
>Reporter: manasaveloori
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-Xen.(System VMs not in local storage)
> 2.Deploy a VM with default template.
> 3.Create a Volume.
> 4.Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
> 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
> ===END=== 10.252.192.69 -- GET
> command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: CLUSTER and HOST
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Can't move volume between scope:
> CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3
[jira] [Commented] (CLOUDSTACK-310) Failed to add host - Plugin error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706812#comment-13706812 ] Abhinandan Prateek commented on CLOUDSTACK-310: --- Making the priority as Major. > Failed to add host - Plugin error > - > > Key: CLOUDSTACK-310 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-310 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Xen >Affects Versions: 4.1.0, 4.2.0 > Environment: Management server is running centos 6.2 > Host is running Xen 4.1 on ubuntu 12.04 LTS installed with xcp-xapi package > Followed the tutorial - > http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution_-_proposed >Reporter: Taavi Türnpuu > Fix For: 4.2.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > management-server.log > 2012-10-10 12:47:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:47:45,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:15,820 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2012-10-10 > 09:48:15 GMT > 2012-10-10 12:48:15,822 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null) > Found 0 running routers. > 2012-10-10 12:48:15,822 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Got 0 snapshots to be executed at 2012-10-10 09:48:15 > GMT > 2012-10-10 12:48:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:16,045 DEBUG > [cloud.network.ExternalLoadBalancerUsageManagerImpl] > (ExternalNetworkMonitor-1:null) External load balancer devices stats > collector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) VmStatsCollector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-3:null) HostStatsCollector is running... > 2012-10-10 12:48:32,855 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) StorageCollector is running... > 2012-10-10 12:48:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Running Capacity Checker ... > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) recalculating system capacity > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done recalculating system capacity > 2012-10-10 12:48:45,827 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:45,831 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done running Capacity Checker ... > 2012-10-10 12:49:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:49:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:49:32,416 DEBUG [cloud.server.StatsCollector] > (StatsCollec
[jira] [Resolved] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koushik Das resolved CLOUDSTACK-3493.
-
Resolution: Not A Problem
Try creating a disk with a local disk offering and it should work. If attch
fails even with a local disk offering then reopen.
> Attach volume to VM is failing in case of Primary-Localstorage .
>
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> 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: 4.2 stable build
>Reporter: manasaveloori
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-Xen.(System VMs not in local storage)
> 2.Deploy a VM with default template.
> 3.Create a Volume.
> 4.Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
> 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
> ===END=== 10.252.192.69 -- GET
> command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: CLUSTER and HOST
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Can't move volume between scope:
> CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-5
[jira] [Updated] (CLOUDSTACK-310) Failed to add host - Plugin error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-310: -- Priority: Major (was: Critical) > Failed to add host - Plugin error > - > > Key: CLOUDSTACK-310 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-310 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Xen >Affects Versions: 4.1.0, 4.2.0 > Environment: Management server is running centos 6.2 > Host is running Xen 4.1 on ubuntu 12.04 LTS installed with xcp-xapi package > Followed the tutorial - > http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution_-_proposed >Reporter: Taavi Türnpuu > Fix For: 4.2.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > management-server.log > 2012-10-10 12:47:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:47:45,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:15,820 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2012-10-10 > 09:48:15 GMT > 2012-10-10 12:48:15,822 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null) > Found 0 running routers. > 2012-10-10 12:48:15,822 DEBUG [storage.snapshot.SnapshotSchedulerImpl] > (SnapshotPollTask:null) Got 0 snapshots to be executed at 2012-10-10 09:48:15 > GMT > 2012-10-10 12:48:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:16,045 DEBUG > [cloud.network.ExternalLoadBalancerUsageManagerImpl] > (ExternalNetworkMonitor-1:null) External load balancer devices stats > collector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) VmStatsCollector is running... > 2012-10-10 12:48:32,413 DEBUG [cloud.server.StatsCollector] > (StatsCollector-3:null) HostStatsCollector is running... > 2012-10-10 12:48:32,855 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) StorageCollector is running... > 2012-10-10 12:48:44,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Running Capacity Checker ... > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) recalculating system capacity > 2012-10-10 12:48:45,788 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing cpu/ram capacity update > 2012-10-10 12:48:45,790 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing storage capacity update > 2012-10-10 12:48:45,791 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done capacity updates for public ip and Vlans > 2012-10-10 12:48:45,799 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done executing capacity updates for private ip > 2012-10-10 12:48:45,806 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done recalculating system capacity > 2012-10-10 12:48:45,827 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:48:45,831 DEBUG [cloud.alert.AlertManagerImpl] > (CapacityChecker:null) Done running Capacity Checker ... > 2012-10-10 12:49:14,767 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage > UPintenance mode > 2012-10-10 12:49:15,826 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 routers. > 2012-10-10 12:49:32,416 DEBUG [cloud.server.StatsCollector] > (StatsCollector-2:null) VmStatsCollector is running... > 2012-10-10 12:49:
[jira] [Closed] (CLOUDSTACK-3493) Attach volume to VM is failing in case of Primary-Localstorage .
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori closed CLOUDSTACK-3493.
-
Working fine with disk offering.Hence closing the issue.
> Attach volume to VM is failing in case of Primary-Localstorage .
>
>
> Key: CLOUDSTACK-3493
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3493
> 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: 4.2 stable build
>Reporter: manasaveloori
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-Xen.(System VMs not in local storage)
> 2.Deploy a VM with default template.
> 3.Create a Volume.
> 4.Attach the created volume to the VM.
> Observed the following exception :
> 2013-07-12 19:24:30,025 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-17:null) submit async job-96, details: AsyncJobVO {id:96,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId:
> 33, cmd: org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"2d279447-7d91-4b97-9c86-10f09d08771c","sessionkey":"NPIr/lm7+u0dB9XxfOmuCTTHu+8\u003d","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","virtualMachineId":"924eb3a7-321a-432d-8ba8-e7c8cfeee87f","httpmethod":"GET","_":"1373617816676","ctxAccountId":"2","ctxStartEventId":"389"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-12 19:24:30,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
> ===END=== 10.252.192.69 -- GET
> command=attachVolume&id=2d279447-7d91-4b97-9c86-10f09d08771c&virtualMachineId=924eb3a7-321a-432d-8ba8-e7c8cfeee87f&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617816676
> 2013-07-12 19:24:30,033 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-96
> 2013-07-12 19:24:30,153 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Can't move volume between
> scope: CLUSTER and HOST
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1586)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1839)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:513)
> 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-12 19:24:30,155 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-96) Complete async job-96, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Can't move volume between scope:
> CLUSTER and HOST
> 2013-07-12 19:24:33,092 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===START=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> 2013-07-12 19:24:33,097 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-37:null) Ping from 1
> 2013-07-12 19:24:33,118 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-13:null) Async job-96 completed
> 2013-07-12 19:24:33,129 DEBUG [cloud.api.ApiServlet] (catalina-exec-13:null)
> ===END=== 10.252.192.69 -- GET
> command=queryAsyncJobResult&jobId=81574554-3985-4738-9085-576c65391e44&response=json&sessionkey=NPIr%2Flm7%2Bu0dB9XxfOmuCTTHu%2B8%3D&_=1373617819883
> Attaching
[jira] [Assigned] (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:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-1809: -- Assignee: Nitin Mehta Can you comment what could be wrong and that it needs to be assigned to the VMWare specialist ? > 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: Nitin Mehta >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] [Updated] (CLOUDSTACK-1528) No UI level check for Overcommit ratio;It is accepting special character,negative values and zero
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-1528:
--
Component/s: API
> No UI level check for Overcommit ratio;It is accepting special
> character,negative values and zero
> -
>
> Key: CLOUDSTACK-1528
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1528
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, UI
>Affects Versions: 4.2.0
>Reporter: prashant kumar mishra
>Assignee: Bharat Kumar
> Fix For: 4.2.0
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg
>
>
> 1-There is no check in UI for special character and zero.
> 2-If we provide any special character or zero for overcommit ratio in UI ,DB
> is getting upgraded by default value 1.
> Steps
>
> 1-Create a cluster provide some special characters for overcommit ratio
> Expected
> -
> should have some error message , overcommite ratio cant't be special
> character or less than zero etc.
> Actual
>
> cluster is getting created with overcommit ratio ={special
> character,zero,-ive values} but DB is storing default value 1 .
> DB
> ---
> mysql> select* from cluster_details;
> +++---+---+
> | id | cluster_id | name | value |
> +++---+---+
> | 1 | 1 | cpuOvercommitRatio| 1.0 |
> | 2 | 1 | memoryOvercommitRatio | 1.0 |
> | 3 | 2 | cpuOvercommitRatio| 1.0 |
> | 4 | 2 | memoryOvercommitRatio | 1.0 |
> | 5 | 3 | cpuOvercommitRatio| 1.0 |
> | 6 | 3 | memoryOvercommitRatio | 1.0 |
> +++---+---+
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-906) [DOC] Document the firewall functionality of Cisco ASA 1000v within CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706816#comment-13706816 ] ASF subversion and git services commented on CLOUDSTACK-906: Commit 1b373accf4dca3ed7b12db90b556af59d8e12f8b in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1b373ac ] CLOUDSTACK-906 draft > [DOC] Document the firewall functionality of Cisco ASA 1000v within CloudStack > -- > > Key: CLOUDSTACK-906 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-906 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Radhika Nair > Fix For: 4.2.0 > > > Document the firewall functionality of Cisco ASA 1000v within CloudStack -- 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-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-2987: Status: Ready To Review (was: In Progress) > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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-3415) Guest os memory is not getting dynamically adjusted incase of overcommit
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-3415: -- Assignee: Bharat Kumar > Guest os memory is not getting dynamically adjusted incase of overcommit > > > Key: CLOUDSTACK-3415 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3415 > 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: master stable branch ;vmware esxi-5.1 >Reporter: prashant kumar mishra >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > Attachments: Logs_DB.rar > > > In case of contention existing vms memory should automatically get reduced > (should be between reserved and max) so that new vms can accommodate on > host.But i did not see this behavior on vmware. > Guest OS always shows max memory even in case of contention . > Steps to reproduce > --- > 1-Preapre a CS setup with vmware esxi5.1 > 1-Set memory overcommit to 2 > 3-Create a service offering of1 (cpu=500MGZ,Memory=4096MB) > 4-Deploy vms using service offering of1 till no memory left on hypervisor > 5-run cat /proc/meminfo on each guest > Actual > -- > 1-Step 5 shows each guest is having 4096MB > 2-Total guest os memory(at guest OS level) >what physically available on host > Expected > -- > 1-VMs memory should dynamically get adjusted (<4096) in order to accommodate > new vms on host > 2-Total guest os memory (at guest OS level) <=what physically available on > host -- 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-906) [DOC] Document the firewall functionality of Cisco ASA 1000v within CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706821#comment-13706821 ] ASF subversion and git services commented on CLOUDSTACK-906: Commit b948bbd552fe72b3eb191359e46ac65cddd321e8 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b948bbd ] CLOUDSTACK-906 > [DOC] Document the firewall functionality of Cisco ASA 1000v within CloudStack > -- > > Key: CLOUDSTACK-906 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-906 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Radhika Nair > Fix For: 4.2.0 > > > Document the firewall functionality of Cisco ASA 1000v within CloudStack -- 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-3368) download URLs of ISOs and templates become invalid after recreating SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-3368. Resolution: Fixed > download URLs of ISOs and templates become invalid after recreating SSVM > - > > Key: CLOUDSTACK-3368 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3368 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > > After destroy/create SSVM, the download URLs of ISOs and templates become > invalid, because > (1) the public ip of SSVM changes > (2) the path doesnot exist in SSVM even SSVM has the same public ip. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3494) listvmwareDcs API doesn't exist for admin
Srikanteswararao Talluri created CLOUDSTACK-3494: Summary: listvmwareDcs API doesn't exist for admin Key: CLOUDSTACK-3494 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3494 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Reporter: Srikanteswararao Talluri Fix For: 4.2.0 steps to reproduce: == >From UI, hover over quick view of zone. ===START=== 10.101.255.52 -- GET command=listVmwareDcs&response=json&sessionkey=GbrTR2rbSHy4w4cDQKLilYTtvpw%3D&zoneid=4c7bd40d-7d0e-468c-b3ab-34e803633c16&_=1373612606633 2013-07-12 17:58:41,445 DEBUG [cloud.api.ApiServer] (catalina-exec-24:null) The given command:listVmwareDcs does not exist or it is not available for user with id:2 2013-07-12 17:58:41,446 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) ===END=== 10.101.255.52 -- GET command=listVmwareDcs&response=json&sessionkey=GbrTR2rbSHy4w4cDQKLilYTtvpw%3D&zoneid=4c7bd40d-7d0e-468c-b3ab-34e803633c16&_=1373612606633 -- 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-3480) Correct the templates.sql to point to right systemvm templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706822#comment-13706822 ] Abhinandan Prateek commented on CLOUDSTACK-3480: The db template path is actually not used for seeding system VM templates. > Correct the templates.sql to point to right systemvm templates > -- > > Key: CLOUDSTACK-3480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3480 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > When using NFS as a secondary storage we are required to place systemVM > templates for the initial bootstrap of the service VMs (CPVM, SSVM). This is > not a mandatory step when using object storage as a backing image store. In > the > case of object store we download the templates as listed in the vm_template > table for the hypervisor we are dealing with. The source of the entires is in > the templates.sql file. Since systemVM templates have undergone changes from > 3.0.2 (from when the template entires exist in vm_template) it is best to > update these to the latest available locations for the systemVM templates. > One instance that will not work is the KVM clock sync that requires the newer > systemVM template to exist. -- 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-1475) RegisterISO error after Update SSL Certificate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou closed CLOUDSTACK-1475. Resolution: Fixed > RegisterISO error after Update SSL Certificate > -- > > Key: CLOUDSTACK-1475 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1475 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.1.1, 4.2.0 > > > After updating SSL Certificate, and restart cloud-management service. > whentry to registerISO from the url which is shown in "downloadISO", it will > fail with the error message "sun.security.validator.ValidatorException: PKIX > path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target". > Another problem is that, the url of DownloadISO always(!) be > **-**-**-**.realhostip.com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2940) Domain on SSVM is not being updated for download urls that come for CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706820#comment-13706820 ] ASF subversion and git services commented on CLOUDSTACK-2940: - Commit 5174b002bc3e2e0013a580e63bf3ac45c18e5e2a in branch refs/heads/4.1 from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5174b00 ] CLOUDSTACK-2940 Allowing Replacement of realhostip.com with a customized domain for SSVM. Though the config variable was there we were always hardcoding to realhostip.com Reviewed-by: Abhi > Domain on SSVM is not being updated for download urls that come for CS. > --- > > Key: CLOUDSTACK-2940 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2940 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3362) upload Custom SSL Certificate failed on UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhou closed CLOUDSTACK-3362.
Resolution: Fixed
> upload Custom SSL Certificate failed on UI
> --
>
> Key: CLOUDSTACK-3362
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3362
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> I tried to use my SSL certificate, but failed.
> (1) When I input both certificate and private key, it returned "Failed to
> update SSL Certificate" message, without any log in management-server.log
> I think it is because of the length of keys. So I removed some characters
> from private key.
> (2) After I removed some characters from private key, it returned another
> message "Received value -BEGIN CERTIFICATE- *-END
> CERTIFICATE- for parameter certificate is invalid, contains illegal ASCII
> non-printable characters"
> I think it is because the url was not encoded, so I added todb in
> ui/scripts/ui-custom/physicalResources.js
> diff --git a/ui/scripts/ui-custom/physicalResources.js
> b/ui/scripts/ui-custom/physicalResources.js
> index 529adcf..7dc40ea 100644
> --- a/ui/scripts/ui-custom/physicalResources.js
> +++ b/ui/scripts/ui-custom/physicalResources.js
> @@ -82,8 +82,8 @@
> $.ajax({
>url: createURL('uploadCustomCertificate'),
>data: {
> -certificate: args.data.certificate,
> -privatekey: args.data.privatekey,
> +certificate: todb(args.data.certificate),
> +privatekey: todb(args.data.privatekey),
> domainsuffix: args.data.domainsuffix
>},
>dataType: 'json',
> After that, CLOUDSTACK-3244 appeared.
> I tested on master branch, but I think 4.1.0 and 4.2 have the same issue.
--
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-1475) RegisterISO error after Update SSL Certificate
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706817#comment-13706817 ] ASF subversion and git services commented on CLOUDSTACK-1475: - Commit 3b5bcac81a14aa239e172f14f1819bd445063a6a in branch refs/heads/4.1 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b5bcac ] CLOUDSTACK-1475: fix RegisterISO error after Update SSL Certificate > RegisterISO error after Update SSL Certificate > -- > > Key: CLOUDSTACK-1475 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1475 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.1, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.1.1, 4.2.0 > > > After updating SSL Certificate, and restart cloud-management service. > whentry to registerISO from the url which is shown in "downloadISO", it will > fail with the error message "sun.security.validator.ValidatorException: PKIX > path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target". > Another problem is that, the url of DownloadISO always(!) be > **-**-**-**.realhostip.com -- 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-3368) download URLs of ISOs and templates become invalid after recreating SSVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706818#comment-13706818 ] ASF subversion and git services commented on CLOUDSTACK-3368: - Commit 2963f0479e81d6202630cbcb99379311790e4981 in branch refs/heads/4.1 from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2963f04 ] CLOUDSTACK-3368: clear download URLs when create SSVM and validate download URLs > download URLs of ISOs and templates become invalid after recreating SSVM > - > > Key: CLOUDSTACK-3368 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3368 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0, 4.2.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > > After destroy/create SSVM, the download URLs of ISOs and templates become > invalid, because > (1) the public ip of SSVM changes > (2) the path doesnot exist in SSVM even SSVM has the same public ip. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3362) upload Custom SSL Certificate failed on UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706819#comment-13706819
]
ASF subversion and git services commented on CLOUDSTACK-3362:
-
Commit 7b2f68e8cfaea5f313ff91da90a4ac62e5933afa in branch refs/heads/4.1 from
[~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7b2f68e ]
CLOUDSTACK-3362: use POST instead of GET and encode/decode cert/key in
uploadCustomCertificate
> upload Custom SSL Certificate failed on UI
> --
>
> Key: CLOUDSTACK-3362
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3362
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> I tried to use my SSL certificate, but failed.
> (1) When I input both certificate and private key, it returned "Failed to
> update SSL Certificate" message, without any log in management-server.log
> I think it is because of the length of keys. So I removed some characters
> from private key.
> (2) After I removed some characters from private key, it returned another
> message "Received value -BEGIN CERTIFICATE- *-END
> CERTIFICATE- for parameter certificate is invalid, contains illegal ASCII
> non-printable characters"
> I think it is because the url was not encoded, so I added todb in
> ui/scripts/ui-custom/physicalResources.js
> diff --git a/ui/scripts/ui-custom/physicalResources.js
> b/ui/scripts/ui-custom/physicalResources.js
> index 529adcf..7dc40ea 100644
> --- a/ui/scripts/ui-custom/physicalResources.js
> +++ b/ui/scripts/ui-custom/physicalResources.js
> @@ -82,8 +82,8 @@
> $.ajax({
>url: createURL('uploadCustomCertificate'),
>data: {
> -certificate: args.data.certificate,
> -privatekey: args.data.privatekey,
> +certificate: todb(args.data.certificate),
> +privatekey: todb(args.data.privatekey),
> domainsuffix: args.data.domainsuffix
>},
>dataType: 'json',
> After that, CLOUDSTACK-3244 appeared.
> I tested on master branch, but I think 4.1.0 and 4.2 have the same issue.
--
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-3480) Correct the templates.sql to point to right systemvm templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706822#comment-13706822 ] Abhinandan Prateek edited comment on CLOUDSTACK-3480 at 7/12/13 9:39 AM: - -- was (Author: aprateek): The db template path is actually not used for seeding system VM templates. > Correct the templates.sql to point to right systemvm templates > -- > > Key: CLOUDSTACK-3480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3480 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > When using NFS as a secondary storage we are required to place systemVM > templates for the initial bootstrap of the service VMs (CPVM, SSVM). This is > not a mandatory step when using object storage as a backing image store. In > the > case of object store we download the templates as listed in the vm_template > table for the hypervisor we are dealing with. The source of the entires is in > the templates.sql file. Since systemVM templates have undergone changes from > 3.0.2 (from when the template entires exist in vm_template) it is best to > update these to the latest available locations for the systemVM templates. > One instance that will not work is the KVM clock sync that requires the newer > systemVM template to exist. -- 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-3480) Correct the templates.sql to point to right systemvm templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706822#comment-13706822 ] Abhinandan Prateek edited comment on CLOUDSTACK-3480 at 7/12/13 9:39 AM: - Deleting the prev comment. was (Author: aprateek): -- > Correct the templates.sql to point to right systemvm templates > -- > > Key: CLOUDSTACK-3480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3480 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Priority: Critical > Fix For: 4.2.0 > > > When using NFS as a secondary storage we are required to place systemVM > templates for the initial bootstrap of the service VMs (CPVM, SSVM). This is > not a mandatory step when using object storage as a backing image store. In > the > case of object store we download the templates as listed in the vm_template > table for the hypervisor we are dealing with. The source of the entires is in > the templates.sql file. Since systemVM templates have undergone changes from > 3.0.2 (from when the template entires exist in vm_template) it is best to > update these to the latest available locations for the systemVM templates. > One instance that will not work is the KVM clock sync that requires the newer > systemVM template to exist. -- 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-3495) xenserver 6.1 and 6.2 can not open vnc console
Hongtu Zang created CLOUDSTACK-3495: --- Summary: xenserver 6.1 and 6.2 can not open vnc console Key: CLOUDSTACK-3495 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3495 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VNC Proxy, XenServer Affects Versions: 4.2.0 Environment: xenserver 6.1 or 6.2 Reporter: Hongtu Zang Fix For: 4.2.0 can not open vnc console in web UI, if hypervisor is xenserver 6.1 or 6.2 this is because of the path of the vnc-port file is the same with 6.0 but the vmops code is looking for the pid and port as xenserver 5.x -- 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-2875) VM password is not correct after deployment and resetpassword on KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou reopened CLOUDSTACK-2875: -- reopen it, as 8080 should be opened by /etc/init.d/cloud-passwd-srvr. Maybe something else are wrong. > VM password is not correct after deployment and resetpassword on KVM > > > Key: CLOUDSTACK-2875 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2875 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 > Environment: CentOS 6.4 >Reporter: Wei Zhou >Assignee: Wei Zhou > Labels: integration-test > > After fixed CLOUDSTACK-2823, the systemvms are running finally. > A new issue is that I can not log in the VM (Ubuntu 12.04 64bit) as the > password is not correct, even after reset password. The IP and hostname are > correct in VM. > systemvm from > http://jenkins.cloudstack.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-2013-06-04-master-kvm.qcow2.bz2 -- 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-2049) Dedicate Public IP addresses - Usage events
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty closed CLOUDSTACK-2049. -- > Dedicate Public IP addresses - Usage events > --- > > Key: CLOUDSTACK-2049 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2049 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Dedication by admin is equivalent to users acquiring IP. > Hence a user should be charged for a dedicated IP from the time it is > dedicated to the time it is released back to the system pool. -- 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-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706828#comment-13706828 ] ASF subversion and git services commented on CLOUDSTACK-2987: - Commit 5dd1a1dd8eec0a37db36b5c86d847fbbe4fcc41d in branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5dd1a1d ] CLOUDSTACK-2987: Fixing dynamicallyScalable flag in register and update template API Previuos commit: 7b6b8d7a077478620232ea1ac4ec2304289e8661 This fix is due to some changes made by the merges after this commit. Signed-off-by: Abhinandan Prateek > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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-3011) [Dedicated Resources] Global config to disallow an account from acquiring public ips and guest vlans from the system
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty closed CLOUDSTACK-3011. -- Confirmed global config has been added to disallow accounts from acquiring ips and vlans from system pool > [Dedicated Resources] Global config to disallow an account from acquiring > public ips and guest vlans from the system > > > Key: CLOUDSTACK-3011 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3011 > 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: Likitha Shetty >Assignee: Likitha Shetty > Labels: documentation > Fix For: 4.2.0 > > > Add 2 configs - use.system.public.ips and use.system.guest.vlans > The 2 global configs should allow root admin to disallow any account from > acquiring public ips and guest vlans from the system if the account has > dedicated resources and these dedicated resources have all been consumed. > Both configs should be configurable at the account level too. -- 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-3258) Fix AWSAPI to provide tags support for resource' security-groups'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty closed CLOUDSTACK-3258. -- > Fix AWSAPI to provide tags support for resource' security-groups' > - > > Key: CLOUDSTACK-3258 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3258 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0 >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Tags related EC2 APIs are failing with unsupported error. -- 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-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706832#comment-13706832 ] ASF subversion and git services commented on CLOUDSTACK-2987: - Commit 8816d41d3b62fe50bbeb70e541f54f8e232c362e in branch refs/heads/4.2 from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8816d41 ] CLOUDSTACK-2987: Fixing dynamicallyScalable flag in register and update template API Previuos commit: 7b6b8d7a077478620232ea1ac4ec2304289e8661 This fix is due to some changes made by the merges after this commit. Signed-off-by: Abhinandan Prateek > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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-2987) Ensure XStools to be there in template inorder to enable dynamic scaling of vm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-2987. - Resolution: Fixed > Ensure XStools to be there in template inorder to enable dynamic scaling of vm > -- > > Key: CLOUDSTACK-2987 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987 > 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 > > > XS tools need to be installed on the guest vm for Xenserver for memory > dynamic scaling and over provisioning to work. > XStools contain baloon drivers that are required to dynamically manipulate > the memory attributes (dynamic max/min). If they are altered at run time > without these tools, it can lead to unstable behavior for vm and potential > crash. Both for memory dynamic scaling and over provisioning this is > required. > So we need to be able to ensure whether xstools are installed on the template > based on the user inputs while registering the template and use the same to > set different memory/cpu values to make dynamic scaling work. -- 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-728) Add support for Nicira NVP to VmWare hypervisor orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706837#comment-13706837 ] ASF subversion and git services commented on CLOUDSTACK-728: Commit 392bbcc737ec8622d4101df783bc947266ff3dfe in branch refs/heads/master from [~htrippaers] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=392bbcc ] CLOUDSTACK-728 Rewrite support for lswitch connected nics on both standard and distributed switches. Fix the name of the interface id in extra config, so the nic is found up using the nic uuid instead of the vm id. getVlanInfo should return null when the nic is plugged on a Lswitch network. On a distributed portgroup all vms should be connected to a single portgroup and set a specific vlan on the port. On a standard switch each nic should have its own portgroup with a dedicated vlan (not related to CS vlans) > Add support for Nicira NVP to VmWare hypervisor orchestration > - > > Key: CLOUDSTACK-728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-728 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-728) Add support for Nicira NVP to VmWare hypervisor orchestration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706836#comment-13706836 ] ASF subversion and git services commented on CLOUDSTACK-728: Commit 2691970f280c0d997f294510a7244a625151f3da in branch refs/heads/master from [~htrippaers] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2691970 ] CLOUDSTACK-728 Get the framework in place the support the removal of the portgroup that is created for a nic connected to an lswitch. Add a command to tell a hypervisor guru to take some action when expunging a nic > Add support for Nicira NVP to VmWare hypervisor orchestration > - > > Key: CLOUDSTACK-728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-728 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3495) xenserver 6.1 and 6.2 can not open vnc console
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706838#comment-13706838 ] Hongtu Zang commented on CLOUDSTACK-3495: - fixed here https://reviews.apache.org/r/12500/ > xenserver 6.1 and 6.2 can not open vnc console > -- > > Key: CLOUDSTACK-3495 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3495 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy, XenServer >Affects Versions: 4.2.0 > Environment: xenserver 6.1 or 6.2 >Reporter: Hongtu Zang > Labels: console, vnc, xenserver > Fix For: 4.2.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > can not open vnc console in web UI, if hypervisor is xenserver 6.1 or 6.2 > this is because of the path of the vnc-port file is the same with 6.0 but the > vmops code is looking for the pid and port as xenserver 5.x -- 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-3094) [Add network]Adding a shared network to already deployed VM is failing.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava resolved CLOUDSTACK-3094.
Resolution: Fixed
> [Add network]Adding a shared network to already deployed VM is failing.
> ---
>
> Key: CLOUDSTACK-3094
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3094
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
>Reporter: manasaveloori
>Assignee: Saksham Srivastava
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip, management-server.zip,
> mysqldump1.dmp, mysqldump1.dmp
>
>
> Steps:
> 1.Have a CS with advanced zone.
> 2.Create a VPC and a tier network.
> 3.Create a VM using the tier network.
> 4.Create a shared network.
> 5.Go to the VPC VM ->NICs->Add network. Select the shared network from
> the dropdown and add the network.
> Observation:
> Adding the shared network is failing with unexpected exception.
> 013-06-20 22:37:18,984 DEBUG [network.guru.DirectNetworkGuru]
> (Job-Executor-16:job-184) remove nic 80 secondary ip
> 2013-06-20 22:37:19,000 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-16:job-184) Removed nic id=80
> 2013-06-20 22:37:19,002 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-16:job-184) Revoving nic secondary ip entry ...
> 2013-06-20 22:37:19,003 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-16:job-184) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to add NIC to
> VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:916)
> at
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109)
> 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-20 22:37:19,004 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-16:job-184) Complete async job-184, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Unable to add NIC to
> VM[User|979cbfa9-5e02-4f35-8ac9-fe8c25dac2ae]
> 2013-06-20 22:37:20,113 INFO [vmware.resource.VmwareResource]
> (DirectAgent-125:10.147.40.29) vm_data command on domain router 10.147.40.181
> completed
> 2013-06-20 22:37:20,115 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-125:null) Seq 1-563282274: Response Received:
> 2013-06-20 22:37:20,116 DEBUG [agent.transport.Request]
> (DirectAgent-125:null) Seq 1-563282274: Processing: { Ans: , MgmtId:
> 6805241462820, via: 1, Ver: v1, Flags: 110,
> [{"Answer":{"result":true,"wait":0}}] }
> UI is listing all the nics even though adding a nic is failing.(Ifconfig –a
> in the VM not showing the added shared network)
> We are able to add multiple shared networks while deploying the VM(instance
> creation), but same is not happening through “ Add network option”
> Attaching the MS logs and DB logs.
--
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-3496) Primary Storage resource usage is not getting updated if detached volume is deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3496: - Fix Version/s: 4.2.0 > Primary Storage resource usage is not getting updated if detached volume is > deleted > - > > Key: CLOUDSTACK-3496 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496 > 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: Sailaja Mada >Priority: Critical > Fix For: 4.2.0 > > > Setup : Advanced Zone with Xen 6.2 > Steps: > 1. Create user account and deploy VM - It has ROOT disk of 20 GB . Now > primary storage resource usage is 20 GB > > 2. Add a DATA volume with small offering (5GB) , Now primary storage > resource usage is 25 GB > 3. Attach this volume to the instance. > 4. Detach the volume > 5. Delete the volume which is deleted . There is no change in primary storage > resource usage even after deleting the volume of 5 GB. It is still 25 GB. > Observation: > Primary Storage resource usage is not getting updated if detached volume is > deleted -- 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-3496) Primary Storage resource usage is not getting updated if detached volume is deleted
Sailaja Mada created CLOUDSTACK-3496: Summary: Primary Storage resource usage is not getting updated if detached volume is deleted Key: CLOUDSTACK-3496 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496 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: Sailaja Mada Priority: Critical Setup : Advanced Zone with Xen 6.2 Steps: 1. Create user account and deploy VM - It has ROOT disk of 20 GB . Now primary storage resource usage is 20 GB 2. Add a DATA volume with small offering (5GB) , Now primary storage resource usage is 25 GB 3. Attach this volume to the instance. 4. Detach the volume 5. Delete the volume which is deleted . There is no change in primary storage resource usage even after deleting the volume of 5 GB. It is still 25 GB. Observation: Primary Storage resource usage is not getting updated if detached volume is deleted -- 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-3496) Primary Storage resource usage is not getting updated if detached volume is deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3496: - Attachment: apilog.log > Primary Storage resource usage is not getting updated if detached volume is > deleted > - > > Key: CLOUDSTACK-3496 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496 > 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: Sailaja Mada >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log > > > Setup : Advanced Zone with Xen 6.2 > Steps: > 1. Create user account and deploy VM - It has ROOT disk of 20 GB . Now > primary storage resource usage is 20 GB > > 2. Add a DATA volume with small offering (5GB) , Now primary storage > resource usage is 25 GB > 3. Attach this volume to the instance. > 4. Detach the volume > 5. Delete the volume which is deleted . There is no change in primary storage > resource usage even after deleting the volume of 5 GB. It is still 25 GB. > Observation: > Primary Storage resource usage is not getting updated if detached volume is > deleted -- 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-3494) listvmwareDcs API doesn't exist for admin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-3494: - Assignee: Sateesh Chodapuneedi > listvmwareDcs API doesn't exist for admin > - > > Key: CLOUDSTACK-3494 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3494 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.2.0 >Reporter: Srikanteswararao Talluri >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > steps to reproduce: > == > From UI, hover over quick view of zone. > ===START=== 10.101.255.52 -- GET > command=listVmwareDcs&response=json&sessionkey=GbrTR2rbSHy4w4cDQKLilYTtvpw%3D&zoneid=4c7bd40d-7d0e-468c-b3ab-34e803633c16&_=1373612606633 > 2013-07-12 17:58:41,445 DEBUG [cloud.api.ApiServer] (catalina-exec-24:null) > The given command:listVmwareDcs does not exist or it is not available for > user with id:2 > 2013-07-12 17:58:41,446 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.101.255.52 -- GET > command=listVmwareDcs&response=json&sessionkey=GbrTR2rbSHy4w4cDQKLilYTtvpw%3D&zoneid=4c7bd40d-7d0e-468c-b3ab-34e803633c16&_=1373612606633 -- 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-3496) Primary Storage resource usage is not getting updated if detached volume is deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reassigned CLOUDSTACK-3496: --- Assignee: Sanjay Tripathi > Primary Storage resource usage is not getting updated if detached volume is > deleted > - > > Key: CLOUDSTACK-3496 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496 > 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: Sailaja Mada >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log > > > Setup : Advanced Zone with Xen 6.2 > Steps: > 1. Create user account and deploy VM - It has ROOT disk of 20 GB . Now > primary storage resource usage is 20 GB > > 2. Add a DATA volume with small offering (5GB) , Now primary storage > resource usage is 25 GB > 3. Attach this volume to the instance. > 4. Detach the volume > 5. Delete the volume which is deleted . There is no change in primary storage > resource usage even after deleting the volume of 5 GB. It is still 25 GB. > Observation: > Primary Storage resource usage is not getting updated if detached volume is > deleted -- 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-3497) The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2
Paul Angus created CLOUDSTACK-3497: -- Summary: The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2 Key: CLOUDSTACK-3497 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3497 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller, Management Server, XenServer Affects Versions: 4.2.0 Environment: xenserver 6.2, CloudStack 4.2 Reporter: Paul Angus Fix For: 4.2.0 The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2 Specifically: A request a request to find Storage Pools suitable for live migration results in the following messages logged DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 10.0.0.33 -- GET command=findStoragePoolsForMigration&id=fa1dc489-0414-4f91-9637-9fb05462f0e7&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373621024636 ERROR [cloud.server.ManagementServerImpl] (catalina-exec-22:null) Capabilities for host Host[-6-Routing] couldn't be retrieved. -- 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-3497) The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3497: - Assignee: Devdeep Singh > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > --- > > Key: CLOUDSTACK-3497 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3497 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.2.0 > Environment: xenserver 6.2, CloudStack 4.2 >Reporter: Paul Angus >Assignee: Devdeep Singh > Labels: hypervisor, xenserver > Fix For: 4.2.0 > > > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > Specifically: > A request a request to find Storage Pools suitable for live migration results > in the following messages logged > DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=fa1dc489-0414-4f91-9637-9fb05462f0e7&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373621024636 > ERROR [cloud.server.ManagementServerImpl] (catalina-exec-22:null) > Capabilities for host Host[-6-Routing] couldn't be retrieved. -- 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-2988) UI: checkbox to know whether tools installed on the template during register template
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala resolved CLOUDSTACK-2988. - Resolution: Fixed > UI: checkbox to know whether tools installed on the template during register > template > - > > Key: CLOUDSTACK-2988 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2988 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > > During template registration/updation there should be a check box to know > whether tools are installed on the template or not. > Same check box should be there for updateVirtualMachine API. > -- 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-2757) Category not persisted when added config items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-2757: --- Status: Ready To Review (was: In Progress) > Category not persisted when added config items > -- > > Key: CLOUDSTACK-2757 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Category is persisted when adding config items in > ConfigurationDaoImpl.getValueAndInitIfNotExist. > It is always set to "Advanced". > This can cause encryption failures. > It'll be good to cleanup the SQL and use VO/DAO instead -- 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-2630) Object_Store_Refactor - Snapshots - There is no delta snapshots being created for subsequent snapshots when multiple snapshots are taken for root /data volumes.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706859#comment-13706859
]
Abhinav Roy commented on CLOUDSTACK-2630:
-
The issue is being seen even now with the latest 4.2 build
> Object_Store_Refactor - Snapshots - There is no delta snapshots being created
> for subsequent snapshots when multiple snapshots are taken for root /data
> volumes.
> -
>
> Key: CLOUDSTACK-2630
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2630
> 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: Blocker
> Fix For: 4.2.0
>
>
> Object_Store_Refactor - Snapshots - There is no delta syncs being created for
> subsequent snapshots when multiple snapshots are taken for root /data volumes
> Steps to reproduce the problem:
> Deploy a Vm with root and data disk.
> Take 1 snapshot of root volume.
> Do some changes to the root volume like create files.
> Take another snapshot of root volume.
> Notice that the 2nd snapshot taken is not a delta snapshot.
> [root@nfs2 3]# ls -ltr
> total 2607572
> -rw-r--r-- 1 root root 1863848448 May 22 15:28
> aecfd50d-c5f7-4270-96af-ccef8d040854.vhd
> -rw-r--r-- 1 root root 1865949696 May 22 15:33
> d9d89b01-a82c-41b0-a440-3bb807beac6e.vhd
> [root@nfs2 3]#
> Take 1 snapshot of data volume.
> Do some changes to the data volume like create files.
> Take another snapshot of data volume.
> Notice that the 2nd snapshot taken is not a delta snapshot.
> [root@nfs2 8]# ls -ltr
> total 13052
> -rw-r--r-- 1 root root 153403904 May 22 13:53
> 15f1706f-7a2a-45ba-96bc-d0dc520909f3.vhd
> -rw-r--r-- 1 root root 153403904 May 22 13:54
> 9047547a-a131-431a-b3f0-de1a3acb5117.vhd
> -rw-r--r-- 1 root root 153403904 May 22 15:47
> 6077e984-f7e3-4981-919d-25b0381fb563.vhd
> management server logs:
> 2013-05-22 14:46:17,881 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-21:null) submit async job-30, details: AsyncJobVO {id:30,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Snapshot,
> instanceId: 7, cmd:
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd,
> cmdOriginator: null, cmdInfo:
> {"id":"7","response":"json","sessionkey":"5LuVTJbq8L9whPX/rBchZgFpeGs\u003d","ctxUserId":"2","httpmethod":"GET","_":"1369262605452","volumeid":"127eb892-e435-4a13-a29a-5b9d3185face","ctxAccountId":"2","ctxStartEventId":"95"},
> 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-22 14:46:17,883 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-7:job-30) Executing
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-30
> 2013-05-22 14:46:17,915 INFO [user.snapshot.CreateSnapshotCmd]
> (Job-Executor-7:job-30) VOLSS: createSnapshotCmd starts:1369259177915
> 2013-05-22 14:46:17,976 DEBUG [agent.transport.Request]
> (Job-Executor-7:job-30) Seq 1-375915079: Sending { Cmd , MgmtId:
> 206915885079359, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"volume":{"uuid":"127eb892-e435-4a13-a29a-5b9d3185face","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"dbf7203e-d359-3179-a464-9900e126cdb0","id":3,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campo-systemp-1/primary2","port":2049}},"name":"DATA-8","size":5368709120,"path":"4cfaf81f-e11b-42ae-a290-65e2e36fb099","volumeId":8,"vmName":"i-2-8-VM","accountId":2,"id":8},"dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"dbf7203e-d359-3179-a464-9900e126cdb0","id":3,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/campo-systemp-1/primary2","port":2049}},"vmName":"i-2-8-VM","name":"data-123_DATA-8_20130522214617","hypervisorType":"XenServer","id":7}},"wait":0}}]
> }
> 2013-05-22 14:46:17,976 DEBUG [agent.transport.Request]
> (Job-Executor-7:job-30) Seq 1-375915079: Executing: { Cmd , MgmtId:
> 206915885079359, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"volume":{"uuid":"127eb892-e435-4a13-a29a-5b9d3185
[jira] [Assigned] (CLOUDSTACK-3188) Not able to add network to a VM after installing the Vmtools on a windows VM.(regression)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saksham Srivastava reassigned CLOUDSTACK-3188:
--
Assignee: Saksham Srivastava
> Not able to add network to a VM after installing the Vmtools on a windows
> VM.(regression)
> -
>
> Key: CLOUDSTACK-3188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3188
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Assignee: Saksham Srivastava
>Priority: Critical
> Fix For: 4.2.0
>
>
> Steps followed are as below:
> 1)Installed a VMware Advanced Zone setup.
> 2)once the system VM's are up added a Windows template.
> 3)Created a Vm using the windows864 bit template.
> 4)Once the VM came up tried to add a network to the VM then the below error
> message is observed which says the VM tools is not installed
> "2013-06-25 15:29:36,780 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-151) Seq 5-1148784739: Executing: { Cmd , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 100111,
> [{"PlugNicCommand":{"nic":{"deviceId":1,"networkRateMbps":200,"defaultNic":false,"uuid":"91a77dc9-9958-4e5d-8992-8e5a50e9e6db","ip":"10.1.4.218","netmask":"255.255.255.0","gateway":"10.1.4.1","mac":"02:00:3e:fb:00:09","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1057","isolationUri":"vlan://1057","isSecurityGroupEnabled":false},"instanceName":"i-8-51-VM","vmType":"User","wait":0}}]
> }
> 2013-06-25 15:29:36,781 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: Executing request
> 2013-06-25 15:29:36,782 INFO [vmware.resource.VmwareResource]
> (DirectAgent-250:10.147.40.24) Executing resource PlugNicCommand
> {"nic":{"deviceId":1,"networkRateMbps":200,"defaultNic":false,"uuid":"91a77dc9-9958-4e5d-8992-8e5a50e9e6db","ip":"10.1.4.218","netmask":"255.255.255.0","gateway":"10.1.4.1","mac":"02:00:3e:fb:00:09","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1057","isolationUri":"vlan://1057","isSecurityGroupEnabled":false},"instanceName":"i-8-51-VM","vmType":"User","wait":0}
> 2013-06-25 15:29:36,783 DEBUG [vmware.mo.HostMO]
> (DirectAgent-250:10.147.40.24) find VM i-8-51-VM on host
> 2013-06-25 15:29:36,783 DEBUG [vmware.mo.HostMO]
> (DirectAgent-250:10.147.40.24) load VM cache on host
> 2013-06-25 15:29:36,802 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-250:10.147.40.24) vmware tools is not installed or not running,
> cannot add nic to vm i-8-51-VM
> 2013-06-25 15:29:36,803 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: Response Received:
> 2013-06-25 15:29:36,803 DEBUG [agent.transport.Request]
> (DirectAgent-250:null) Seq 5-1148784739: Processing: { Ans: , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 110,
> [{"PlugNicAnswer":{"result":false,"details":"Unable to execute PlugNicCommand
> due to vmware tools is not installed or not running, cannot add nic to vm
> i-8-51-VM","wait":0}}] }
> 2013-06-25 15:29:36,804 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-151) Seq 5-1148784739: Received: { Ans: , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 110, { PlugNicAnswer } }
> 2013-06-25 15:29:36,804 WARN [cloud.vm.UserVmManagerImpl]
> (Job-Executor-18:job-151) Unable to plug nic for VM[User|win864vmw] due to:
> due to: Unable to execute PlugNicCommand due to vmware tools is not installed
> or not running, cannot add nic to vm i-8-51-VM
> 2013-06-25 15:29:36,808 WARN [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-18:job-151) Failed to plug nic to the vm VM[User|win864vmw] in
> network Ntwk[226|Guest|8]
> 2013-06-25 15:29:36,806 DEBUG [agent.manager.AgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: No more commands found
> 2013-06-25 15:29:36,830 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-18:job-151) Service SecurityGroup is not supported in the
> network id=226
> 2013-06-25 15:29:36,854 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-18:job-151) Removed nic id=126
> 2013-06-25 15:29:36,857 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-18:job-151) Revoving nic secondary ip entry ...
> 2013-06-25 15:29:36,858 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-18:job-151) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to add NIC to
> VM[User|win864vmw]
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:899)
>
[jira] [Updated] (CLOUDSTACK-3496) [Regression]Primary Storage resource usage is not getting updated if detached volume is deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3496: - Summary: [Regression]Primary Storage resource usage is not getting updated if detached volume is deleted(was: Primary Storage resource usage is not getting updated if detached volume is deleted ) > [Regression]Primary Storage resource usage is not getting updated if detached > volume is deleted > - > > Key: CLOUDSTACK-3496 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3496 > 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: Sailaja Mada >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > Attachments: apilog.log > > > Setup : Advanced Zone with Xen 6.2 > Steps: > 1. Create user account and deploy VM - It has ROOT disk of 20 GB . Now > primary storage resource usage is 20 GB > > 2. Add a DATA volume with small offering (5GB) , Now primary storage > resource usage is 25 GB > 3. Attach this volume to the instance. > 4. Detach the volume > 5. Delete the volume which is deleted . There is no change in primary storage > resource usage even after deleting the volume of 5 GB. It is still 25 GB. > Observation: > Primary Storage resource usage is not getting updated if detached volume is > deleted -- 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-3499) AttachVolume is mandating Xen PV drivers to be installed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3499:
-
Fix Version/s: 4.2.0
> AttachVolume is mandating Xen PV drivers to be installed
> -
>
> Key: CLOUDSTACK-3499
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3499
> 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: Sailaja Mada
>Priority: Critical
> Fix For: 4.2.0
>
>
> Setup: XenServer 6.2 , ACS 4.2
> Steps :
> 1. Create user account and deploy VM with template which does not have PV
> drivers installed
> 2. Create new DATA volume using small disk offering.
> 3. Tried to attach volume to the instance.
> Observation:
> AttachVolume is mandating Xen PV drivers to be installed
> Note :
> 1. Attach volume is working if instance is deployed with PV drivers installed
> template (Default Cent OS)
> 2. PV drivers were mandatory only for migration in the previous releases.
> Now it is mandating for attach volume also.
> 2013-07-12 14:07:44,657 DEBUG
> [datastore.driver.CloudStackPrimaryDataStoreDriverImpl]
> (Job-Executor-14:job-56) Creating volume:
> org.apache.cloudstack.storage.volume.VolumeObject@26c3dc39
> 2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Sending { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
> }
> 2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Executing: { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
> }
> 2013-07-12 14:07:44,662 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-393:null) Seq 1-1058341678: Executing request
> 2013-07-12 14:07:44,748 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-393:null) SR retrieved for ae321c7e-120b-38d9-b732-20b2ea8c58b4
> 2013-07-12 14:07:44,753 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-393:null) Checking ae321c7e-120b-38d9-b732-20b2ea8c58b4 or SR
> f7b947d6-0e8c-3bab-0b78-d8dbce0938fa on
> XS[5b53e784-364d-4f85-bec6-f83be13334e8-10.102.192.17]
> 2013-07-12 14:07:45,177 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-07-12 14:07:45,444 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-07-12 14:07:45,694 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-393:null) Seq 1-1058341678: Response Received:
> 2013-07-12 14:07:45,695 DEBUG [agent.transport.Request]
> (DirectAgent-393:null) Seq 1-1058341678: Processing: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CreateObjectAnswer":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"name":"vol1","size":5368709120,"path":"ddec79d5-6926-4753-ac4d-5e6b8f7906a3","accountId":0,"id":0}},"result":true,"wait":0}}]
> }
> 2013-07-12 14:07:45,695 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Received: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
> 2013-07-12 14:07:45,729 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341679: Sending { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStor
[jira] [Commented] (CLOUDSTACK-2757) Category not persisted when added config items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706867#comment-13706867 ] ASF subversion and git services commented on CLOUDSTACK-2757: - Commit 87df51356b8d3a00c1c7a8def753de052a471b3e in branch refs/heads/4.2 from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=87df513 ] CLOUDSTACK-2757. When configs are added the value of the property 'category' is not persisted. > Category not persisted when added config items > -- > > Key: CLOUDSTACK-2757 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Category is persisted when adding config items in > ConfigurationDaoImpl.getValueAndInitIfNotExist. > It is always set to "Advanced". > This can cause encryption failures. > It'll be good to cleanup the SQL and use VO/DAO instead -- 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-3498) [Object_Store_Refactor] Deleting and adding back the zone does not create NFS Cache store and Failure in Sytem VMs Start Up
Sanjeev N created CLOUDSTACK-3498: - Summary: [Object_Store_Refactor] Deleting and adding back the zone does not create NFS Cache store and Failure in Sytem VMs Start Up Key: CLOUDSTACK-3498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3498 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 ACS 4.2 branch. Reporter: Sanjeev N Priority: Critical Fix For: 4.2.0 Deleting a zone does not delete the NFS Cache store in that zone and adding another zone with same NFS cache store details those were given in the deleted zone does not create another NFS Cache store in the new zone. Hence the Failure in System vms bring up. Steps to Reproduce: 1.Bring up CS with advanced zone say zone1. 2.Add secondary storage with S3 provider and with NFS Cache Store 3.Delete secondary storage 4.Delete zone1 5.Add another zone say zone2 6.Add secondary storage with s3 provider and NFS Cache storage in Zone2 with NFS Server and Path same as zone1 Observations: === 1.Deleting zone did not delete NFS Cache store from image_store table. 2.Adding NFS Cache store with same details in new zone did not create another entry in image_store table for the new zone. Impact: == CS downloads Routing template from S3 to NFS Cache store to bring up the System VMs. Since CS did not find NFS Cache store in the new zone to copy the routing template spinning system vms failed with following exception: 2013-07-12 06:28:14,731 DEBUG [storage.motion.AncientDataMotionStrategy] (consoleproxy-1:null) needCacheStorage true, dest at null dest role Primarytemplate/tmpl/1/3/routing-3/systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2 src role Image 2013-07-12 06:28:14,737 DEBUG [network.guru.PublicNetworkGuru] (secstorage-1:null) public network deallocate network: networkId: 210, ip: 10.147.48.3 2013-07-12 06:28:14,739 DEBUG [cache.allocator.StorageCacheRandomAllocator] (consoleproxy-1:null) Can't find cache storage in zone: 3 2013-07-12 06:28:14,739 DEBUG [storage.motion.AncientDataMotionStrategy] (consoleproxy-1:null) copy object failed: com.cloud.utils.exception.CloudRuntimeException: No cache DataStore in scope id 3 type ZONE 2013-07-12 06:28:14,739 DEBUG [storage.motion.AncientDataMotionStrategy] (consoleproxy-1:null) copy failed com.cloud.utils.exception.CloudRuntimeException: com.cloud.utils.exception.CloudRuntimeException: No cache DataStore in scope id 3 type ZONE at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyObject(AncientDataMotionStrategy.java:204) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:351) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:390) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:490) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2485) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2542) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:927) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1664) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$Scheduled
[jira] [Created] (CLOUDSTACK-3499) AttachVolume is mandating Xen PV drivers to be installed
Sailaja Mada created CLOUDSTACK-3499:
Summary: AttachVolume is mandating Xen PV drivers to be installed
Key: CLOUDSTACK-3499
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3499
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: Sailaja Mada
Priority: Critical
Setup: XenServer 6.2 , ACS 4.2
Steps :
1. Create user account and deploy VM with template which does not have PV
drivers installed
2. Create new DATA volume using small disk offering.
3. Tried to attach volume to the instance.
Observation:
AttachVolume is mandating Xen PV drivers to be installed
Note :
1. Attach volume is working if instance is deployed with PV drivers installed
template (Default Cent OS)
2. PV drivers were mandatory only for migration in the previous releases. Now
it is mandating for attach volume also.
2013-07-12 14:07:44,657 DEBUG
[datastore.driver.CloudStackPrimaryDataStoreDriverImpl]
(Job-Executor-14:job-56) Creating volume:
org.apache.cloudstack.storage.volume.VolumeObject@26c3dc39
2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
(Job-Executor-14:job-56) Seq 1-1058341678: Sending { Cmd , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
}
2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
(Job-Executor-14:job-56) Seq 1-1058341678: Executing: { Cmd , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
}
2013-07-12 14:07:44,662 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-393:null) Seq 1-1058341678: Executing request
2013-07-12 14:07:44,748 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-393:null) SR retrieved for ae321c7e-120b-38d9-b732-20b2ea8c58b4
2013-07-12 14:07:44,753 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-393:null) Checking ae321c7e-120b-38d9-b732-20b2ea8c58b4 or SR
f7b947d6-0e8c-3bab-0b78-d8dbce0938fa on
XS[5b53e784-364d-4f85-bec6-f83be13334e8-10.102.192.17]
2013-07-12 14:07:45,177 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-07-12 14:07:45,444 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-07-12 14:07:45,694 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-393:null) Seq 1-1058341678: Response Received:
2013-07-12 14:07:45,695 DEBUG [agent.transport.Request] (DirectAgent-393:null)
Seq 1-1058341678: Processing: { Ans: , MgmtId: 280320865129348, via: 1, Ver:
v1, Flags: 10,
[{"org.apache.cloudstack.storage.command.CreateObjectAnswer":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"name":"vol1","size":5368709120,"path":"ddec79d5-6926-4753-ac4d-5e6b8f7906a3","accountId":0,"id":0}},"result":true,"wait":0}}]
}
2013-07-12 14:07:45,695 DEBUG [agent.transport.Request]
(Job-Executor-14:job-56) Seq 1-1058341678: Received: { Ans: , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
2013-07-12 14:07:45,729 DEBUG [agent.transport.Request]
(Job-Executor-14:job-56) Seq 1-1058341679: Sending { Cmd , MgmtId:
280320865129348, via: 1, Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"path":"ddec79d5-6926-4753-ac4d-5e6b8f7906a3","volumeId":17,"accountId":3,"format":"VHD","id":17}},"diskSeq":1,"type":"DATADISK"},"
[jira] [Closed] (CLOUDSTACK-1786) While reserving IPs in guest network, if guestvmcidr is a subset of network cidr but not a subset of cidr, exception is thrown.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava closed CLOUDSTACK-1786. -- > While reserving IPs in guest network, if guestvmcidr is a subset of network > cidr but not a subset of cidr, exception is thrown. > --- > > Key: CLOUDSTACK-1786 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1786 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 >Reporter: Saksham Srivastava >Assignee: Saksham Srivastava > Fix For: 4.2.0 > > > The following scenario: > networkcidr: 10.1.1.0/24 > cidr: 10.1.1.224/27 > Applying reservation with guestvmcidr: 10.1.1.0/26 results in exception: > Invalid value of Guest VM CIDR. For IP Reservation, Guest VM CIDR should be > a subset of network CIDR: 10.1.1.224/27 > Expected behavior: > Reservation should happen and new cidr should be 10.1.1.0/26 -- 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-2757) Category not persisted when added config items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706869#comment-13706869 ] ASF subversion and git services commented on CLOUDSTACK-2757: - Commit aaaf168f5a38294ef098bdf9c60657711f6655bf in branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aaaf168 ] CLOUDSTACK-2757. When configs are added the value of the property 'category' is not persisted. > Category not persisted when added config items > -- > > Key: CLOUDSTACK-2757 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Category is persisted when adding config items in > ConfigurationDaoImpl.getValueAndInitIfNotExist. > It is always set to "Advanced". > This can cause encryption failures. > It'll be good to cleanup the SQL and use VO/DAO instead -- 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-2277) Add approriate message for the user informing about the absence of vm-tools when adding nics to vm on vmware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava closed CLOUDSTACK-2277. -- Closing issue as now network cannot be added/removed if vm-tools are not installed. > Add approriate message for the user informing about the absence of vm-tools > when adding nics to vm on vmware > > > Key: CLOUDSTACK-2277 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2277 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, VMware >Affects Versions: 4.2.0 >Reporter: Saksham Srivastava >Assignee: Saksham Srivastava > Fix For: 4.2.0 > > > When adding NICs to guest vm on vmware through addNicToVirtualMachine, vm > tools must be installed on guestVms to allow hot nic plugin. > This information should be made available to the user in logs. -- 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-2757) Category not persisted when added config items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706871#comment-13706871 ] ASF subversion and git services commented on CLOUDSTACK-2757: - Commit 6e160d33361e2664f261fdc17d63e947b56105fe in branch refs/heads/master-6-17-stable from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6e160d3 ] CLOUDSTACK-2757. When configs are added the value of the property 'category' is not persisted. > Category not persisted when added config items > -- > > Key: CLOUDSTACK-2757 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Category is persisted when adding config items in > ConfigurationDaoImpl.getValueAndInitIfNotExist. > It is always set to "Advanced". > This can cause encryption failures. > It'll be good to cleanup the SQL and use VO/DAO instead -- 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-3499) AttachVolume is mandating Xen PV drivers to be installed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3499:
-
Attachment: apilog.log
> AttachVolume is mandating Xen PV drivers to be installed
> -
>
> Key: CLOUDSTACK-3499
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3499
> 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: Sailaja Mada
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log
>
>
> Setup: XenServer 6.2 , ACS 4.2
> Steps :
> 1. Create user account and deploy VM with template which does not have PV
> drivers installed
> 2. Create new DATA volume using small disk offering.
> 3. Tried to attach volume to the instance.
> Observation:
> AttachVolume is mandating Xen PV drivers to be installed
> Note :
> 1. Attach volume is working if instance is deployed with PV drivers installed
> template (Default Cent OS)
> 2. PV drivers were mandatory only for migration in the previous releases.
> Now it is mandating for attach volume also.
> 2013-07-12 14:07:44,657 DEBUG
> [datastore.driver.CloudStackPrimaryDataStoreDriverImpl]
> (Job-Executor-14:job-56) Creating volume:
> org.apache.cloudstack.storage.volume.VolumeObject@26c3dc39
> 2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Sending { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
> }
> 2013-07-12 14:07:44,662 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Executing: { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"ae321c7e-120b-38d9-b732-20b2ea8c58b4","id":4,"poolType":"IscsiLUN","host":"10.102.192.101","path":"/iqn.2004-04.com.qnap:ts-659proii:iscsi.lun2.cf5b54/0","port":3260}},"name":"vol1","size":5368709120,"volumeId":17,"accountId":3,"id":17}},"wait":0}}]
> }
> 2013-07-12 14:07:44,662 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-393:null) Seq 1-1058341678: Executing request
> 2013-07-12 14:07:44,748 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-393:null) SR retrieved for ae321c7e-120b-38d9-b732-20b2ea8c58b4
> 2013-07-12 14:07:44,753 DEBUG [xen.resource.CitrixResourceBase]
> (DirectAgent-393:null) Checking ae321c7e-120b-38d9-b732-20b2ea8c58b4 or SR
> f7b947d6-0e8c-3bab-0b78-d8dbce0938fa on
> XS[5b53e784-364d-4f85-bec6-f83be13334e8-10.102.192.17]
> 2013-07-12 14:07:45,177 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-07-12 14:07:45,444 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy
> 2013-07-12 14:07:45,694 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-393:null) Seq 1-1058341678: Response Received:
> 2013-07-12 14:07:45,695 DEBUG [agent.transport.Request]
> (DirectAgent-393:null) Seq 1-1058341678: Processing: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CreateObjectAnswer":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"name":"vol1","size":5368709120,"path":"ddec79d5-6926-4753-ac4d-5e6b8f7906a3","accountId":0,"id":0}},"result":true,"wait":0}}]
> }
> 2013-07-12 14:07:45,695 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341678: Received: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
> 2013-07-12 14:07:45,729 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-56) Seq 1-1058341679: Sending { Cmd , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"78e945fb-0255-42a4-a0da-609d67b726f0","volumeType":"DATADISK","dataStore":{"org.apache
