[jira] [Created] (CLOUDSTACK-8735) Browser Based Volume and Template Test Automation
Sailaja Mada created CLOUDSTACK-8735: Summary: Browser Based Volume and Template Test Automation Key: CLOUDSTACK-8735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8735 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Reporter: Sailaja Mada Assignee: Sailaja Mada Browser Based Volume and Template Test Automation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7422) [Automation] Attach volume test case failing with error Invalid configuration for device '0'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-7422:
-
Assignee: (was: Sailaja Mada)
[Automation] Attach volume test case failing with error Invalid
configuration for device '0'
--
Key: CLOUDSTACK-7422
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7422
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.5.0
Environment: Vmware 5.0
build 4.5
Reporter: Rayees Namathponnan
Priority: Critical
Fix For: 4.5.0
Steps to reproduce the defect
Run the test
integration.component.test_volumes.TestAttachVolumeISO.test_01_volume_iso_attach
This test case performing below steps
678 # Validate the following
679 # 1. Create and attach 5 data volumes to VM
680 # 2. Create an ISO. Attach it to VM instance
681 # 3. Verify that attach ISO is successful
Here attach volume fails with below error
{noformat}
a5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAZh0ABRWb2x1
bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAACnNxAH4ABgHJ
, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Sat Aug 23 14:45:42 PDT 2014}, job
origin:3043
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
TestDiskServ to VM TestVM-24cfe95b-8976-48af-ba42-459b37cfb89c; AttachV
olumeCommand failed due to Exception: java.lang.RuntimeException
Message: Invalid configuration for device '0'.
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2248)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1216)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2615)
at sun.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
at sun.reflect.GeneratedMethodAccessor568.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy184.handleVmWorkJob(Unknown Source)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
[jira] [Commented] (CLOUDSTACK-7422) [Automation] Attach volume test case failing with error Invalid configuration for device '0'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237461#comment-14237461
]
Sailaja Mada commented on CLOUDSTACK-7422:
--
Similar issue fixed by Likitha recently . It is not automation bug.
[Automation] Attach volume test case failing with error Invalid
configuration for device '0'
--
Key: CLOUDSTACK-7422
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7422
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Volumes
Affects Versions: 4.5.0
Environment: Vmware 5.0
build 4.5
Reporter: Rayees Namathponnan
Priority: Critical
Fix For: 4.5.0
Steps to reproduce the defect
Run the test
integration.component.test_volumes.TestAttachVolumeISO.test_01_volume_iso_attach
This test case performing below steps
678 # Validate the following
679 # 1. Create and attach 5 data volumes to VM
680 # 2. Create an ISO. Attach it to VM instance
681 # 3. Verify that attach ISO is successful
Here attach volume fails with below error
{noformat}
a5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAZh0ABRWb2x1
bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAACnNxAH4ABgHJ
, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Sat Aug 23 14:45:42 PDT 2014}, job
origin:3043
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume
TestDiskServ to VM TestVM-24cfe95b-8976-48af-ba42-459b37cfb89c; AttachV
olumeCommand failed due to Exception: java.lang.RuntimeException
Message: Invalid configuration for device '0'.
at
com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2248)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1216)
at
com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2615)
at sun.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
at sun.reflect.GeneratedMethodAccessor568.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy184.handleVmWorkJob(Unknown Source)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
[jira] [Updated] (CLOUDSTACK-7613) [UI]CPU Sockets page does not display XenServer 6.5 Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7613: - Attachment: sailajacloud_usage.sql sailajacloud.sql [UI]CPU Sockets page does not display XenServer 6.5 Information --- Key: CLOUDSTACK-7613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7613 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Sailaja Mada Fix For: 4.5.0 Attachments: listCPUsocktesUI.png, sailajacloud.sql, sailajacloud_usage.sql Steps: 1. Install and configure Adv zone with XS 6.5 2. Tried to view CPU Sockets page from Infrastructure page Observation: 1. It is calling list hosts by XenServer hypervisor and its receiving the count 2 for XS 6.5. But its displayed in the UI. Attached snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7613) [UI]CPU Sockets page does not display XenServer 6.5 Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7613: - Assignee: Jessica Wang (was: Sailaja Mada) [UI]CPU Sockets page does not display XenServer 6.5 Information --- Key: CLOUDSTACK-7613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7613 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Jessica Wang Fix For: 4.5.0 Attachments: listCPUsocktesUI.png, sailajacloud.sql, sailajacloud_usage.sql Steps: 1. Install and configure Adv zone with XS 6.5 2. Tried to view CPU Sockets page from Infrastructure page Observation: 1. It is calling list hosts by XenServer hypervisor and its receiving the count 2 for XS 6.5. But its displayed in the UI. Attached snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6372) [UI]Incorrect Field name while adding Primary Storage (*label.path)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-6372. closing as per previous comment [UI]Incorrect Field name while adding Primary Storage (*label.path) --- Key: CLOUDSTACK-6372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6372 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Chris Suich Priority: Minor Fix For: 4.4.0 Attachments: addPSsnap.png Steps: 1. Install and Configure Management Server 2. Tried to add Primary Storage while configuring the Zone Observation: Noticed incorrect Field name while adding Primary Storage (*label.path) (attached snap) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6412) [UI]Incorrect Field value added with host details page(Dedicated label.no)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-6412. closing as per previous comment [UI]Incorrect Field value added with host details page(Dedicated label.no) -- Key: CLOUDSTACK-6412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6412 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Jessica Wang Priority: Minor Fix For: 4.4.0 Attachments: dedicatedincorrectlabel.png Setup: ACS 4.4 with XenServer 6.2.5 Steps: 1. Install and configure Adv zone using Xenserver 6.2.5 2. Go to Host Details page Observation: Incorrect Field value added with host details page(Dedicated label.no) (Attached the snapshot) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6414) [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-6414. Its fixed. Hence closing the bug. [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Key: CLOUDSTACK-6414 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6414 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Jessica Wang Fix For: 4.4.0 Attachments: FailedtoaddDomainAdminUI.png Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) createAccount API call works to create Domain Admin User. It is the failure only in the UI. Attached Firebug snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada closed CLOUDSTACK-6575.
Its fixed. Hence closing the bug.
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Saksham Srivastava
Priority: Critical
Fix For: 4.4.0
Attachments: logs.zip
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) unhandled exception executing
api command: [Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167)
at
[jira] [Updated] (CLOUDSTACK-4139) [VMWARE]Failed to resize the volumes which are created from snapshot of root volume with controller type IDE.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-4139:
-
Fix Version/s: 4.5.0
[VMWARE]Failed to resize the volumes which are created from snapshot of root
volume with controller type IDE.
-
Key: CLOUDSTACK-4139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Sateesh Chodapuneedi
Fix For: 4.4.0, 4.5.0
Attachments: apilog.log, management-server.log, newdb.sql
Steps:
1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
2. Deploy instance
3. Create snapshot from ROOT volume
4. Attach the volume to an instance
5. Tried to resize the volume from 2 GB to 5 GB .
Observation:
1. It Failed to resize the volumes which are created from snapshot .
2. Task notification says resize is completed from UI but it failed and no
resize happened for this volume
3. I could resize the DATA volumes which are added by using the disk offering
and attached to the instance.
2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785: { Ans: ,
MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===START=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-21:null) submit async job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId:
3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null,
cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd,
cmdOriginator: null, cmdInfo:
{id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null)
===END=== 10.144.6.19 -- GET
command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing
org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [
40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to
Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by
DomainChecker_EnhancerByCloudStack_ccb7a71
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Sending { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,534 DEBUG [agent.transport.Request]
(Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq
2-1287389738: Executing: { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
}
2013-08-07 16:37:33,557 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-32:null) Seq 2-1287389738: Executing request
2013-08-07
[jira] [Updated] (CLOUDSTACK-4593) [VMWARE] [Upgrade]Livestorage Migration VM Snapshot features are not fully functional after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-4593: - Fix Version/s: 4.5.0 [VMWARE] [Upgrade]Livestorage Migration VM Snapshot features are not fully functional after upgrade -- Key: CLOUDSTACK-4593 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4593 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller, Upgrade, VMware Affects Versions: 4.2.1 Reporter: Sailaja Mada Assignee: Sateesh Chodapuneedi Fix For: 4.4.0, 4.5.0 Attachments: apilogs.rar, clouddbback.dmp, mgmtlogs.rar Steps: Upgraded setup : 307 Setup with 2 clusters ( Cluster1 – 2 ESXi 5.0 hosts , Cluster2 – Esxi 4.1 host) 1.11 Vm’s deployed with 2 VM’s in stopped state 2.VM’s with ROOT volume, 2 DATA volumes, 3 DATA volumes 3.Snapshots , Template / volumes from this snapshot 4.Detached volumes 5.Empty volumes which are not attached to any instance 6.Cluster with 2 primary storage's Upgraded to 4.2 I got into below failures with VM Snapshot if tried without Stop/Start of the VM Post upgrade : 2013-09-02 21:35:36,733 WARN [vmware.resource.VmwareResource] (DirectAgent-320:10.102.192.23) StartCommand failed due to Exception: java.lang.RuntimeException Message: File unspecified filename was not found java.lang.RuntimeException: File unspecified filename was not found at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378) at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.powerOn(VirtualMachineMO.java:188) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2966) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-09-02 21:35:36,742 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-320:null) Seq 6-949618439: Response Received: 2013-09-02 21:35:43,972 INFO [storage.volume.VolumeServiceImpl] (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) Volume 52 is not referred anywhere, remove it from volumes table 2013-09-02 21:35:43,981 ERROR [cloud.storage.VolumeManagerImpl] (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) migrate volume failed:copy volume from primary to secondary failed due to exception: Exception: java.lang.Exception Message: Unable to find related disk device for volume. volume path: ROOT-14-30-04 2013-09-02 21:35:43,990 INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-75:job-151 = [ 3e8e2327-7c56-45ea-a653-ee5b89d75d57 ]) Unable to contact resource. com.cloud.exception.StorageUnavailableException: Resource [StoragePool:203] is unreachable: migrate volume failed: copy volume from primary to secondary failed due to exception: Exception: java.lang.Exception Message: Unable to find related disk device for volume. volume path: ROOT-14-30-04 at com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2254) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2590) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at
[jira] [Updated] (CLOUDSTACK-3995) No error notification is generated when Primary storage (Zonelevel) is added with wrong path and it is allowed to add
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3995:
-
Fix Version/s: 4.5.0
No error notification is generated when Primary storage (Zonelevel) is added
with wrong path and it is allowed to add
-
Key: CLOUDSTACK-3995
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3995
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Minor
Fix For: 4.4.0, 4.5.0
Attachments: apilog.log, management-server.log
Steps:
1. Configure Adv zone with VMWARE
2. Tried to add wrong Zone wide primary storage point
Observation:
It is allowed to add with wrong path and there is no failure error
notification. But in the logs it says storage pool addition failed.
2013-08-01 10:11:30,741 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null)
===START=== 10.144.6.19 -- GET
command=createStoragePoolscope=zonezoneid=176d7081-e1d2-4472-8a17-eff1322ddd39hypervisor=VMwarename=wrongzwps1url=nfs%3A%2F%2F10.102.192.100%2Fcpg_vol%2Fsailaja%2Fwrongzwps1response=jsonsessionkey=x8JP8GtGm4LirW0b8AK9sVj26D0%3D_=1375332320686
2013-08-01 10:11:30,748 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) createPool Params @ scheme - nfs storageHost -
10.102.192.100 hostPath - /cpg_vol/sailaja/wrongzwps1 port - -1
2013-08-01 10:11:30,763 DEBUG [cloud.storage.StorageManagerImpl]
(catalina-exec-17:null) Adding pool null to host 1
2013-08-01 10:11:30,767 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-757532167: Sending { Cmd , MgmtId:
187767034175903, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.ModifyStoragePoolCommand:{add:true,pool:{id:6,uuid:8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,host:10.102.192.100,path:/cpg_vol/sailaja/wrongzwps1,port:2049,type:NetworkFilesystem},localPath:/mnt//8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,wait:0}}]
}
2013-08-01 10:11:30,767 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-757532167: Executing: { Cmd , MgmtId:
187767034175903, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.ModifyStoragePoolCommand:{add:true,pool:{id:6,uuid:8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,host:10.102.192.100,path:/cpg_vol/sailaja/wrongzwps1,port:2049,type:NetworkFilesystem},localPath:/mnt//8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,wait:0}}]
}
2013-08-01 10:11:30,768 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-52:null) Seq 1-757532167: Executing request
2013-08-01 10:11:30,768 INFO [vmware.resource.VmwareResource]
(DirectAgent-52:10.102.192.18) Executing resource ModifyStoragePoolCommand:
{add:true,pool:{id:6,uuid:8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,host:10.102.192.100,path:/cpg_vol/sailaja/wrongzwps1,port:2049,type:NetworkFilesystem},localPath:/mnt//8f4e2b4b-76a2-3f11-b98c-2ee8108ab900,wait:0}
2013-08-01 10:11:30,949 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 3 routers to update status.
2013-08-01 10:11:30,951 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-08-01 10:11:30,962 INFO [vmware.mo.HostMO]
(DirectAgent-52:10.102.192.18) Creation of NFS datastore on vCenter failed.
Details: vCenter API trace - mountDatastore(). target MOR: host-8973, vmfs:
false, poolHost: 10.102.192.100, poolHostPort: 2049, poolPath:
/cpg_vol/sailaja/wrongzwps1, poolUuid: 8f4e2b4b76a23f11b98c2ee8108ab900.
Exception mesg: An error occurred during host configuration.
2013-08-01 10:11:30,962 ERROR [vmware.resource.VmwareResource]
(DirectAgent-52:10.102.192.18) ModifyStoragePoolCommand failed due to
Exception: java.lang.Exception
Message: Creation of NFS datastore on vCenter failed.
java.lang.Exception: Creation of NFS datastore on vCenter failed.
at
com.cloud.hypervisor.vmware.mo.HostMO.mountDatastore(HostMO.java:772)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4102)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:472)
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
[jira] [Closed] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-7598. This is fixed now. Hence closing the bug. Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Devdeep Singh Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7505: - Fix Version/s: 4.5.0 Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Anthony Xu Priority: Blocker Fix For: 4.5.0 Attachments: i-2-10-VM-from-tools-template, i-2-7-vm-params-after-registeriso-PVtoolsinstallation Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-7505. This is fixed now. Hence closing the bug. Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Anthony Xu Priority: Blocker Fix For: 4.5.0 Attachments: i-2-10-VM-from-tools-template, i-2-7-vm-params-after-registeriso-PVtoolsinstallation Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7683) NPE while expunging the failed VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7683: - Attachment: expungenpelogs.zip NPE while expunging the failed VM - Key: CLOUDSTACK-7683 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7683 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Attachments: expungenpelogs.zip Steps: 1. Install and configure with XS 6.5 2. Tried to Deployed VM (Windows 7) . It failed to deploy VM due to resources not being available 3. Deleted this VM which is in Error state Observation:NPE while expunging the failed VM 2014-10-08 11:09:11,894 DEBUG [o.a.c.s.v.VolumeObject] (API-Job-Executor-58:ctx-bdc8e992 job-4398 ctx-8115790b) Failed to update state java.lang.NullPointerException at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:101) at org.apache.cloudstack.storage.volume.VolumeObject.stateTransit(VolumeObject.java:185) at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:325) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.deleteVolumeCallback(VolumeServiceImpl.java:339) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.deleteAsync(CloudStackPrimaryDataStoreDriverImpl.java:222) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.expungeVolumeAsync(VolumeServiceImpl.java:323) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.cleanupVolumes(VolumeOrchestrator.java:862) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:522) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:454) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1709) at sun.reflect.GeneratedMethodAccessor803.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:665) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1444) at sun.reflect.GeneratedMethodAccessor816.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at
[jira] [Created] (CLOUDSTACK-7683) NPE while expunging the failed VM
Sailaja Mada created CLOUDSTACK-7683: Summary: NPE while expunging the failed VM Key: CLOUDSTACK-7683 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7683 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Install and configure with XS 6.5 2. Tried to Deployed VM (Windows 7) . It failed to deploy VM due to resources not being available 3. Deleted this VM which is in Error state Observation:NPE while expunging the failed VM 2014-10-08 11:09:11,894 DEBUG [o.a.c.s.v.VolumeObject] (API-Job-Executor-58:ctx-bdc8e992 job-4398 ctx-8115790b) Failed to update state java.lang.NullPointerException at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:101) at org.apache.cloudstack.storage.volume.VolumeObject.stateTransit(VolumeObject.java:185) at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:325) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.deleteVolumeCallback(VolumeServiceImpl.java:339) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.deleteAsync(CloudStackPrimaryDataStoreDriverImpl.java:222) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.expungeVolumeAsync(VolumeServiceImpl.java:323) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.cleanupVolumes(VolumeOrchestrator.java:862) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:522) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:454) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1709) at sun.reflect.GeneratedMethodAccessor803.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:665) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1444) at sun.reflect.GeneratedMethodAccessor816.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at
[jira] [Updated] (CLOUDSTACK-7683) NPE while expunging the failed VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7683: - Fix Version/s: 4.5.0 NPE while expunging the failed VM - Key: CLOUDSTACK-7683 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7683 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Steps: 1. Install and configure with XS 6.5 2. Tried to Deployed VM (Windows 7) . It failed to deploy VM due to resources not being available 3. Deleted this VM which is in Error state Observation:NPE while expunging the failed VM 2014-10-08 11:09:11,894 DEBUG [o.a.c.s.v.VolumeObject] (API-Job-Executor-58:ctx-bdc8e992 job-4398 ctx-8115790b) Failed to update state java.lang.NullPointerException at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:101) at org.apache.cloudstack.storage.volume.VolumeObject.stateTransit(VolumeObject.java:185) at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:325) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.deleteVolumeCallback(VolumeServiceImpl.java:339) at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:25) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:126) at org.apache.cloudstack.storage.datastore.driver.CloudStackPrimaryDataStoreDriverImpl.deleteAsync(CloudStackPrimaryDataStoreDriverImpl.java:222) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.expungeVolumeAsync(VolumeServiceImpl.java:323) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.cleanupVolumes(VolumeOrchestrator.java:862) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:522) at com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:454) at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1709) at sun.reflect.GeneratedMethodAccessor803.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy212.expunge(Unknown Source) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:738) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:665) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1444) at sun.reflect.GeneratedMethodAccessor816.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at
[jira] [Closed] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada closed CLOUDSTACK-6382.
This is fixed now. Hence closing the bug
System VM's failing to start with XenServer 6.2.5
-
Key: CLOUDSTACK-6382
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6382
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Anthony Xu
Priority: Blocker
Fix For: 4.4.0
Steps:
Build : 4.4
Configure Adv zone with XenServer 6.2.5
Observation:
System VM’s are failing to start with below exception and there are lot of
SR’s that got added to XenServer .
2014-04-10 16:09:42,622 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:job-4/job-22 ctx-4609aa64) Seq 1-8947526559678332946:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/1/,origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.101/Sailaja/gpuss1,_role:Image}},name:routing-1,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:0a336642-b7d7-3262-ae46-8f06ccdf8c30,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpups1/?ROLE=PrimarySTOREUUID=0a336642-b7d7-3262-ae46-8f06ccdf8c30}},name:routing-1,hypervisorType:XenServer}},executeInSequence:false,options:{},wait:10800}}]
}
2014-04-10 16:09:42,624 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) template 1 is already in
store:1, type:Primary
2014-04-10 16:09:42,627 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Found template routing-1 in
storage pool 1 with VMTemplateStoragePool id: 2
2014-04-10 16:09:42,630 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-13:ctx-d982de4d) Seq 1-8947526559678332946: Executing request
2014-04-10 16:09:42,654 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Acquire lock on
VMTemplateStoragePool 2 with timeout 3600 seconds
2014-04-10 16:09:42,657 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,660 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-13:ctx-d982de4d) Failed to destroy pbd
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG
[jira] [Closed] (CLOUDSTACK-6684) Error instances are not getting expunged within the specified expunge interval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada closed CLOUDSTACK-6684.
This is fixed now. Hence closing the bug
Error instances are not getting expunged within the specified expunge interval
--
Key: CLOUDSTACK-6684
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6684
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Likitha Shetty
Priority: Critical
Fix For: 4.4.0
Attachments: expungelogs.zip
Steps:
1. Configure Adv zone using Xenserver 6.2.5
2. Deployed windows 2012 R2 and window 8 instances
3. Set the expunge interval to 10 seconds
3. Windows 2012 R2 instances failed to deploy due to another bug
https://issues.apache.org/jira/browse/CLOUDSTACK-6661
These failed instances are in Error state.
Expunge thread triggered to expunge instances. It identified the instances
to expunge but failed to do with Runtime exceptions,
2014-05-15 15:23:03,552 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Processing Seq 2-1697: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: [\n{\n \id\: 10,\n \clientInfo\: \\,\n
\host\: \10.102.192.10\,\n \port\: -1,\n \tag\:
\3884c408-9b63-4f04-ab63-4626e0cbd9af\,\n \createTime\:
1400166406368,\n \lastUsedTime\: 1400166620142\n}\n
]\n},wait:0}}] }
2014-05-15 15:23:03,556 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Sending Seq 2-1697: { Ans: ,
MgmtId: 55355881446856, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-15 15:23:06,528 INFO [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Found 2 vms to expunge.
2014-05-15 15:23:06,531 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-3-7-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-05-15 15:23:06,534 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-2-10-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
[jira] [Created] (CLOUDSTACK-7606) [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page
Sailaja Mada created CLOUDSTACK-7606: Summary: [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page Key: CLOUDSTACK-7606 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7606 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Configure Adv zone using XS 6.5 2. Uploaded a new vhd volume using upload volume option 3. Access this volume details page Observation: [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7606) [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7606: - Attachment: incorrectuploadvolumeid.png [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page --- Key: CLOUDSTACK-7606 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7606 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: incorrectuploadvolumeid.png Steps: 1. Configure Adv zone using XS 6.5 2. Uploaded a new vhd volume using upload volume option 3. Access this volume details page Observation: [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7606) [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7606: - Fix Version/s: 4.5.0 [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page --- Key: CLOUDSTACK-7606 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7606 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: incorrectuploadvolumeid.png Steps: 1. Configure Adv zone using XS 6.5 2. Uploaded a new vhd volume using upload volume option 3. Access this volume details page Observation: [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7607) [UI]Incorrect name ( ???label.user.vm???) with cloudstack dash board General Alerts
Sailaja Mada created CLOUDSTACK-7607: Summary: [UI]Incorrect name ( ???label.user.vm???) with cloudstack dash board General Alerts Key: CLOUDSTACK-7607 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7607 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Configure Adv zone using XS 6.5 2. Deployed VM . It failed to deploy due to insufficient resources. 3. This generated an Alert for user VM deploy failure Observation : [UI]Incorrect name ( ???label.user.vm???) with cloudstack dash board General Alerts Attached screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7606) [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7606: - Attachment: incorrectdashboardUI.png [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page --- Key: CLOUDSTACK-7606 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7606 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: incorrectdashboardUI.png, incorrectuploadvolumeid.png Steps: 1. Configure Adv zone using XS 6.5 2. Uploaded a new vhd volume using upload volume option 3. Access this volume details page Observation: [UI]Incorrect Field value (???label.vm.id??? state.detached) with uploaded volume details page Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7608) [UI]Incorrect name (View ???label.portable.ip???) with Region Details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7608: - Attachment: incorrectregionUI.png [UI]Incorrect name (View ???label.portable.ip???) with Region Details page Key: CLOUDSTACK-7608 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7608 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Attachments: incorrectregionUI.png Steps: 1. Configure Adv zone using XS 6.5 2. Access Region = Details page Observation: [UI]Incorrect name (View ???label.portable.ip???) with Region Details page Attached screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7608) [UI]Incorrect name (View ???label.portable.ip???) with Region Details page
Sailaja Mada created CLOUDSTACK-7608: Summary: [UI]Incorrect name (View ???label.portable.ip???) with Region Details page Key: CLOUDSTACK-7608 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7608 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Attachments: incorrectregionUI.png Steps: 1. Configure Adv zone using XS 6.5 2. Access Region = Details page Observation: [UI]Incorrect name (View ???label.portable.ip???) with Region Details page Attached screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7609) [UI]Tool tip information is not available for GPU card selection while creating Compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7609: - Fix Version/s: 4.5.0 [UI]Tool tip information is not available for GPU card selection while creating Compute offering Key: CLOUDSTACK-7609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7609 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Steps: 1. Tried to create Compute offering with GPU card and vGPU type. Observation: [UI]Tool tip information is not available for GPU card selection while creating Compute offering Attached screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7609) [UI]Tool tip information is not available for GPU card selection while creating Compute offering
Sailaja Mada created CLOUDSTACK-7609: Summary: [UI]Tool tip information is not available for GPU card selection while creating Compute offering Key: CLOUDSTACK-7609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7609 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Tried to create Compute offering with GPU card and vGPU type. Observation: [UI]Tool tip information is not available for GPU card selection while creating Compute offering Attached screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7609) [UI]Tool tip information is not available for GPU card selection while creating Compute offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7609: - Attachment: GPUtooltip.png [UI]Tool tip information is not available for GPU card selection while creating Compute offering Key: CLOUDSTACK-7609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7609 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: GPUtooltip.png Steps: 1. Tried to create Compute offering with GPU card and vGPU type. Observation: [UI]Tool tip information is not available for GPU card selection while creating Compute offering Attached screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7598: - Fix Version/s: 4.5.0 Cloudstack VM State is not in sync with state from Hypervisor - Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.5.0 Attachments: vmsynclogs.rar Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7613) [UI]CPU Sockets page does not display XenServer 6.5 Information
Sailaja Mada created CLOUDSTACK-7613: Summary: [UI]CPU Sockets page does not display XenServer 6.5 Information Key: CLOUDSTACK-7613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7613 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Install and configure Adv zone with XS 6.5 2. Tried to view CPU Sockets page from Infrastructure page Observation: 1. It is calling list hosts by XenServer hypervisor and its receiving the count 2 for XS 6.5. But its displayed in the UI. Attached snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7613) [UI]CPU Sockets page does not display XenServer 6.5 Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7613: - Fix Version/s: 4.5.0 [UI]CPU Sockets page does not display XenServer 6.5 Information --- Key: CLOUDSTACK-7613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7613 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: listCPUsocktesUI.png Steps: 1. Install and configure Adv zone with XS 6.5 2. Tried to view CPU Sockets page from Infrastructure page Observation: 1. It is calling list hosts by XenServer hypervisor and its receiving the count 2 for XS 6.5. But its displayed in the UI. Attached snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7613) [UI]CPU Sockets page does not display XenServer 6.5 Information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7613: - Attachment: listCPUsocktesUI.png [UI]CPU Sockets page does not display XenServer 6.5 Information --- Key: CLOUDSTACK-7613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7613 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: listCPUsocktesUI.png Steps: 1. Install and configure Adv zone with XS 6.5 2. Tried to view CPU Sockets page from Infrastructure page Observation: 1. It is calling list hosts by XenServer hypervisor and its receiving the count 2 for XS 6.5. But its displayed in the UI. Attached snap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7597) [UI]Incorrect Field value (???label.vgpu???) with VM details page
Sailaja Mada created CLOUDSTACK-7597: Summary: [UI]Incorrect Field value (???label.vgpu???) with VM details page Key: CLOUDSTACK-7597 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7597 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Install and configure adv zone(XenServer 6.5). 2. Deploy VM instance 3. Try to view VM details screen Observation: [UI]Incorrect Field value (???label.vgpu???) with VM details page (Attached screen) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7597) [UI]Incorrect Field value (???label.vgpu???) with VM details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7597: - Attachment: incorrectlable.png [UI]Incorrect Field value (???label.vgpu???) with VM details page -- Key: CLOUDSTACK-7597 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7597 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: incorrectlable.png Steps: 1. Install and configure adv zone(XenServer 6.5). 2. Deploy VM instance 3. Try to view VM details screen Observation: [UI]Incorrect Field value (???label.vgpu???) with VM details page (Attached screen) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7597) [UI]Incorrect Field value (???label.vgpu???) with VM details page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7597: - Fix Version/s: 4.5.0 [UI]Incorrect Field value (???label.vgpu???) with VM details page -- Key: CLOUDSTACK-7597 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7597 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: incorrectlable.png Steps: 1. Install and configure adv zone(XenServer 6.5). 2. Deploy VM instance 3. Try to view VM details screen Observation: [UI]Incorrect Field value (???label.vgpu???) with VM details page (Attached screen) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7598) Cloudstack VM State is not in sync with state from Hypervisor
Sailaja Mada created CLOUDSTACK-7598: Summary: Cloudstack VM State is not in sync with state from Hypervisor Key: CLOUDSTACK-7598 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Steps: 1. Install and configure Adv zone using XS 6.5 Hypervisor 2. Deploy Linux VM , Windows VM 3. After VM is up and running login to the VM and shutdown the instance 4. It moved to Shutdown state in the hypervisor 5. But this state is not synced to cloudstack and it remained in running state in cloudstack Observation: Cloudstack VM State is not in sync with state from Hypervisor Ob -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7518: - Attachment: ssvmlogs.zip SSVM stop/start is not initiating the download for Partially downloaded ISO's -- Key: CLOUDSTACK-7518 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Attachments: isologs.zip, ssvmlogs.zip Setup: 1. Configure Adv Zone with XS 6.5 2. Register Windows 2012 ISO , Waited for it to download 20% 3. Stop SSVM 4. ISO details gets the status as SSVM Agent disconnected 5. Start SSVM Observation: SSVM stop/start is not initiating the download for Partially downloaded templates/ISO's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7526) [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7526: - Attachment: screenshot-1.png [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) --- Key: CLOUDSTACK-7526 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7526 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: screenshot-1.png Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Attached screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7526) [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7526: - Fix Version/s: 4.5.0 [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) --- Key: CLOUDSTACK-7526 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7526 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: screenshot-1.png Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Attached screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7526) [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add)
Sailaja Mada created CLOUDSTACK-7526: Summary: [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Key: CLOUDSTACK-7526 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7526 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Attached screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7526) [UI]Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7526: - Summary: [UI]Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add) (was: [UI]Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add)) [UI]Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add) Key: CLOUDSTACK-7526 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7526 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: screenshot-1.png Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Attached screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7526) [UI]Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7526: - Description: Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add) Attached screen was: Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO details page while adding Tags(Key and Value) (label.add) Attached screen [UI]Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add) Key: CLOUDSTACK-7526 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7526 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Fix For: 4.5.0 Attachments: screenshot-1.png Steps: 1. Access Management Server UI 2. Go to Templates = Details of any of the template Observation: Observed Incorrect Field value with Template/ISO/Network/Instance details page while adding Tags(Key and Value) (label.add) Attached screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-7498) [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-7498: -- This issue is reproducible. With user logout/login to the UI , it works fine first time. Second time it gets into the issue again. [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined -- Key: CLOUDSTACK-7498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Attachments: registerisoUI.png Steps: 1. Install 4.5 cloudstack 2. Access Management Server UI and tried register ISO Observations : 1. It is not invoking Register ISO page and failing with ReferenceError: osTypeObjs is not defined Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instanc
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126763#comment-14126763
]
Sailaja Mada commented on CLOUDSTACK-7505:
--
1. Register ISO and Installed Windows 8/2012 operating System
2. Attach PV tools and installed on to the Guest OS
xe vm-param-list for this vm
uuid ( RO) : f5b3e0b2-d61a-d0cc-2638-616feb9fc0d0
name-label ( RW): i-2-7-VM
name-description ( RW): Clones of this template will
automatically provision their storage when first booted and then reconfigure
themselves with the optimal settings for Windows 8 (64-bit).
user-version ( RW): 1
is-a-template ( RW): false
is-a-snapshot ( RO): false
snapshot-of ( RO): not in database
snapshots ( RO):
snapshot-time ( RO): 19700101T00:00:00Z
snapshot-info ( RO):
parent ( RO): not in database
children ( RO):
is-control-domain ( RO): false
power-state ( RO): running
memory-actual ( RO): 2147487744
memory-target ( RO): unknown
memory-overhead ( RO): 20971520
memory-static-max ( RW): 2147483648
memory-dynamic-max ( RW): 2147483648
memory-dynamic-min ( RW): 2147483648
memory-static-min ( RW): 2147483648
suspend-VDI-uuid ( RW): not in database
suspend-SR-uuid ( RW): not in database
VCPUs-params (MRW): weight: 33; cap: 0
VCPUs-max ( RW): 2
VCPUs-at-startup ( RW): 2
actions-after-shutdown ( RW): Destroy
actions-after-reboot ( RW): Restart
actions-after-crash ( RW): Destroy
console-uuids (SRO): b59bf3aa-cd56-cd96-0b3b-439d8a2860f2
platform (MRW): timeoffset: 0; viridian: true; acpi: 1;
apic: true; pae: true; videoram: 8; nx: true; vga: std
allowed-operations (SRO): changing_dynamic_range; migrate_send;
pool_migrate; changing_VCPUs_live; suspend; hard_reboot; hard_shutdown;
clean_reboot; clean_shutdown; pause; checkpoint; snapshot
current-operations (SRO):
blocked-operations (MRW):
allowed-VBD-devices (SRO): 1; 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13;
14; 15
allowed-VIF-devices (SRO): 1; 2; 3; 4; 5; 6
possible-hosts ( RO): d079d968-6311-4bb2-87b7-0dc017971fa1
HVM-boot-policy ( RW): BIOS order
HVM-boot-params (MRW): order: dc
HVM-shadow-multiplier ( RW): 1.000
PV-kernel ( RW):
PV-ramdisk ( RW):
PV-args ( RW):
PV-legacy-args ( RW):
PV-bootloader ( RW):
PV-bootloader-args ( RW):
last-boot-CPU-flags ( RO): vendor: GenuineIntel; features:
17bee3ff-bfebfbff-0001-2c100800
last-boot-record ( RO): '('struct' ('uuid'
'f5b3e0b2-d61a-d0cc-2638-616feb9fc0d0') ('allowed_operations' ('array'))
('current_operations' ('struct'
('OpaqueRef:a2590e3b-e04f-ea4a-66f1-4a90bcf5729a' 'start_on'))) ('power_state'
'Halted') ('name_label' 'i-2-7-VM') ('name_description' 'Clones of this
template will automatically provision their storage when first booted and then
reconfigure themselves with the optimal settings for Windows 8 (64-bit).')
('user_version' '1') ('is_a_template' ('boolean' '0')) ('suspend_VDI'
'OpaqueRef:NULL') ('resident_on' 'OpaqueRef:NULL') ('affinity'
'OpaqueRef:01ec70b4-aadf-5a08-7649-2e81495f3ff1') ('memory_overhead'
'20971520') ('memory_target' '4294967296') ('memory_static_max' '2147483648')
('memory_dynamic_max' '2147483648') ('memory_dynamic_min' '2147483648')
('memory_static_min' '2147483648') ('VCPUs_params' ('struct' ('weight' '33')
('cap' '0'))) ('VCPUs_max' '2') ('VCPUs_at_startup' '2')
('actions_after_shutdown' 'destroy') ('actions_after_reboot' 'restart')
('actions_after_crash' 'destroy') ('consoles' ('array')) ('VIFs' ('array'
'OpaqueRef:c71b8934-60d5-c8c9-88fe-44b3357fb73b')) ('VBDs' ('array'
'OpaqueRef:dda2c6d4-eed0-2888-d56f-604e90a4560c'
'OpaqueRef:5eb90a80-63c8-0d2e-e1ce-0da8ab42d8f0')) ('crash_dumps' ('array'))
('VTPMs' ('array')) ('PV_bootloader' '') ('PV_kernel' '') ('PV_ramdisk' '')
('PV_args' '') ('PV_bootloader_args' '') ('PV_legacy_args' '')
('HVM_boot_policy' 'BIOS order') ('HVM_boot_params' ('struct' ('order' 'dc')))
('HVM_shadow_multiplier' ('double' '1')) ('platform' ('struct' ('viridian'
'true') ('acpi' '1') ('apic' 'true') ('pae' 'true') ('videoram' '8') ('nx'
'true') ('vga' 'std'))) ('PCI_bus' '') ('other_config' ('struct' ('mac_seed'
'5232f4ca-45f7-5e01-65bb-9fc14eab8ff1') ('install-methods' 'cdrom') ('vm_uuid'
[jira] [Updated] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7505: - Attachment: i-2-10-VM-from-tools-template i-2-7-vm-params-after-registeriso-PVtoolsinstallation Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Attachments: i-2-10-VM-from-tools-template, i-2-7-vm-params-after-registeriso-PVtoolsinstallation Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's
Sailaja Mada created CLOUDSTACK-7518: Summary: SSVM stop/start is not initiating the download for Partially downloaded ISO's Key: CLOUDSTACK-7518 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Attachments: isologs.zip Setup: 1. Configure Adv Zone with XS 6.5 2. Register Windows 2012 ISO , Waited for it to download 20% 3. Stop SSVM 4. ISO details gets the status as SSVM Agent disconnected 5. Start SSVM Observation: SSVM stop/start is not initiating the download for Partially downloaded templates/ISO's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7518: - Attachment: isologs.zip SSVM stop/start is not initiating the download for Partially downloaded ISO's -- Key: CLOUDSTACK-7518 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Attachments: isologs.zip Setup: 1. Configure Adv Zone with XS 6.5 2. Register Windows 2012 ISO , Waited for it to download 20% 3. Stop SSVM 4. ISO details gets the status as SSVM Agent disconnected 5. Start SSVM Observation: SSVM stop/start is not initiating the download for Partially downloaded templates/ISO's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7518) SSVM stop/start is not initiating the download for Partially downloaded ISO's
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7518: - Fix Version/s: 4.5.0 SSVM stop/start is not initiating the download for Partially downloaded ISO's -- Key: CLOUDSTACK-7518 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7518 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template, XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.5.0 Attachments: isologs.zip Setup: 1. Configure Adv Zone with XS 6.5 2. Register Windows 2012 ISO , Waited for it to download 20% 3. Stop SSVM 4. ISO details gets the status as SSVM Agent disconnected 5. Start SSVM Observation: SSVM stop/start is not initiating the download for Partially downloaded templates/ISO's -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7505) Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances
Sailaja Mada created CLOUDSTACK-7505: Summary: Windows 2012 and Windows 8 instances created with 6.5 PV tools installed template are getting into repair state, Later XenServer 6.5 Is shutting down these instances automatically Key: CLOUDSTACK-7505 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7505 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Steps: 1. Configure Adv Zone using XenServer 6.5 2. Registered Windows 8 and Windows 2012 templates which has XS 6.5 PV tools installed.I have enabled option Original XS Version is 6.1+: Yes 3. Deployed VM using this template 4. VM got started and moved to running state. But got into repair state, Later XenServer 6.5 Is shutting down these instances automatically. VM Parameters are : platform (MRW): timeoffset: 0; viridian: true; acpi: 1; ap ic: true; pae: true; videoram: 8; device_id: 0002; nx: true; vga: std allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_ shutdown; pause; snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7498) [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada closed CLOUDSTACK-7498. Resolution: Cannot Reproduce This is working now. [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined -- Key: CLOUDSTACK-7498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Attachments: registerisoUI.png Steps: 1. Install 4.5 cloudstack 2. Access Management Server UI and tried register ISO Observations : 1. It is not invoking Register ISO page and failing with ReferenceError: osTypeObjs is not defined Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7495) [Automation][HyperV] Stack trace along with error message - CloudStack currently only supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125217#comment-14125217
]
Sailaja Mada commented on CLOUDSTACK-7495:
--
This is automated and BVT is skipping this test:
elif hosts[0].hypervisor.lower() in (vmware, hyperv):
self.skipTest(Resize Volume is unsupported on VmWare and Hyper-V)
[Automation][HyperV] Stack trace along with error message - CloudStack
currently only supports volumes marked as the KVM, VMware, or XenServer
hypervisor type for resize.
--
Key: CLOUDSTACK-7495
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7495
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
{code}
2014-09-03 17:55:32,084 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-5e814549 ctx-6724d865 ctx-56a27ef7) ===END===
10.220.135.217 -- GET
jobid=3f397629-d004-4020-a97d-8aa277ea2c61apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=6X9pGZqTxQTAxWy4N73kVno%2B62s%3D
2014-09-03 17:55:32,091 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-123:ctx-0a86f6fa job-255) Unexpected exception while
executing
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
com.cloud.exception.InvalidParameterValueException: CloudStack currently only
supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
resize.
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:725)
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy184.resizeVolume(Unknown Source)
at
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin.execute(ResizeVolumeCmdByAdmin.java:37)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at
[jira] [Created] (CLOUDSTACK-7498) [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined
Sailaja Mada created CLOUDSTACK-7498: Summary: [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined Key: CLOUDSTACK-7498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7498 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Install 4.5 cloudstack 2. Access Management Server UI and tried register ISO Observations : 1. It is not invoking Register ISO page and failing with ReferenceError: osTypeObjs is not defined Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7498) [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7498: - Attachment: registerisoUI.png [UI] Register ISO option is failing to invoke ISO registration page with ReferenceError: osTypeObjs is not defined -- Key: CLOUDSTACK-7498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Critical Attachments: registerisoUI.png Steps: 1. Install 4.5 cloudstack 2. Access Management Server UI and tried register ISO Observations : 1. It is not invoking Register ISO page and failing with ReferenceError: osTypeObjs is not defined Attached the screenshot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state with lo
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7222: - Summary: [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state with low memory (was: [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state with low memory -- Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Assignee: Saksham Srivastava Priority: Minor Fix For: 4.5.0 Attachments: apilog.log, management-server.log Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6453: - Fix Version/s: 4.5.0 [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers -- Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Sanjay Tripathi Priority: Critical Fix For: 4.4.0, 4.5.0 Attachments: SMlog, gpulogs.zip Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada reopened CLOUDSTACK-6453: -- Tried with latest master. Reported issue is not fixed. Hence reopening the bug. [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers -- Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Sanjay Tripathi Priority: Critical Fix For: 4.4.0, 4.5.0 Attachments: SMlog, gpulogs.zip Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7094) Update PV-tools in all the VMs in case of xenserver upgrade to avoid PV-tools error in VMs with VGPU support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7094: - Fix Version/s: 4.5.0 Update PV-tools in all the VMs in case of xenserver upgrade to avoid PV-tools error in VMs with VGPU support Key: CLOUDSTACK-7094 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7094 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.4.0 Reporter: Sanjay Tripathi Fix For: 4.5.0 If VM(say windows 7) with PV tools installed is running on XS host 6.0 or on previous versions and user wants to upgrade it to XS 620SP1. Steps to follow: a. Upgrade XenServer to 620SP1 b. Update the PV tools in all the VMs. c. Change service offering to have VGPU support. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada resolved CLOUDSTACK-6453. -- Resolution: Fixed Fix Version/s: (was: 4.5.0) Reopened wrong defect. [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers -- Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Assignee: Sanjay Tripathi Priority: Critical Fix For: 4.4.0 Attachments: SMlog, gpulogs.zip Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7222: - Fix Version/s: 4.5.0 [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state - Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.5.0 Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and getting stopped
Sailaja Mada created CLOUDSTACK-7222: Summary: [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and getting stopped Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7222: - Summary: [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state (was: [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and getting stopped) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state - Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.5.0 Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7222: - Attachment: management-server.log apilog.log [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state - Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.5.0 Attachments: apilog.log, management-server.log Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082200#comment-14082200 ] Sailaja Mada commented on CLOUDSTACK-7222: -- This is happening only when compute offering is defined with very less memory Ex: 200 MB. [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state - Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.5.0 Attachments: apilog.log, management-server.log Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7222) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-7222: - Priority: Minor (was: Blocker) [GPU] Windows 2012 Server instance created from Windows with PV drivers installed and using vGPU offering is going to repair state and moved to stopped state - Key: CLOUDSTACK-7222 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.5.0 Reporter: Sailaja Mada Priority: Minor Fix For: 4.5.0 Attachments: apilog.log, management-server.log Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using normal compute offering without GPU 4. Install Windows 2012 instance and install PV drivers 5. Stop the VM and create template from ROOT volume 6. Deploy windows 2012 instance using this template with vGPU K200 service offering 7. Windows instance got created using this card on XenServer. But got into repair state after sometime. 8. Later this VM got into stopped state. 9. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 10. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6692) Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state
Sailaja Mada created CLOUDSTACK-6692: Summary: Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state Key: CLOUDSTACK-6692 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6692 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Attachments: vgpulogs.zip Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template with non GPU offering 5. Stop the VM 6. Upgrade the service offering to GPU offering (K2 260) 7. Tried to start the VM. Start VM is completed . 8. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6661) deployvm failed with NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998617#comment-13998617
]
Sailaja Mada commented on CLOUDSTACK-6661:
--
This issue is reproducible consistently with Windows 2012 R2 64 bit instance.
2014-05-15 13:14:12,066 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-5:job-26/job-27 ctx-974ae1d9) Seq 1-3522377858557149379:
Sending { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:d75694b2-d7f4-48a2-8bfc-3aafd073c005,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:bd93a9ac-e84c-36db-b4fe-80d406208de5,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/vgpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/vgpups1/?ROLE=PrimarySTOREUUID=bd93a9ac-e84c-36db-b4fe-80d406208de5}},name:ROOT-6,size:21474836480,volumeId:6,vmName:i-3-6-VM,accountId:3,format:VHD,id:6,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-05-15 13:14:12,066 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-5:job-26/job-27 ctx-974ae1d9) Seq 1-3522377858557149379:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:d75694b2-d7f4-48a2-8bfc-3aafd073c005,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:bd93a9ac-e84c-36db-b4fe-80d406208de5,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/vgpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/vgpups1/?ROLE=PrimarySTOREUUID=bd93a9ac-e84c-36db-b4fe-80d406208de5}},name:ROOT-6,size:21474836480,volumeId:6,vmName:i-3-6-VM,accountId:3,format:VHD,id:6,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-05-15 13:14:12,067 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-17:ctx-94d64fbb) Seq 1-3522377858557149379: Executing request
2014-05-15 13:14:12,091 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-17:ctx-94d64fbb) SR retrieved for
bd93a9ac-e84c-36db-b4fe-80d406208de5
2014-05-15 13:14:12,098 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-17:ctx-94d64fbb) Checking bd93a9ac-e84c-36db-b4fe-80d406208de5 or
SR f60239ff-6b5e-c627-4bef-aaa0999ca70b on
XS[4861cedc-f7fc-40fc-a330-9b57be4cd387-10.102.192.10]
2014-05-15 13:14:12,906 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-17:ctx-94d64fbb) Seq 1-3522377858557149379: Response Received:
2014-05-15 13:14:12,907 DEBUG [c.c.a.t.Request] (DirectAgent-17:ctx-94d64fbb)
Seq 1-3522377858557149379: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CreateObjectAnswer:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{name:ROOT-6,size:21474836480,path:746b1abf-e304-49c6-813e-14b8058e8147,accountId:0,id:0}},result:true,wait:0}}]
}
2014-05-15 13:14:12,907 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-5:job-26/job-27 ctx-974ae1d9) Seq 1-3522377858557149379:
Received: { Ans: , MgmtId: 55355881446856, via: 1, Ver: v1, Flags: 10, {
CreateObjectAnswer } }
2014-05-15 13:14:12,975 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Work-Job-Executor-5:job-26/job-27 ctx-974ae1d9) template 204 is already in
store:1, type:Image
2014-05-15 13:14:12,990 ERROR [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-5:job-26/job-27 ctx-974ae1d9) Failed to start instance
VM[User|i-3-6-VM]
java.lang.NullPointerException
at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
[jira] [Updated] (CLOUDSTACK-6692) Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6692: - Attachment: vgpulogs.zip Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state Key: CLOUDSTACK-6692 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6692 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Attachments: vgpulogs.zip Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template with non GPU offering 5. Stop the VM 6. Upgrade the service offering to GPU offering (K2 260) 7. Tried to start the VM. Start VM is completed . 8. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6693) Enabling Dynamic scale is causing for Windows 8 instance to repair state
Sailaja Mada created CLOUDSTACK-6693: Summary: Enabling Dynamic scale is causing for Windows 8 instance to repair state Key: CLOUDSTACK-6693 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6693 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template. This has dynamic scaling option set to no 5. Enable Zone level Dynamic scale VM config parameter 6. Stop the VM 7. Edit VM details and Enable Dynamic scale VM option 8. Start the VM . Start VM is completed . 9. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Enabling Dynamic scale is causing for Windows 8 instance to repair state Notes: Later disabled Dynamic scale and started the VM. It started with no issues. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6684) Error instances are not getting expunged within the specified expunge interval
Sailaja Mada created CLOUDSTACK-6684:
Summary: Error instances are not getting expunged within the
specified expunge interval
Key: CLOUDSTACK-6684
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6684
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Attachments: expungelogs.zip
Steps:
1. Configure Adv zone using Xenserver 6.2.5
2. Deployed windows 2012 R2 and window 8 instances
3. Set the expunge interval to 10 seconds
3. Windows 2012 R2 instances failed to deploy due to another bug
https://issues.apache.org/jira/browse/CLOUDSTACK-6661
These failed instances are in Error state.
Expunge thread triggered to expunge instances. It identified the instances to
expunge but failed to do with Runtime exceptions,
2014-05-15 15:23:03,552 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Processing Seq 2-1697: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: [\n{\n \id\: 10,\n \clientInfo\: \\,\n
\host\: \10.102.192.10\,\n \port\: -1,\n \tag\:
\3884c408-9b63-4f04-ab63-4626e0cbd9af\,\n \createTime\:
1400166406368,\n \lastUsedTime\: 1400166620142\n}\n
]\n},wait:0}}] }
2014-05-15 15:23:03,556 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Sending Seq 2-1697: { Ans: ,
MgmtId: 55355881446856, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-15 15:23:06,528 INFO [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Found 2 vms to expunge.
2014-05-15 15:23:06,531 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-3-7-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-05-15 15:23:06,534 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-2-10-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
[jira] [Updated] (CLOUDSTACK-6693) Enabling Dynamic scale is causing for Windows 8 instance to repair state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6693: - Fix Version/s: 4.4.0 Enabling Dynamic scale is causing for Windows 8 instance to repair state - Key: CLOUDSTACK-6693 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6693 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template. This has dynamic scaling option set to no 5. Enable Zone level Dynamic scale VM config parameter 6. Stop the VM 7. Edit VM details and Enable Dynamic scale VM option 8. Start the VM . Start VM is completed . 9. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Enabling Dynamic scale is causing for Windows 8 instance to repair state Notes: Later disabled Dynamic scale and started the VM. It started with no issues. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6684) Error instances are not getting expunged within the specified expunge interval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6684:
-
Attachment: expungelogs.zip
Error instances are not getting expunged within the specified expunge interval
--
Key: CLOUDSTACK-6684
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6684
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Attachments: expungelogs.zip
Steps:
1. Configure Adv zone using Xenserver 6.2.5
2. Deployed windows 2012 R2 and window 8 instances
3. Set the expunge interval to 10 seconds
3. Windows 2012 R2 instances failed to deploy due to another bug
https://issues.apache.org/jira/browse/CLOUDSTACK-6661
These failed instances are in Error state.
Expunge thread triggered to expunge instances. It identified the instances
to expunge but failed to do with Runtime exceptions,
2014-05-15 15:23:03,552 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Processing Seq 2-1697: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: [\n{\n \id\: 10,\n \clientInfo\: \\,\n
\host\: \10.102.192.10\,\n \port\: -1,\n \tag\:
\3884c408-9b63-4f04-ab63-4626e0cbd9af\,\n \createTime\:
1400166406368,\n \lastUsedTime\: 1400166620142\n}\n
]\n},wait:0}}] }
2014-05-15 15:23:03,556 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Sending Seq 2-1697: { Ans: ,
MgmtId: 55355881446856, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-15 15:23:06,528 INFO [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Found 2 vms to expunge.
2014-05-15 15:23:06,531 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-3-7-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-05-15 15:23:06,534 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-2-10-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[jira] [Updated] (CLOUDSTACK-6692) Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6692: - Fix Version/s: 4.4.0 Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state Key: CLOUDSTACK-6692 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6692 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Attachments: vgpulogs.zip Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template with non GPU offering 5. Stop the VM 6. Upgrade the service offering to GPU offering (K2 260) 7. Tried to start the VM. Start VM is completed . 8. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6684) Error instances are not getting expunged within the specified expunge interval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6684:
-
Fix Version/s: 4.4.0
Error instances are not getting expunged within the specified expunge interval
--
Key: CLOUDSTACK-6684
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6684
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Attachments: expungelogs.zip
Steps:
1. Configure Adv zone using Xenserver 6.2.5
2. Deployed windows 2012 R2 and window 8 instances
3. Set the expunge interval to 10 seconds
3. Windows 2012 R2 instances failed to deploy due to another bug
https://issues.apache.org/jira/browse/CLOUDSTACK-6661
These failed instances are in Error state.
Expunge thread triggered to expunge instances. It identified the instances
to expunge but failed to do with Runtime exceptions,
2014-05-15 15:23:03,552 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Processing Seq 2-1697: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: [\n{\n \id\: 10,\n \clientInfo\: \\,\n
\host\: \10.102.192.10\,\n \port\: -1,\n \tag\:
\3884c408-9b63-4f04-ab63-4626e0cbd9af\,\n \createTime\:
1400166406368,\n \lastUsedTime\: 1400166620142\n}\n
]\n},wait:0}}] }
2014-05-15 15:23:03,556 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 2-1697: Sending Seq 2-1697: { Ans: ,
MgmtId: 55355881446856, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-05-15 15:23:06,528 INFO [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Found 2 vms to expunge.
2014-05-15 15:23:06,531 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-3-7-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-05-15 15:23:06,534 WARN [c.c.v.UserVmManagerImpl]
(UserVm-Scavenger-1:ctx-8a506c20) Unable to expunge VM[User|i-2-10-VM]
com.cloud.utils.exception.CloudRuntimeException: Please destroy vm with
specified vmId before expunge
at
com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3620)
at
com.cloud.vm.UserVmManagerImpl$ExpungeTask.runInContext(UserVmManagerImpl.java:1801)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[jira] [Updated] (CLOUDSTACK-6693) Enabling Dynamic scale is causing for Windows 8 instance to repair state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6693: - Attachment: vgpulogs.zip Enabling Dynamic scale is causing for Windows 8 instance to repair state - Key: CLOUDSTACK-6693 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6693 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Attachments: vgpulogs.zip Steps: 1. Configure Adv zone with Xen 6.2.5 2. Deploy windows 8 VM . 3. Install PV drivers . Stop the VM and create template from ROOT volume 4. Deploy windows 8 instance using this template. This has dynamic scaling option set to no 5. Enable Zone level Dynamic scale VM config parameter 6. Stop the VM 7. Edit VM details and Enable Dynamic scale VM option 8. Start the VM . Start VM is completed . 9. View Console of this VM - Noticed that its moved to Automatic Repair state and VM moved to stopped state later from XS and then from Cloudstack Observation: Enabling Dynamic scale is causing for Windows 8 instance to repair state Notes: Later disabled Dynamic scale and started the VM. It started with no issues. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
Sailaja Mada created CLOUDSTACK-6575:
Summary: Deploy VM failed with NPE while using custom compute
offering
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd] (catalina-exec-19:ctx-b904a14a
ctx-e989ce28) Ignoring paremeter displayvm as the caller is not authorized to
pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd] (catalina-exec-19:ctx-b904a14a
ctx-e989ce28) Ignoring paremeter deploymentplanner as the caller is not
authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd] (catalina-exec-19:ctx-b904a14a
ctx-e989ce28) Ignoring paremeter displayvm as the caller is not authorized to
pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd] (catalina-exec-19:ctx-b904a14a
ctx-e989ce28) Ignoring paremeter deploymentplanner as the caller is not
authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer] (catalina-exec-19:ctx-b904a14a
ctx-e989ce28) unhandled exception executing api command:
[Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167)
at
com.cloud.service.dao.ServiceOfferingDaoImpl.getcomputeOffering(ServiceOfferingDaoImpl.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Updated] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6575:
-
Fix Version/s: 4.4.0
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) unhandled exception executing
api command: [Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167)
at
com.cloud.service.dao.ServiceOfferingDaoImpl.getcomputeOffering(ServiceOfferingDaoImpl.java:227)
[jira] [Updated] (CLOUDSTACK-6575) Deploy VM failed with NPE while using custom compute offering
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6575:
-
Attachment: logs.zip
Deploy VM failed with NPE while using custom compute offering
--
Key: CLOUDSTACK-6575
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6575
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Critical
Fix For: 4.4.0
Attachments: logs.zip
Steps:
1. Install and configure Adv zone using Xen 6.2.5 Hypervisor
2. Create Compute offering with Custom option enabled
3. Deploy VM using Default Cent OS template using Customer option enabled
Compute offering with CPU=1, Memory=2000 , Speed = 500
Observation:
Deploy VM failed with NPE while using custom compute offering
API call:
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,233 DEBUG [c.c.a.ApiServlet]
(catalina-exec-19:ctx-b904a14a) ===START=== 10.144.6.6 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=TDXLIOmV8uKaEsb9Mr5o96exjw0%3Dzoneid=764d3b82-5f1f-450c-a337-6b1398c472b3templateid=68e3978c-d1d8-11e3-9149-32588ba65dc8hypervisor=XenServerserviceofferingid=d04e17be-e99d-427a-95bf-ed0cbc82520ddetails%5B0%5D.cpuNumber=1details%5B0%5D.cpuSpeed=500details%5B0%5D.memory=2000diskofferingid=ac9d944f-6b66-4822-bd97-bde18573caaeiptonetworklist%5B0%5D.networkid=91973ed0-97f6-47bf-94ea-25751da81ae9displayname=newcent1name=newcent1_=1399286122706
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,247 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to service offering:13 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,255 DEBUG [c.c.a.d.ParamProcessWorker]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] to disk offering:4 by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Tmpl[5-VHD-centos56-x86_64-xen} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter displayvm as
the caller is not authorized to pass it in
2014-05-05 16:04:23,295 DEBUG [o.a.c.a.BaseCmd]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Ignoring paremeter
deploymentplanner as the caller is not authorized to pass it in
2014-05-05 16:04:23,335 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,373 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Ntwk[91973ed0-97f6-47bf-94ea-25751da81ae9|Guest|8]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,412 DEBUG [c.c.u.AccountManagerImpl]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) Access to
{Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1]} granted to
Acct[e412bd9a-f443-413d-941f-a2fdf1af6cf3-cdcuser1] by
RoleBasedEntityAccessChecker
2014-05-05 16:04:23,437 ERROR [c.c.a.ApiServer]
(catalina-exec-19:ctx-b904a14a ctx-e989ce28) unhandled exception executing
api command: [Ljava.lang.String;@763f4779
java.lang.NullPointerException
at
com.cloud.service.ServiceOfferingVO.init(ServiceOfferingVO.java:167)
at
[jira] [Updated] (CLOUDSTACK-6576) No Error Handling while deploying GPU unsupported instances on a GPU enabled host (Ex: Cent OS instance)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6576:
-
Fix Version/s: 4.4.0
No Error Handling while deploying GPU unsupported instances on a GPU enabled
host (Ex: Cent OS instance)
Key: CLOUDSTACK-6576
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6576
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Minor
Fix For: 4.4.0
Steps:
1. Install and configure Adv zone with GPU enabled XenServer 6.2.5
2. Try to deploy default Cent OS instance using GPU enabled offering( K2 -
200 profile)
Observation:
1. Xenserver does not support vGPU with Linux instances.
2. Cloudstack throws deployment failure after throwing lot of exceptions by
XenServer.
Expected Results:
CloudStack should parse the failure provided by XS and provide proper
deployment failure as unsupported deployment.
2014-05-05 16:38:50,730 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Sending { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:1439f05b06e154d2,params:{},uuid:00069b3f-abf0-4f0d-a12c-6ae9d1a3ea81,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:e92dcd30-3775-4762-bb83-b6c9d901644b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e8ccf63a-577b-3378-9741-16ce76631992,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/goletagpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/goletagpups1/?ROLE=PrimarySTOREUUID=e8ccf63a-577b-3378-9741-16ce76631992}},name:ROOT-9,size:21474836480,path:8d273d72-877c-4776-b4b5-9e52072ea45f,volumeId:11,vmName:i-3-9-VM,accountId:3,format:VHD,id:11,deviceId:0,hypervisorType:XenServer}},diskSeq:0,path:8d273d72-877c-4776-b4b5-9e52072ea45f,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.102.192.101,volumeSize:21474836480}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:91973ed0-97f6-47bf-94ea-25751da81ae9,ip:10.1.1.220,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:03:4b:00:07,dns1:10.140.50.5,broadcastType:Vlan,type:Guest,broadcastUri:vlan://770,isolationUri:vlan://770,isSecurityGroupEnabled:false}],gpuDevice:{gpuGroup:Group
of NVIDIA Corporation GK104GL [GRID K2] GPUs,vgpuType:GRID
K200}},hostIp:10.102.192.66,executeInSequence:false,wait:0}}] }
2014-05-05 16:38:50,732 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
[jira] [Created] (CLOUDSTACK-6576) No Error Handling while deploying GPU unsupported instances on a GPU enabled host (Ex: Cent OS instance)
Sailaja Mada created CLOUDSTACK-6576:
Summary: No Error Handling while deploying GPU unsupported
instances on a GPU enabled host (Ex: Cent OS instance)
Key: CLOUDSTACK-6576
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6576
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Minor
Steps:
1. Install and configure Adv zone with GPU enabled XenServer 6.2.5
2. Try to deploy default Cent OS instance using GPU enabled offering( K2 - 200
profile)
Observation:
1. Xenserver does not support vGPU with Linux instances.
2. Cloudstack throws deployment failure after throwing lot of exceptions by
XenServer.
Expected Results:
CloudStack should parse the failure provided by XS and provide proper
deployment failure as unsupported deployment.
2014-05-05 16:38:50,730 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Sending { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:1439f05b06e154d2,params:{},uuid:00069b3f-abf0-4f0d-a12c-6ae9d1a3ea81,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:e92dcd30-3775-4762-bb83-b6c9d901644b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e8ccf63a-577b-3378-9741-16ce76631992,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/goletagpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/goletagpups1/?ROLE=PrimarySTOREUUID=e8ccf63a-577b-3378-9741-16ce76631992}},name:ROOT-9,size:21474836480,path:8d273d72-877c-4776-b4b5-9e52072ea45f,volumeId:11,vmName:i-3-9-VM,accountId:3,format:VHD,id:11,deviceId:0,hypervisorType:XenServer}},diskSeq:0,path:8d273d72-877c-4776-b4b5-9e52072ea45f,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.102.192.101,volumeSize:21474836480}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:91973ed0-97f6-47bf-94ea-25751da81ae9,ip:10.1.1.220,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:03:4b:00:07,dns1:10.140.50.5,broadcastType:Vlan,type:Guest,broadcastUri:vlan://770,isolationUri:vlan://770,isSecurityGroupEnabled:false}],gpuDevice:{gpuGroup:Group
of NVIDIA Corporation GK104GL [GRID K2] GPUs,vgpuType:GRID
K200}},hostIp:10.102.192.66,executeInSequence:false,wait:0}}] }
2014-05-05 16:38:50,732 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:1439f05b06e154d2,params:{},uuid:00069b3f-abf0-4f0d-a12c-6ae9d1a3ea81,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:e92dcd30-3775-4762-bb83-b6c9d901644b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e8ccf63a-577b-3378-9741-16ce76631992,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/goletagpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/goletagpups1/?ROLE=PrimarySTOREUUID=e8ccf63a-577b-3378-9741-16ce76631992}},name:ROOT-9,size:21474836480,path:8d273d72-877c-4776-b4b5-9e52072ea45f,volumeId:11,vmName:i-3-9-VM,accountId:3,format:VHD,id:11,deviceId:0,hypervisorType:XenServer}},diskSeq:0,path:8d273d72-877c-4776-b4b5-9e52072ea45f,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.102.192.101,volumeSize:21474836480}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:91973ed0-97f6-47bf-94ea-25751da81ae9,ip:10.1.1.220,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:03:4b:00:07,dns1:10.140.50.5,broadcastType:Vlan,type:Guest,broadcastUri:vlan://770,isolationUri:vlan://770,isSecurityGroupEnabled:false}],gpuDevice:{gpuGroup:Group
of NVIDIA Corporation GK104GL [GRID K2] GPUs,vgpuType:GRID
K200}},hostIp:10.102.192.66,executeInSequence:false,wait:0}}] }
2014-05-05 16:38:50,732 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-296:ctx-251a7963) Seq
[jira] [Updated] (CLOUDSTACK-6576) No Error Handling while deploying GPU unsupported instances on a GPU enabled host (Ex: Cent OS instance)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6576:
-
Attachment: logs1.zip
No Error Handling while deploying GPU unsupported instances on a GPU enabled
host (Ex: Cent OS instance)
Key: CLOUDSTACK-6576
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6576
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Minor
Fix For: 4.4.0
Attachments: logs1.zip
Steps:
1. Install and configure Adv zone with GPU enabled XenServer 6.2.5
2. Try to deploy default Cent OS instance using GPU enabled offering( K2 -
200 profile)
Observation:
1. Xenserver does not support vGPU with Linux instances.
2. Cloudstack throws deployment failure after throwing lot of exceptions by
XenServer.
Expected Results:
CloudStack should parse the failure provided by XS and provide proper
deployment failure as unsupported deployment.
2014-05-05 16:38:50,730 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Sending { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:1439f05b06e154d2,params:{},uuid:00069b3f-abf0-4f0d-a12c-6ae9d1a3ea81,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:e92dcd30-3775-4762-bb83-b6c9d901644b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e8ccf63a-577b-3378-9741-16ce76631992,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/goletagpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/goletagpups1/?ROLE=PrimarySTOREUUID=e8ccf63a-577b-3378-9741-16ce76631992}},name:ROOT-9,size:21474836480,path:8d273d72-877c-4776-b4b5-9e52072ea45f,volumeId:11,vmName:i-3-9-VM,accountId:3,format:VHD,id:11,deviceId:0,hypervisorType:XenServer}},diskSeq:0,path:8d273d72-877c-4776-b4b5-9e52072ea45f,type:ROOT,_details:{managed:false,storagePort:2049,storageHost:10.102.192.101,volumeSize:21474836480}},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId:0,networkRateMbps:200,defaultNic:true,uuid:91973ed0-97f6-47bf-94ea-25751da81ae9,ip:10.1.1.220,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:03:4b:00:07,dns1:10.140.50.5,broadcastType:Vlan,type:Guest,broadcastUri:vlan://770,isolationUri:vlan://770,isSecurityGroupEnabled:false}],gpuDevice:{gpuGroup:Group
of NVIDIA Corporation GK104GL [GRID K2] GPUs,vgpuType:GRID
K200}},hostIp:10.102.192.66,executeInSequence:false,wait:0}}] }
2014-05-05 16:38:50,732 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-18:job-58/job-59 ctx-4a14e747) Seq 1-7036029992836286502:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:9,name:i-3-9-VM,bootloader:PyGrub,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:CentOS
5.6
[jira] [Created] (CLOUDSTACK-6452) Failed to Live Migrate VM across clusters with Xenserver 6.2.5
Sailaja Mada created CLOUDSTACK-6452: Summary: Failed to Live Migrate VM across clusters with Xenserver 6.2.5 Key: CLOUDSTACK-6452 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6452 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Install and configure Adv zone using Xen 6.2.5 hypervisor with 2 clusters having 1 host in each cluster 2. deploy Windows 2012 instance 3. Live Migrate instance from cluster1 host to cluster2 Observation: Failed to Live Migrate VM across clusters with Xenserver 6.2.5 Job failed due to exception Failed to migrated vm VM[User|i-3-21-VM] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|i-3-21-VM] to host Host[-4-Routing]. Exception: com.cloud.utils.exception.CloudRuntimeException Message: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO Stack: com.cloud.utils.exception.CloudRuntimeException: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:123) at com.cloud.hypervisor.xen.resource.XenServer610Resource.execute(XenServer610Resource.java:357) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:88) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:113) ... 16 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6452) Failed to Live Migrate VM across clusters with Xenserver 6.2.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6452: - Fix Version/s: 4.4.0 Failed to Live Migrate VM across clusters with Xenserver 6.2.5 -- Key: CLOUDSTACK-6452 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6452 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Steps: 1. Install and configure Adv zone using Xen 6.2.5 hypervisor with 2 clusters having 1 host in each cluster 2. deploy Windows 2012 instance 3. Live Migrate instance from cluster1 host to cluster2 Observation: Failed to Live Migrate VM across clusters with Xenserver 6.2.5 Job failed due to exception Failed to migrated vm VM[User|i-3-21-VM] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|i-3-21-VM] to host Host[-4-Routing]. Exception: com.cloud.utils.exception.CloudRuntimeException Message: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO Stack: com.cloud.utils.exception.CloudRuntimeException: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:123) at com.cloud.hypervisor.xen.resource.XenServer610Resource.execute(XenServer610Resource.java:357) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:88) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:113) ... 16 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6452) Failed to Live Migrate VM across clusters with Xenserver 6.2.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6452: - Attachment: migrationlogs.rar Failed to Live Migrate VM across clusters with Xenserver 6.2.5 -- Key: CLOUDSTACK-6452 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6452 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Critical Fix For: 4.4.0 Attachments: migrationlogs.rar Steps: 1. Install and configure Adv zone using Xen 6.2.5 hypervisor with 2 clusters having 1 host in each cluster 2. deploy Windows 2012 instance 3. Live Migrate instance from cluster1 host to cluster2 Observation: Failed to Live Migrate VM across clusters with Xenserver 6.2.5 Job failed due to exception Failed to migrated vm VM[User|i-3-21-VM] along with its volumes. com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm VM[User|i-3-21-VM] to host Host[-4-Routing]. Exception: com.cloud.utils.exception.CloudRuntimeException Message: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO Stack: com.cloud.utils.exception.CloudRuntimeException: Unable to get the updated VDI paths of the migrated vm java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:123) at com.cloud.hypervisor.xen.resource.XenServer610Resource.execute(XenServer610Resource.java:357) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:88) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO at com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:113) ... 16 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6452) Failed to Live Migrate VM across clusters with Xenserver 6.2.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13973997#comment-13973997
]
Sailaja Mada commented on CLOUDSTACK-6452:
--
2014-04-18 16:46:06,148 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-38:job-191/job-192) Unable to complete AsyncJobVO {id:192,
userId: 2, accountId: 2, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkMigrate, cmdInfo:
rO0ABXNyACVjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZVdpdGhTdG9yYWdlsew9z6UxtXMCAANKAApkZXN0SG9zdElkSgAJc3JjSG9zdElkTAAMdm9sdW1lVG9Qb29sdAAPTGphdmEvdXRpbC9NYXA7eHIAE2NvbS5jbG91ZC52bS5WbVdvcmufmbZW8CVnawIABEoACWFjY291bnRJZEoABnVzZXJJZEoABHZtSWRMAAtoYW5kbGVyTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO3hwAAIAAgAVdAAZVmlydHVhbE1hY2hpbmVNYW5hZ2VySW1wbAAEAAFzcgARamF2YS51dGlsLkhhc2hNYXAFB9rBwxZg0QMAAkYACmxvYWRGYWN0b3JJAAl0aHJlc2hvbGR4cD9QdwgQAHg,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 55355881446856, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Fri Apr 18 16:17:44 IST 2014}, job origin:191
com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm
VM[User|i-3-21-VM] along with its volumes.
com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm
VM[User|i-3-21-VM] to host Host[-4-Routing]. Exception:
com.cloud.utils.exception.CloudRuntimeException
Message: Unable to get the updated VDI paths of the migrated vm
java.lang.ClassCastException: org.apache.cloudstack.storage.to.TemplateObjectTO
cannot be cast to org.apache.cloudstack.storage.to.VolumeObjectTO
Stack: com.cloud.utils.exception.CloudRuntimeException: Unable to get the
updated VDI paths of the migrated vm java.lang.ClassCastException:
org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to
org.apache.cloudstack.storage.to.VolumeObjectTO
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:123)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.execute(XenServer610Resource.java:357)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:88)
at
com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.ClassCastException:
org.apache.cloudstack.storage.to.TemplateObjectTO cannot be cast to
org.apache.cloudstack.storage.to.VolumeObjectTO
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.getUpdatedVolumePathsOfMigratedVm(XenServer610Resource.java:113)
... 16 more
at
org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.migrateVolumes(VolumeOrchestrator.java:941)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrateWithStorage(VirtualMachineManagerImpl.java:2138)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrateWithStorage(VirtualMachineManagerImpl.java:5213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5309)
at
[jira] [Commented] (CLOUDSTACK-6452) Failed to Live Migrate VM across clusters with Xenserver 6.2.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13974004#comment-13974004
]
Sailaja Mada commented on CLOUDSTACK-6452:
--
VM is not getting started after migration failure:
lags: 10, { Answer } }
2014-04-18 17:34:53,029 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Work-Job-Executor-40:job-193/job-195 ctx-5f835fbc) Volume 27 is not found on
image store 1, so no need to delete
2014-04-18 17:34:53,033 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Work-Job-Executor-40:job-193/job-195 ctx-5f835fbc) Unsupported data object
(VOLUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7a329b),
no need to delete from object in store ref table
2014-04-18 17:34:53,038 WARN [o.a.c.s.d.ObjectInDataStoreManagerImpl]
(Work-Job-Executor-40:job-193/job-195 ctx-5f835fbc) Unsupported data object
(VOLUME, org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@649dc40),
no need to delete from object in store ref table
2014-04-18 17:34:53,092 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-40:job-193/job-195 ctx-5f835fbc) Seq 4-3512807709348993546:
Sending { Cmd , MgmtId: 55355881446856, via: 4(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DeleteCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:640dc9fb-3ec5-4ca6-9750-7046f3e5b50f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cae1ed4a-6d0d-3f91-9986-73c0a5240b25,id:2,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpunewss1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpunewss1/?ROLE=PrimarySTOREUUID=cae1ed4a-6d0d-3f91-9986-73c0a5240b25}},name:ROOT-21,size:21474836480,path:a596f936-c701-49ad-8bb4-f31b45454ee5,volumeId:28,vmName:i-3-21-VM,accountId:3,format:VHD,id:28,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-04-18 17:34:53,092 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-40:job-193/job-195 ctx-5f835fbc) Seq 4-3512807709348993546:
Executing: { Cmd , MgmtId: 55355881446856, via: 4(cldstk-R720-66), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DeleteCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:640dc9fb-3ec5-4ca6-9750-7046f3e5b50f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:cae1ed4a-6d0d-3f91-9986-73c0a5240b25,id:2,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpunewss1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpunewss1/?ROLE=PrimarySTOREUUID=cae1ed4a-6d0d-3f91-9986-73c0a5240b25}},name:ROOT-21,size:21474836480,path:a596f936-c701-49ad-8bb4-f31b45454ee5,volumeId:28,vmName:i-3-21-VM,accountId:3,format:VHD,id:28,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-04-18 17:34:53,093 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-498:ctx-05f1b882) Seq 4-3512807709348993546: Executing request
2014-04-18 17:34:53,106 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-498:ctx-05f1b882) Failed to delete volume
The uuid you supplied was invalid.
at com.xensource.xenapi.Types.checkResponse(Types.java:1482)
at com.xensource.xenapi.Connection.dispatch(Connection.java:350)
at
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:456)
at com.xensource.xenapi.VDI.getByUuid(VDI.java:326)
at
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.deleteVolume(XenServerStorageProcessor.java:505)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:123)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:56)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
at
com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:64)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
[jira] [Created] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
Sailaja Mada created CLOUDSTACK-6453: Summary: [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Blocker Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6453: - Fix Version/s: 4.4.0 [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers -- Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.4.0 Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6453) [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6453: - Attachment: SMlog gpulogs.zip [GPU] Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers -- Key: CLOUDSTACK-6453 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6453 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Blocker Fix For: 4.4.0 Attachments: SMlog, gpulogs.zip Steps: 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2 2. Create Service Offering using K2 - K200 profile of vGPU 3. Deploy windows 2012 instance with ISO using K200 vGPU profile offering 4. Install Windows 2012 instance and install PV drivers 5. During PV driver installation Windows 2012 server went for reboot. Observation: 1. After reboot, Windows 2012 Server instance created with vGPU offering is not coming up after installing PV drivers 2. It remained in stopped state. 3. Tried to start instance manually , Cloudstack says Instance started and instance moved to running state. But XenServer failed to start the instance. 4. Later Cloudstack also marked the instance in stopped state. Attached detailed logs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6412) [UI]Incorrect Field value added with host details page(Dedicated label.no)
Sailaja Mada created CLOUDSTACK-6412: Summary: [UI]Incorrect Field value added with host details page(Dedicated label.no) Key: CLOUDSTACK-6412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6412 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Minor Attachments: dedicatedincorrectlabel.png Setup: ACS 4.4 with XenServer 6.2.5 Steps: 1. Install and configure Adv zone using Xenserver 6.2.5 2. Go to Host Details page Observation: Incorrect Field value added with host details page(Dedicatedlabel.no) (Attached the snapshot) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6412) [UI]Incorrect Field value added with host details page(Dedicated label.no)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6412: - Fix Version/s: 4.4.0 [UI]Incorrect Field value added with host details page(Dedicated label.no) -- Key: CLOUDSTACK-6412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6412 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Minor Fix For: 4.4.0 Attachments: dedicatedincorrectlabel.png Setup: ACS 4.4 with XenServer 6.2.5 Steps: 1. Install and configure Adv zone using Xenserver 6.2.5 2. Go to Host Details page Observation: Incorrect Field value added with host details page(Dedicated label.no) (Attached the snapshot) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6412) [UI]Incorrect Field value added with host details page(Dedicated label.no)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6412: - Attachment: dedicatedincorrectlabel.png [UI]Incorrect Field value added with host details page(Dedicated label.no) -- Key: CLOUDSTACK-6412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6412 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Minor Fix For: 4.4.0 Attachments: dedicatedincorrectlabel.png Setup: ACS 4.4 with XenServer 6.2.5 Steps: 1. Install and configure Adv zone using Xenserver 6.2.5 2. Go to Host Details page Observation: Incorrect Field value added with host details page(Dedicated label.no) (Attached the snapshot) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6414) [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6414: - Fix Version/s: 4.4.0 [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Key: CLOUDSTACK-6414 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6414 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Fix For: 4.4.0 Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Attached Firebug snap. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6414) [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined)
Sailaja Mada created CLOUDSTACK-6414: Summary: [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Key: CLOUDSTACK-6414 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6414 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Attached Firebug snap. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6414) [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6414: - Description: Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) createAccount API call works to create Domain Admin User. It is the failure only in the UI. Attached Firebug snap. was: Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Attached Firebug snap. [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Key: CLOUDSTACK-6414 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6414 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Fix For: 4.4.0 Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) createAccount API call works to create Domain Admin User. It is the failure only in the UI. Attached Firebug snap. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6414) [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6414: - Attachment: FailedtoaddDomainAdminUI.png [UI] UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) Key: CLOUDSTACK-6414 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6414 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Fix For: 4.4.0 Attachments: FailedtoaddDomainAdminUI.png Steps: 1. Install and configure Adv Zone using XenServer 6.2.5 2. Create domain CDC under root domain 3. Tried to create Domain Admin user under CDC domain from ACS Management Console as root admin user. Observation: UI is not allowing to create DomainAdmin User (ReferenceError: rootDomainId is not defined) createAccount API call works to create Domain Admin User. It is the failure only in the UI. Attached Firebug snap. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6405) Observed SQL exceptions during db upgrade from 4.0.0 to 4.4.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969193#comment-13969193 ] Sailaja Mada commented on CLOUDSTACK-6405: -- This issue is same as : (CLOUDSTACK-6386) DB Exceptions while starting the Management server first time Observed SQL exceptions during db upgrade from 4.0.0 to 4.4.0 - Key: CLOUDSTACK-6405 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6405 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Latest build from 4.4 with commit 098324aa84d3835d2eca24d41f0266128d2d4f29 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 Attachments: catalina.rar, management-server.rar Observed SQL Exceptions during db upgrade from 4.0.0 to 4.4.0 Steps to Reproduce: 1.Install MS with latest build from 4.4 2.Observe log file after cloudstack-setup-management During MS start we upgrade DB from 4.0.0 to latest version which is 4.4.0 Found some SQL exceptions during this db upgrade. Following is one of them: INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) at com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) at com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6407) NPE while collecting VM statistics
Sailaja Mada created CLOUDSTACK-6407:
Summary: NPE while collecting VM statistics
Key: CLOUDSTACK-6407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6407
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Setup : 4.4 with XenServer 6.2.5
1. Install and configure Adv zone using XenServer 6.2.5
2. Deployed 2 Windows (8 and 2012) VM's using Domain user account .
Observed NPE's while collecting VM statistics in the Management server
log(Attached)
2014-04-15 00:00:49,574 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-2e085056) VmStatsCollector is running...
2014-04-15 00:00:49,588 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Executing request
2014-04-15 00:00:49,618 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Exception Caught while
executing command
java.lang.NullPointerException
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Response Received:
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (DirectAgent-69:ctx-9a19b721)
Seq 1-6476457739135503930: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException,wait:0}}]
}
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (StatsCollector-4:ctx-2e085056)
Seq 1-6476457739135503930: Received: { Ans: , MgmtId: 55355881446856, via: 1,
Ver: v1, Flags: 10, { Answer } }
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.AgentManagerImpl]
(StatsCollector-4:ctx-2e085056) Details from executing class
com.cloud.agent.api.GetVmStatsCommand: java.lang.NullPointerException
2014-04-15 00:00:49,619 WARN [c.c.v.UserVmManagerImpl]
(StatsCollector-4:ctx-2e085056) Unable to obtain VM statistics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6407) NPE while collecting VM statistics
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6407:
-
Attachment: management-server.log
NPE while collecting VM statistics
---
Key: CLOUDSTACK-6407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6407
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Fix For: 4.4.0
Attachments: management-server.log
Setup : 4.4 with XenServer 6.2.5
1. Install and configure Adv zone using XenServer 6.2.5
2. Deployed 2 Windows (8 and 2012) VM's using Domain user account .
Observed NPE's while collecting VM statistics in the Management server
log(Attached)
2014-04-15 00:00:49,574 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-2e085056) VmStatsCollector is running...
2014-04-15 00:00:49,588 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Executing request
2014-04-15 00:00:49,618 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Exception Caught
while executing command
java.lang.NullPointerException
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Response Received:
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (DirectAgent-69:ctx-9a19b721)
Seq 1-6476457739135503930: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException,wait:0}}]
}
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request]
(StatsCollector-4:ctx-2e085056) Seq 1-6476457739135503930: Received: { Ans:
, MgmtId: 55355881446856, via: 1, Ver: v1, Flags: 10, { Answer } }
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.AgentManagerImpl]
(StatsCollector-4:ctx-2e085056) Details from executing class
com.cloud.agent.api.GetVmStatsCommand: java.lang.NullPointerException
2014-04-15 00:00:49,619 WARN [c.c.v.UserVmManagerImpl]
(StatsCollector-4:ctx-2e085056) Unable to obtain VM statistics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
