[jira] [Resolved] (CLOUDSTACK-7170) [Automation] Failed to add KVM agent with master

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-7170.
---

Resolution: Fixed

 [Automation] Failed to add KVM agent with  master 
 --

 Key: CLOUDSTACK-7170
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7170
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: KVM - RHEL 6.3
 Master
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: July_23_KVM.rar


 This issue observed in automation setup, failed add KVM agent 
 Might be regressed after 
 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=173909e99d85cfcc85b017bc426950f9f16fddf0
 MS log
 ---
 2014-07-23 00:49:18,307 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Unable to find the 
 server resources at http://10.223.50.66
 2014-07-23 00:49:18,310 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Could not find 
 exception: com.cloud.exception.DiscoveryException in error code list for 
 exceptions
 2014-07-23 00:49:18,310 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:790)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:585)
 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 
 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.$Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 

[jira] [Commented] (CLOUDSTACK-7170) [Automation] Failed to add KVM agent with master

2014-07-24 Thread Kishan Kavala (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072918#comment-14072918
 ] 

Kishan Kavala commented on CLOUDSTACK-7170:
---

Commit c804660c74f08008be4f71607681c83d31f3cc55 reverted 
4523490d44160b054de9e943f72db1d0ce06054a which caused this issue.


 [Automation] Failed to add KVM agent with  master 
 --

 Key: CLOUDSTACK-7170
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7170
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
 Environment: KVM - RHEL 6.3
 Master
Reporter: Rayees Namathponnan
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: July_23_KVM.rar


 This issue observed in automation setup, failed add KVM agent 
 Might be regressed after 
 https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=173909e99d85cfcc85b017bc426950f9f16fddf0
 MS log
 ---
 2014-07-23 00:49:18,307 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Unable to find the 
 server resources at http://10.223.50.66
 2014-07-23 00:49:18,310 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Could not find 
 exception: com.cloud.exception.DiscoveryException in error code list for 
 exceptions
 2014-07-23 00:49:18,310 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-8:ctx-9df22e36 ctx-c5a4207e ctx-3d7179b3) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:790)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:585)
 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 
 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.$Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 

[jira] [Commented] (CLOUDSTACK-7141) UI :Support RBD primary storage pool type for LXC

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072921#comment-14072921
 ] 

ASF subversion and git services commented on CLOUDSTACK-7141:
-

Commit 6d1d445542e5df495585bdde91dd1b92f685c7a7 in cloudstack's branch 
refs/heads/master from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d1d445 ]

CLOUDSTACK-7141: UI: support RBD pool type for LXC


 UI :Support RBD primary storage pool type for LXC
 -

 Key: CLOUDSTACK-7141
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7141
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.5.0


 LXC supports RBD storage pools. Required changes are completed on the 
 backend. UI needs to list RBD pool type while adding primary storage



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7141) UI :Support RBD primary storage pool type for LXC

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-7141.
---

Resolution: Fixed

 UI :Support RBD primary storage pool type for LXC
 -

 Key: CLOUDSTACK-7141
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7141
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.5.0


 LXC supports RBD storage pools. Required changes are completed on the 
 backend. UI needs to list RBD pool type while adding primary storage



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7097) failing to add kvm host to MS

2014-07-24 Thread Kishan Kavala (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072924#comment-14072924
 ] 

Kishan Kavala commented on CLOUDSTACK-7097:
---

Agent requires java7. Unsupported major minor exception is seen when lower 
version of java is installed.

 failing to add  kvm host to MS
 --

 Key: CLOUDSTACK-7097
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7097
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: management-server.log.tar.gz


 Repro steps:
 Create a agent on rhel 6.3
 create a MS on rhel 6.3
 Try creating a zone
 Bug : zone creation fails at adding host step
 MS log shows :
 014-07-11 03:33:46,284 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Received unknown parameters for 
 command addHost. Unknown parameters : clustertype
 2014-07-11 03:33:46,294 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Trying to add a new host at 
 http://10.147.40.24 in data center 1
 2014-07-11 03:33:46,487 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:47,505 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:48,556 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:49,607 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) It's not a KVM enabled machine
 2014-07-11 03:33:49,608 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Unable to find the server 
 resources at http://10.147.40.24
 2014-07-11 03:33:49,611 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-11 03:33:49,611 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 

[jira] [Resolved] (CLOUDSTACK-7097) failing to add kvm host to MS

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-7097.
---

Resolution: Not a Problem

 failing to add  kvm host to MS
 --

 Key: CLOUDSTACK-7097
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7097
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: management-server.log.tar.gz


 Repro steps:
 Create a agent on rhel 6.3
 create a MS on rhel 6.3
 Try creating a zone
 Bug : zone creation fails at adding host step
 MS log shows :
 014-07-11 03:33:46,284 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Received unknown parameters for 
 command addHost. Unknown parameters : clustertype
 2014-07-11 03:33:46,294 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Trying to add a new host at 
 http://10.147.40.24 in data center 1
 2014-07-11 03:33:46,487 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:47,505 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:48,556 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:49,607 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) It's not a KVM enabled machine
 2014-07-11 03:33:49,608 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Unable to find the server 
 resources at http://10.147.40.24
 2014-07-11 03:33:49,611 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-11 03:33:49,611 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 

[jira] [Issue Comment Deleted] (CLOUDSTACK-7097) failing to add kvm host to MS

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala updated CLOUDSTACK-7097:
--

Comment: was deleted

(was: Agent requires java7. Unsupported major minor exception is seen when 
lower version of java is installed.)

 failing to add  kvm host to MS
 --

 Key: CLOUDSTACK-7097
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7097
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: management-server.log.tar.gz


 Repro steps:
 Create a agent on rhel 6.3
 create a MS on rhel 6.3
 Try creating a zone
 Bug : zone creation fails at adding host step
 MS log shows :
 014-07-11 03:33:46,284 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Received unknown parameters for 
 command addHost. Unknown parameters : clustertype
 2014-07-11 03:33:46,294 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Trying to add a new host at 
 http://10.147.40.24 in data center 1
 2014-07-11 03:33:46,487 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:47,505 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:48,556 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:49,607 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) It's not a KVM enabled machine
 2014-07-11 03:33:49,608 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Unable to find the server 
 resources at http://10.147.40.24
 2014-07-11 03:33:49,611 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-11 03:33:49,611 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 

[jira] [Commented] (CLOUDSTACK-7116) unable to add KVM host to MS with error java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0

2014-07-24 Thread Kishan Kavala (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072928#comment-14072928
 ] 

Kishan Kavala commented on CLOUDSTACK-7116:
---

Agent requires java7. Unsupported major minor exception is seen when lower 
version of java is installed.

 unable to add KVM host to MS with error 
 java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : 
 Unsupported major.minor version 51.0
 -

 Key: CLOUDSTACK-7116
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7116
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: cloudstack-agent.err, management-server.log.tar.gz


 Repro steps:
 1. Create a KVM host on rhel 6.3
 As I used following build 
 http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/master/CloudPlatform-4.5.0-57-rhel6.3.tar.gz
 so i need to install jsvc outside of cloudstack for which I have done the 
 following step:
 yum install java-gcj-compat
 rpm -Uvh 
 ftp://rpmfind.net/linux/centos/6.5/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
 and then I installed agent
 Once agent installation is complete I tried to add this KVM host to MS
 and host addition failed with MS logs showing
 2014-07-16 06:09:19,082 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Timeout, to wait for the host 
 connecting to mgt svr, assuming it is failed
 2014-07-16 06:09:19,083 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Unable to find the server 
 resources at http://10.147.40.23
 2014-07-16 06:09:19,084 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-16 06:09:19,084 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 

[jira] [Resolved] (CLOUDSTACK-4475) [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added

2014-07-24 Thread Anshul Gangwar (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anshul Gangwar resolved CLOUDSTACK-4475.


Resolution: Fixed

fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51

 [ZWPS] attaching an uploaded volume to a VM is always going to first primary 
 storage added
 --

 Key: CLOUDSTACK-4475
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4475
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Storage Controller
Affects Versions: 4.2.1
 Environment: vmware esxi 5.1
Reporter: Srikanteswararao Talluri
Assignee: Anshul Gangwar
  Labels: ReleaseNote
 Fix For: 4.4.0


 Steps to reproduce:
 ==
 1. Have an advanced zone deployment with two cluster one host and one cluster 
 scoped primary storage each
 2. add two more zone wide primary storages
 3. create a deployment on zone scoped primary storage
 4. upload  a volume.
 5. attach uploaded volume to VM created in step 3.
 Observation:
 =
 While attaching volume, volume is always copied to first available primary 
 storage in the storage_pool table and as a result attaching a volume created 
 on cluster scoped primary storage to a VM with its root volume on zone wide 
 primary storage fails.
 mysql select * from storage_pool;
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 | id | name | uuid | pool_type
  | port | data_center_id | pod_id | cluster_id | used_bytes| 
 capacity_bytes | host_address | user_info | path  
  | created | removed | update_time | status  | 
 storage_provider_name | scope   | hypervisor | managed | capacity_iops |
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 |  1 | primaryclus1 | 722e6181-8497-3d31-9933-a0a267ae376c | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1678552014848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/primary  | 2013-08-23 12:11:12 | NULL   
  | NULL| Maintenance | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  2 | pimaryclu2   | 9fd9b0fc-c9fd-39b8-8d66-06372c5ff6d2 | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1676566495232 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1primary | 2013-08-23 12:18:14 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  3 | clus1p2  | 22e0c3fe-a390-38fa-8ff7-e1d965a36309 | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660903886848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1p2  | 2013-08-23 14:30:32 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  4 | clus1p3  | f2d9fb6b-c433-3c03-acf8-8f73eac48fae | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660901400576 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1p3  | 2013-08-23 14:31:05 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  5 | clus2p2  | 13bf579c-51f3-317b-893a-98ff6ca8f486 | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1660900147200 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus2p2  | 2013-08-23 14:31:38 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  7 | clus2p3  | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1660894195712 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus2p3  | 2013-08-23 14:33:03 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL 

[jira] [Reopened] (CLOUDSTACK-7097) failing to add kvm host to MS

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala reopened CLOUDSTACK-7097:
---


 failing to add  kvm host to MS
 --

 Key: CLOUDSTACK-7097
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7097
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Management Server
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.5.0

 Attachments: management-server.log.tar.gz


 Repro steps:
 Create a agent on rhel 6.3
 create a MS on rhel 6.3
 Try creating a zone
 Bug : zone creation fails at adding host step
 MS log shows :
 014-07-11 03:33:46,284 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Received unknown parameters for 
 command addHost. Unknown parameters : clustertype
 2014-07-11 03:33:46,294 INFO  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Trying to add a new host at 
 http://10.147.40.24 in data center 1
 2014-07-11 03:33:46,487 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:47,505 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:48,556 DEBUG [c.c.u.s.SSHCmdHelper] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Executing cmd: lsmod|grep kvm
 2014-07-11 03:33:49,607 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) It's not a KVM enabled machine
 2014-07-11 03:33:49,608 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Unable to find the server 
 resources at http://10.147.40.24
 2014-07-11 03:33:49,611 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-11 03:33:49,611 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-12:ctx-007b5513 ctx-c586ed3c) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 

[jira] [Resolved] (CLOUDSTACK-7116) unable to add KVM host to MS with error java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-7116.
---

Resolution: Not a Problem

 unable to add KVM host to MS with error 
 java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : 
 Unsupported major.minor version 51.0
 -

 Key: CLOUDSTACK-7116
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7116
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Kishan Kavala
Priority: Blocker
 Fix For: 4.5.0

 Attachments: cloudstack-agent.err, management-server.log.tar.gz


 Repro steps:
 1. Create a KVM host on rhel 6.3
 As I used following build 
 http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/master/CloudPlatform-4.5.0-57-rhel6.3.tar.gz
 so i need to install jsvc outside of cloudstack for which I have done the 
 following step:
 yum install java-gcj-compat
 rpm -Uvh 
 ftp://rpmfind.net/linux/centos/6.5/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
 and then I installed agent
 Once agent installation is complete I tried to add this KVM host to MS
 and host addition failed with MS logs showing
 2014-07-16 06:09:19,082 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Timeout, to wait for the host 
 connecting to mgt svr, assuming it is failed
 2014-07-16 06:09:19,083 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Unable to find the server 
 resources at http://10.147.40.23
 2014-07-16 06:09:19,084 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-07-16 06:09:19,084 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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.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 $Proxy148.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6417) Adding the KVM host to management server is failing

2014-07-24 Thread Kishan Kavala (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-6417.
---

Resolution: Not a Problem

 Adding the KVM host to management server is failing
 ---

 Key: CLOUDSTACK-6417
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6417
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, Management Server
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Kishan Kavala
 Fix For: 4.4.0

 Attachments: management-server.rar


 Updated java version to 1.7 in both MS and KVM host before installing the CS 
 packages.
 When KVM agent is installed ,the agent package is installing java 1.6
  
Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.45.1.11.1.el6.x86_64
 Now java -verison was pointing to 1.6
 Adding the host to CS is failing with following exception:
 2014-04-15 06:33:43,505 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] 
 (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Timeout, to wait for the host 
 connecting to mgt svr, assuming it is failed
 2014-04-15 06:33:43,511 WARN  [c.c.r.ResourceManagerImpl] 
 (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Unable to find the server 
 resources at http://10.147.40.29
 2014-04-15 06:33:43,513 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Could not find exception: 
 com.cloud.exception.DiscoveryException in error code list for exceptions
 2014-04-15 06:33:43,514 WARN  [o.a.c.a.c.a.h.AddHostCmd] 
 (catalina-exec-25:ctx-cace7f62 ctx-dbfc6bb9) Exception:
 com.cloud.exception.DiscoveryException: Unable to add the host
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
 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 
 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.$Proxy145.discoverHosts(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
 at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   

[jira] [Comment Edited] (CLOUDSTACK-4475) [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added

2014-07-24 Thread Anshul Gangwar (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072927#comment-14072927
 ] 

Anshul Gangwar edited comment on CLOUDSTACK-4475 at 7/24/14 7:26 AM:
-

fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 
 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM 
on zwps, then we were passing the podId of VM instead of storage pool to 
storage allocator. This resulting in use of Clusterscope storage allocator, 
allocating a storage pool for VM on zwps beacuse of pod id not null. This was 
resulting in scope conflict later


was (Author: anshulg):
fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51

 [ZWPS] attaching an uploaded volume to a VM is always going to first primary 
 storage added
 --

 Key: CLOUDSTACK-4475
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4475
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Storage Controller
Affects Versions: 4.2.1
 Environment: vmware esxi 5.1
Reporter: Srikanteswararao Talluri
Assignee: Anshul Gangwar
  Labels: ReleaseNote
 Fix For: 4.4.0


 Steps to reproduce:
 ==
 1. Have an advanced zone deployment with two cluster one host and one cluster 
 scoped primary storage each
 2. add two more zone wide primary storages
 3. create a deployment on zone scoped primary storage
 4. upload  a volume.
 5. attach uploaded volume to VM created in step 3.
 Observation:
 =
 While attaching volume, volume is always copied to first available primary 
 storage in the storage_pool table and as a result attaching a volume created 
 on cluster scoped primary storage to a VM with its root volume on zone wide 
 primary storage fails.
 mysql select * from storage_pool;
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 | id | name | uuid | pool_type
  | port | data_center_id | pod_id | cluster_id | used_bytes| 
 capacity_bytes | host_address | user_info | path  
  | created | removed | update_time | status  | 
 storage_provider_name | scope   | hypervisor | managed | capacity_iops |
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 |  1 | primaryclus1 | 722e6181-8497-3d31-9933-a0a267ae376c | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1678552014848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/primary  | 2013-08-23 12:11:12 | NULL   
  | NULL| Maintenance | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  2 | pimaryclu2   | 9fd9b0fc-c9fd-39b8-8d66-06372c5ff6d2 | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1676566495232 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1primary | 2013-08-23 12:18:14 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  3 | clus1p2  | 22e0c3fe-a390-38fa-8ff7-e1d965a36309 | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660903886848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1p2  | 2013-08-23 14:30:32 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  4 | clus1p3  | f2d9fb6b-c433-3c03-acf8-8f73eac48fae | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660901400576 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1p3  | 2013-08-23 14:31:05 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  5 | clus2p2  | 13bf579c-51f3-317b-893a-98ff6ca8f486 | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1660900147200 |  590228480 | 10.147.28.7  | NULL  | 
 

[jira] [Comment Edited] (CLOUDSTACK-4475) [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added

2014-07-24 Thread Anshul Gangwar (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072927#comment-14072927
 ] 

Anshul Gangwar edited comment on CLOUDSTACK-4475 at 7/24/14 7:28 AM:
-

fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 
 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM 
on zwps, then we were passing the podId of VM instead of storage pool to 
storage allocator. This resulting in use of Clusterscope storage allocator, 
allocating a storage pool for VM on zwps beacuse of pod id not null. This was 
resulting in scope conflict later

verified the scenario on hyper-v setup 


was (Author: anshulg):
fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 
 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM 
on zwps, then we were passing the podId of VM instead of storage pool to 
storage allocator. This resulting in use of Clusterscope storage allocator, 
allocating a storage pool for VM on zwps beacuse of pod id not null. This was 
resulting in scope conflict later

 [ZWPS] attaching an uploaded volume to a VM is always going to first primary 
 storage added
 --

 Key: CLOUDSTACK-4475
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4475
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Storage Controller
Affects Versions: 4.2.1
 Environment: vmware esxi 5.1
Reporter: Srikanteswararao Talluri
Assignee: Anshul Gangwar
  Labels: ReleaseNote
 Fix For: 4.4.0


 Steps to reproduce:
 ==
 1. Have an advanced zone deployment with two cluster one host and one cluster 
 scoped primary storage each
 2. add two more zone wide primary storages
 3. create a deployment on zone scoped primary storage
 4. upload  a volume.
 5. attach uploaded volume to VM created in step 3.
 Observation:
 =
 While attaching volume, volume is always copied to first available primary 
 storage in the storage_pool table and as a result attaching a volume created 
 on cluster scoped primary storage to a VM with its root volume on zone wide 
 primary storage fails.
 mysql select * from storage_pool;
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 | id | name | uuid | pool_type
  | port | data_center_id | pod_id | cluster_id | used_bytes| 
 capacity_bytes | host_address | user_info | path  
  | created | removed | update_time | status  | 
 storage_provider_name | scope   | hypervisor | managed | capacity_iops |
 ++--+--+---+--++++---++--+---++-+-+-+-+---+-++-+---+
 |  1 | primaryclus1 | 722e6181-8497-3d31-9933-a0a267ae376c | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1678552014848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/primary  | 2013-08-23 12:11:12 | NULL   
  | NULL| Maintenance | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  2 | pimaryclu2   | 9fd9b0fc-c9fd-39b8-8d66-06372c5ff6d2 | 
 NetworkFilesystem | 2049 |  1 |  1 |  2 | 
 1676566495232 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1primary | 2013-08-23 12:18:14 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  3 | clus1p2  | 22e0c3fe-a390-38fa-8ff7-e1d965a36309 | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660903886848 |  590228480 | 10.147.28.7  | NULL  | 
 /export/home/talluri/vmware.campo/clus1p2  | 2013-08-23 14:30:32 | NULL   
  | NULL| Up  | DefaultPrimary| CLUSTER | NULL   | 
   0 |  NULL |
 |  4 | clus1p3  | f2d9fb6b-c433-3c03-acf8-8f73eac48fae | 
 NetworkFilesystem | 2049 |  1 |  1 |  1 | 
 1660901400576 |  590228480 | 10.147.28.7  | NULL  | 
 

[jira] [Commented] (CLOUDSTACK-7174) [VMware] Recreating System VMs fails if global config 'vm.instancename' is set to true

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072951#comment-14072951
 ] 

ASF subversion and git services commented on CLOUDSTACK-7174:
-

Commit 786285ab54bf93a4d1cc4d0e688f91a41a1d84bb in cloudstack's branch 
refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=786285a ]

CLOUDSTACK-7174. [VMware] Recreating System VMs fails if global config 
'vm.instancename' is set to true.
Append VM's name in vCenter with the hostname only for User VMs.


 [VMware] Recreating System VMs fails if global config 'vm.instancename' is 
 set to true
 --

 Key: CLOUDSTACK-7174
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7174
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.5.0
Reporter: Likitha Shetty
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.5.0


 Steps to reproduce
 1. Set the global config 'vm.instancename' to true
 2. Destroy SSVM
 3. New SSVM fails to start with the below error
 {noformat}
 2014-07-23 16:49:10,768 WARN  [c.c.h.v.r.VmwareResource] 
 (DirectAgent-5:ctx-7050a6c8 10.102.192.7, job-478/job-487, cmd: StartCommand) 
 StartCommand failed due to Exception: java.lang.Exception
 Message: Failed to find the newly create or relocated VM. vmName: s-27-VM
 java.lang.Exception: Failed to find the newly create or relocated VM. vmName: 
 s-27-VM
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1419)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:462)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
 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)
 2014-07-23 16:49:10,778 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-5:ctx-7050a6c8) Seq 1-1545579097118212119: Cancelling because 
 one of the answers is false and it is stop on error.
 {noformat}
 This is a regression caused by a recent commit - 
 5143fe404bc82dfe42b832c661b4e98a0d9ebfa8



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7174) [VMware] Recreating System VMs fails if global config 'vm.instancename' is set to true

2014-07-24 Thread Likitha Shetty (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Likitha Shetty resolved CLOUDSTACK-7174.


Resolution: Fixed

 [VMware] Recreating System VMs fails if global config 'vm.instancename' is 
 set to true
 --

 Key: CLOUDSTACK-7174
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7174
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.5.0
Reporter: Likitha Shetty
Assignee: Likitha Shetty
Priority: Critical
 Fix For: 4.5.0


 Steps to reproduce
 1. Set the global config 'vm.instancename' to true
 2. Destroy SSVM
 3. New SSVM fails to start with the below error
 {noformat}
 2014-07-23 16:49:10,768 WARN  [c.c.h.v.r.VmwareResource] 
 (DirectAgent-5:ctx-7050a6c8 10.102.192.7, job-478/job-487, cmd: StartCommand) 
 StartCommand failed due to Exception: java.lang.Exception
 Message: Failed to find the newly create or relocated VM. vmName: s-27-VM
 java.lang.Exception: Failed to find the newly create or relocated VM. vmName: 
 s-27-VM
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1419)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:462)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:294)
 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)
 2014-07-23 16:49:10,778 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-5:ctx-7050a6c8) Seq 1-1545579097118212119: Cancelling because 
 one of the answers is false and it is stop on error.
 {noformat}
 This is a regression caused by a recent commit - 
 5143fe404bc82dfe42b832c661b4e98a0d9ebfa8



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-7127) Fix test_regions.py script - addregion failed, Region with id: 1 already exists

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7127:
--

Assignee: Gaurav Aradhye  (was: Ashutosk Kelkar)

 Fix test_regions.py script -  addregion failed, Region with id: 1 already 
 exists
 

 Key: CLOUDSTACK-7127
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7127
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 ===
 Code Snippet from test_regions.py:
 ===
def setUp(self):
 pseudo_random_int = choice(xrange(1, 200)) -- BUG: Region with ID=1 
 already exists on the CloudStack Setup. In case if 1 is chosen the testsuite 
 fails to execute.
 self.services[region][regionid] = pseudo_random_int
 self.services[region][regionname] = region + 
 str(pseudo_random_int)
 self.services[region][regionendpoint] = http://region; + 
 str(pseudo_random_int) + :8080/client
 self.region = Region.create(self.api_client,
 self.services[region]
 )
 Secondly, setup method code should be placed in try and catch blocks
 =
 Test Error:
 =
 Error Message:
 Execute cmd: addregion failed, due to: errorCode: 431, errorText:Region with 
 id: 1 already exists
   begin captured stdout  -
 === TestName: test_createRegionWithExistingRegionName | Status : EXCEPTION ===
 -  end captured stdout  --
   begin captured logging  
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: STARTED 
 : TC: test_createRegionWithExistingRegionName :::
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Payload: 
 {'endpoint': 'http://region1:8080/client', 'name': 'region1', 'id': 1, 
 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'addRegion', 'signature': 'jZQivyHVubuotqAzSjRPxUJmAn4=', 
 'response': 'json'}
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Sending GET 
 Cmd : addRegion===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?endpoint=http%3A%2F%2Fregion1%3A8080%2Fclientname=region1id=1apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=addRegionsignature=jZQivyHVubuotqAzSjRPxUJmAn4%3Dresponse=json
  HTTP/1.1 431 123
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: 
 Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: marvinRequest : 
 CmdName: marvin.cloudstackAPI.addRegion.addRegionCmd object at 0x3341e50 
 Exception: ['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already 

[jira] [Resolved] (CLOUDSTACK-7127) Fix test_regions.py script - addregion failed, Region with id: 1 already exists

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye resolved CLOUDSTACK-7127.


Resolution: Fixed

 Fix test_regions.py script -  addregion failed, Region with id: 1 already 
 exists
 

 Key: CLOUDSTACK-7127
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7127
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 ===
 Code Snippet from test_regions.py:
 ===
def setUp(self):
 pseudo_random_int = choice(xrange(1, 200)) -- BUG: Region with ID=1 
 already exists on the CloudStack Setup. In case if 1 is chosen the testsuite 
 fails to execute.
 self.services[region][regionid] = pseudo_random_int
 self.services[region][regionname] = region + 
 str(pseudo_random_int)
 self.services[region][regionendpoint] = http://region; + 
 str(pseudo_random_int) + :8080/client
 self.region = Region.create(self.api_client,
 self.services[region]
 )
 Secondly, setup method code should be placed in try and catch blocks
 =
 Test Error:
 =
 Error Message:
 Execute cmd: addregion failed, due to: errorCode: 431, errorText:Region with 
 id: 1 already exists
   begin captured stdout  -
 === TestName: test_createRegionWithExistingRegionName | Status : EXCEPTION ===
 -  end captured stdout  --
   begin captured logging  
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: STARTED 
 : TC: test_createRegionWithExistingRegionName :::
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Payload: 
 {'endpoint': 'http://region1:8080/client', 'name': 'region1', 'id': 1, 
 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'addRegion', 'signature': 'jZQivyHVubuotqAzSjRPxUJmAn4=', 
 'response': 'json'}
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Sending GET 
 Cmd : addRegion===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?endpoint=http%3A%2F%2Fregion1%3A8080%2Fclientname=region1id=1apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=addRegionsignature=jZQivyHVubuotqAzSjRPxUJmAn4%3Dresponse=json
  HTTP/1.1 431 123
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: 
 Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: marvinRequest : 
 CmdName: marvin.cloudstackAPI.addRegion.addRegionCmd object at 0x3341e50 
 Exception: ['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists\n']
 Traceback (most recent 

[jira] [Resolved] (CLOUDSTACK-6809) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps

2014-07-24 Thread Devdeep Singh (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Devdeep Singh resolved CLOUDSTACK-6809.
---

Resolution: Not a Problem

We do not allow live storage motion of a volume from cluster wide to zone wide 
primary storage. That is why the findStoragePoolsForMigration api lists only 
zone wide pools for a volume on zone wide storage and cluster wide pools for a 
volume on cluster wide storage. This is the expected behavior.

 listStoragePoolsForMigration doesn't list the zone wide primary storages if 
 the volume is on cluster-wide storage, and doesn't list cwps if volume is on 
 zwps 
 --

 Key: CLOUDSTACK-6809
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Storage Controller
Affects Versions: 4.4.0
 Environment: HyperV Advanced zone setup with cluster wide, zone wide 
 and local storages.
Reporter: Abhinav Roy
Assignee: Devdeep Singh
Priority: Critical
  Labels: S1
 Fix For: 4.4.0


 Steps :
 ==
 1. Deploy a advanced zone hyperv setup with 2 clusters.
 2. Have 2 primary storages in each of the clusters and 2 zone wide primary 
 storages.
 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2
 4. Deply a VM v2 on zone wide primary storage in cluster1/2.
 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2
 Expected behavior :
 =
 All zone wide primary storage and cluster wide primary storages available 
 should be listed
 Observed behavior :
 =
 1. list for v1 doesn't show any zone wide primary storage.
 monkey# find storagepoolsformigration id=31
 count = 1
 storagepool:
 name = p2
 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef
 clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a
 clustername = cluster1
 created = 2014-05-26T11:27:01+0530
 disksizeallocated = 1073741824
 disksizetotal = 998772830208
 disksizeused = 157359783936
 ipaddress = SMB19
 jobstatus = 0
 overprovisionfactor = 2.0
 path = /hyperv-share/abhinav-ps2?user=abhinavroydomain=BLR
 podid = f36ada26-ecf2-4869-ba4f-d844ec23531a
 podname = hyperv
 scope = CLUSTER
 state = Up
 suitableformigration = False
 type = SMB
 zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7
 zonename = hyperv
 2. list for v2 doesn't show any cluster wide primary storage
 monkey# find storagepoolsformigration id=30
 count = 1
 storagepool:
 name = zwps
 id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc
 created = 2014-05-30T11:57:02+0530
 disksizeallocated = 0
 disksizetotal = 998772830208
 hypervisor = Hyperv
 ipaddress = SMB19
 jobstatus = 0
 overprovisionfactor = 2.0
 path = /hyperv-share/abhinav-ps6?user=abhinavroydomain=BLR
 scope = ZONE
 state = Up
 suitableformigration = False
 type = SMB
 zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7
 zonename = hyperv
 NOTE : Even though the pools are not listed, if the migration is attempted 
 using  the API and passing these storage pool ids, migration succeeds from 
 zwps to cwps and vice-versa



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7158) listCapacity API missing types for certain zones

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073047#comment-14073047
 ] 

ASF subversion and git services commented on CLOUDSTACK-7158:
-

Commit da55aff64f1b8255daa7999b91672bd2195bb76b in cloudstack's branch 
refs/heads/master from [~bharat.kumar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=da55aff ]

CLOUDSTACK-7158 listCapacity API missing types for certain zones


 listCapacity API missing types for certain zones
 

 Key: CLOUDSTACK-7158
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7158
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Bharat Kumar
Assignee: Bharat Kumar
 Fix For: 4.5.0


 Issue
 
 listCapacity only shows type 2  6 when for certain zones. If zone id is 
 specified all types are shown.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-5212) [UI]Need Support for the LXC for the Report sockets CS-4908

2014-07-24 Thread Rajani Karuturi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajani Karuturi reassigned CLOUDSTACK-5212:
---

Assignee: Rajani Karuturi  (was: Jessica Wang)

 [UI]Need Support for the LXC for the Report sockets CS-4908
 ---

 Key: CLOUDSTACK-5212
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5212
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kiran Koneti
Assignee: Rajani Karuturi
Priority: Critical
 Fix For: 4.4.0


 For the report sockets feature we need to provide support for the LXC 
 hypervisor.The support is not yet added.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-6980) UI for RegisterTemplate API does not expose requireshvm parameter

2014-07-24 Thread Rajani Karuturi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajani Karuturi reassigned CLOUDSTACK-6980:
---

Assignee: Rajani Karuturi  (was: Jessica Wang)

 UI for RegisterTemplate API does not expose requireshvm parameter
 -

 Key: CLOUDSTACK-6980
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6980
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kishan Kavala
Assignee: Rajani Karuturi

 requireshvm parameter should be false for LXC templates.
 UI does not provide option to set this parameter to false for 
 RegisterTemplate API 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7178) [Automation] Escalations test cases failing with import error while importing BOOLEAN

2014-07-24 Thread Gaurav Aradhye (JIRA)
Gaurav Aradhye created CLOUDSTACK-7178:
--

 Summary: [Automation] Escalations test cases failing with import 
error while importing BOOLEAN
 Key: CLOUDSTACK-7178
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7178
 Project: CloudStack
  Issue Type: Test
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
 Fix For: 4.5.0


Following test cases failing while importing BOOLEAN

test_escalations_ip_addresses.py
test_escalations_snapshtos.py

Resolution:
Remove the import as it is not used anywhere in the code.
Also modify the imports to not use import *



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-5212) [UI]Need Support for the LXC for the Report sockets CS-4908

2014-07-24 Thread Rajani Karuturi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073126#comment-14073126
 ] 

Rajani Karuturi commented on CLOUDSTACK-5212:
-

patch on review board https://reviews.apache.org/r/23884/

 [UI]Need Support for the LXC for the Report sockets CS-4908
 ---

 Key: CLOUDSTACK-5212
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5212
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kiran Koneti
Assignee: Rajani Karuturi
Priority: Critical
 Fix For: 4.4.0


 For the report sockets feature we need to provide support for the LXC 
 hypervisor.The support is not yet added.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-5212) [UI]Need Support for the LXC for the Report sockets CS-4908

2014-07-24 Thread Rajani Karuturi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajani Karuturi updated CLOUDSTACK-5212:


Status: Reviewable  (was: In Progress)

 [UI]Need Support for the LXC for the Report sockets CS-4908
 ---

 Key: CLOUDSTACK-5212
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5212
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Kiran Koneti
Assignee: Rajani Karuturi
Priority: Critical
 Fix For: 4.4.0


 For the report sockets feature we need to provide support for the LXC 
 hypervisor.The support is not yet added.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-5870) API support for retrieving UserData

2014-07-24 Thread sadhu suresh (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073140#comment-14073140
 ] 

sadhu suresh commented on CLOUDSTACK-5870:
--

retrieved user data through getVirtualMachineUserdata API shows user data in 
encrypted(basse64 ) format.is it  expected  behavior or it should show value 
decrypted format as customerVM

getvirtualmachineuserdataresponse 
cloud-stack-version=4.5.0-SNAPSHOTvirtualmachineuserdatavirtualmachineid5c0b953e-e8ed-4774-92aa-b5d9eb7647f9/virtualmachineiduserdataY3VzdG9tZXJWTQ==/userdata/virtualmachineuserdata/getvirtualmachineuserdataresponse

 API support for retrieving UserData
 ---

 Key: CLOUDSTACK-5870
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5870
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.4.0


 Current UserData behavior:
  * userData is passed to the deployVm/updateVm call
  * its stored in CS db and on the VR
  * the only one way to retrieve the data, is to request it from the user vm 
 inside the network by sending http request to the Virtual Router.
  We've adopted this model from Amazon EC2 APIs. But along the way I've 
 noticed that some third party integrators needed to read UserData by Admin to 
 get the information about all vms in the system/network. To solve the 
 problem, people were using different kinds of workarounds - db scripts to 
 read userData from cloudstack DB, or writing CS API extensions: 
 https://github.com/jasonhancock/cloudstack-api-extension.
 So the API I'm proposing, will let you to retrieve User Data via Web API. API 
 will be available to admin as well as end user.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7146) [Automation] Fix the scripts test_assign_vm.py, test_project_limits.py,test_project_resources.py,test_ps_domain_limits.py - Cleanup of domain should be done afte

2014-07-24 Thread Gaurav Aradhye (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073162#comment-14073162
 ] 

Gaurav Aradhye commented on CLOUDSTACK-7146:


Hey Chandan, can you please point me to jenkins build url from where you have 
logged the bug?

 [Automation] Fix the scripts test_assign_vm.py, 
 test_project_limits.py,test_project_resources.py,test_ps_domain_limits.py - 
 Cleanup of domain should be done after cleaning up account in it
 --

 Key: CLOUDSTACK-7146
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7146
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 
 Error Messages:
 
 ---
 One:
 ---
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Payload: 
 {'signature': 'ctoosHX10fXC2XJv8iFdUiNqV5Q=', 'apiKey': 
 u'K1eKecmH_8ipIelDho9Wm-HZm0WhiIw-2cGFZveZJdKOwB_Cchln9O4QBNxkyy8U8UHCRt_leTpa-yvEb04EOA',
  'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: 
 Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.41
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=ctoosHX10fXC2XJv8iFdUiNqV5Q%3DapiKey=K1eKecmH_8ipIelDho9Wm-HZm0WhiIw-2cGFZveZJdKOwB_Cchln9O4QBNxkyy8U8UHCRt_leTpa-yvEb04EOAcommand=queryAsyncJobResultresponse=jsonjobid=ebbf78c7-5a1d-4051-8404-26314a59151a
  HTTP/1.1 200 477
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Response : 
 {jobprocstatus : 0, created : u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): ERROR:  __poll: 
 Exception Occurred :Job failed: {jobprocstatus : 0, created : 
 u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'} 
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-adv-xs/work.63/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 105, in __poll
 % async_response)
 Exception: Job failed: {jobprocstatus : 0, created : 
 u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Response : 
 FAILED
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): ERROR: marvinRequest 
 : CmdName: marvin.cloudstackAPI.deleteDomain.deleteDomainCmd object at 
 0x3844810 Exception: ['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-adv-xs/work.63/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 'Exception: Job 
 failed: {jobprocstatus : 0, created : u\'2014-07-11T16:11:24+\', cmd : 
 u\'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd\', userid : 
 

[jira] [Commented] (CLOUDSTACK-7178) [Automation] Escalations test cases failing with import error while importing BOOLEAN

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073247#comment-14073247
 ] 

ASF subversion and git services commented on CLOUDSTACK-7178:
-

Commit 78a6d557f86db354a073090fc92ea693ee235e1f in cloudstack's branch 
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=78a6d55 ]

CLOUDSTACK-7178: Correcting imports in test_escalations* test cases


 [Automation] Escalations test cases failing with import error while importing 
 BOOLEAN
 -

 Key: CLOUDSTACK-7178
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7178
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Following test cases failing while importing BOOLEAN
 test_escalations_ip_addresses.py
 test_escalations_snapshtos.py
 Resolution:
 Remove the import as it is not used anywhere in the code.
 Also modify the imports to not use import *



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7178) [Automation] Escalations test cases failing with import error while importing BOOLEAN

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073250#comment-14073250
 ] 

ASF subversion and git services commented on CLOUDSTACK-7178:
-

Commit 4e45b296891f71fc7991dc507dc7ae9cec6f5496 in cloudstack's branch 
refs/heads/4.4-forward from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4e45b29 ]

CLOUDSTACK-7178: Correcting imports in test_escalations* test cases


 [Automation] Escalations test cases failing with import error while importing 
 BOOLEAN
 -

 Key: CLOUDSTACK-7178
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7178
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Following test cases failing while importing BOOLEAN
 test_escalations_ip_addresses.py
 test_escalations_snapshtos.py
 Resolution:
 Remove the import as it is not used anywhere in the code.
 Also modify the imports to not use import *



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7125) [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be backedup before creating a Template from it

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073254#comment-14073254
 ] 

ASF subversion and git services commented on CLOUDSTACK-7125:
-

Commit 4395308bd8b469fb02fc71d1e22f25c7d89b6dff in cloudstack's branch 
refs/heads/4.4-forward from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4395308 ]

CLOUDSTACK-7125: Fixed test_blocker_bugs.py, added code to wait for snapshots 
to be in 'BackedU' state


 [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be 
 backedup before creating a Template from it
 

 Key: CLOUDSTACK-7125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7125
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 Failed to create Template as Snapshot is not BackedUp yet
 =
 Error:
 =
 CloudstackAPIException: Execute cmd: createtemplate failed, due to: 
 errorCode: 431, errorText:Snapshot id=3 is not in BackedUp state yet and 
 can't be used for template creation
 test_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): CRITICAL: EXCEPTION: 
 test_02_check_size_snapshotTemplate: ['Traceback (most recent call last):\n', 
 '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
 testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate\n
 self.services[template]\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot\nreturn 
 Template(apiclient.createTemplate(cmd).__dict__)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate\nresponse = 
 self.connection.marvinRequest(command, response_type=response, 
 method=method)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest\nraise e\n', CloudstackAPIException: Execute 
 cmd: createtemplate failed, due to: errorCode: 431, errorText:Snapshot id=3 
 is not in BackedUp state yet and can't be used for template creation\n]
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate
 self.services[template]
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot
 return Template(apiclient.createTemplate(cmd).__dict__)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest
 raise e
 'Execute cmd: createtemplate failed, due to: errorCode: 431, 
 errorText:Snapshot id=3 is not in BackedUp state yet and can\'t be used for 
 template creation\n  begin captured stdout  
 -\n=== TestName: test_02_check_size_snapshotTemplate | 
 Status : EXCEPTION ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: 
 STARTED : TC: test_02_check_size_snapshotTemplate 
 :::\ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: Payload: 
 {\'account\': u\'test-TestTemplates-test_01_create_template-PV1LCJ\', 
 \'domainid\': u\'7ccbf6bc-08ed-11e4-887d-928d578f5db8\', \'volumeid\': 
 u\'7aa4cc3c-5c23-4b30-a30d-b48bd735ebcc\', \'apiKey\': 
 u\'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA\',
  \'command\': 

[jira] [Commented] (CLOUDSTACK-7125) [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be backedup before creating a Template from it

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073253#comment-14073253
 ] 

ASF subversion and git services commented on CLOUDSTACK-7125:
-

Commit 49005b324f18e19166bcbb801bcd07609e44d8db in cloudstack's branch 
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=49005b3 ]

CLOUDSTACK-7125: Fixed test_blocker_bugs.py, added code to wait for snapshots 
to be in 'BackedU' state


 [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be 
 backedup before creating a Template from it
 

 Key: CLOUDSTACK-7125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7125
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 Failed to create Template as Snapshot is not BackedUp yet
 =
 Error:
 =
 CloudstackAPIException: Execute cmd: createtemplate failed, due to: 
 errorCode: 431, errorText:Snapshot id=3 is not in BackedUp state yet and 
 can't be used for template creation
 test_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): CRITICAL: EXCEPTION: 
 test_02_check_size_snapshotTemplate: ['Traceback (most recent call last):\n', 
 '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
 testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate\n
 self.services[template]\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot\nreturn 
 Template(apiclient.createTemplate(cmd).__dict__)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate\nresponse = 
 self.connection.marvinRequest(command, response_type=response, 
 method=method)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest\nraise e\n', CloudstackAPIException: Execute 
 cmd: createtemplate failed, due to: errorCode: 431, errorText:Snapshot id=3 
 is not in BackedUp state yet and can't be used for template creation\n]
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate
 self.services[template]
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot
 return Template(apiclient.createTemplate(cmd).__dict__)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest
 raise e
 'Execute cmd: createtemplate failed, due to: errorCode: 431, 
 errorText:Snapshot id=3 is not in BackedUp state yet and can\'t be used for 
 template creation\n  begin captured stdout  
 -\n=== TestName: test_02_check_size_snapshotTemplate | 
 Status : EXCEPTION ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: 
 STARTED : TC: test_02_check_size_snapshotTemplate 
 :::\ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: Payload: 
 {\'account\': u\'test-TestTemplates-test_01_create_template-PV1LCJ\', 
 \'domainid\': u\'7ccbf6bc-08ed-11e4-887d-928d578f5db8\', \'volumeid\': 
 u\'7aa4cc3c-5c23-4b30-a30d-b48bd735ebcc\', \'apiKey\': 
 u\'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA\',
  \'command\': 

[jira] [Commented] (CLOUDSTACK-7127) Fix test_regions.py script - addregion failed, Region with id: 1 already exists

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073257#comment-14073257
 ] 

ASF subversion and git services commented on CLOUDSTACK-7127:
-

Commit 59c77fbaa4c07e2de9578369e69f47d0e71039b8 in cloudstack's branch 
refs/heads/master from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=59c77fb ]

CLOUDSTACK-7127: Fix for addRegion failure, avoiding regionid 1 while creating 
new region through test case


 Fix test_regions.py script -  addregion failed, Region with id: 1 already 
 exists
 

 Key: CLOUDSTACK-7127
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7127
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 ===
 Code Snippet from test_regions.py:
 ===
def setUp(self):
 pseudo_random_int = choice(xrange(1, 200)) -- BUG: Region with ID=1 
 already exists on the CloudStack Setup. In case if 1 is chosen the testsuite 
 fails to execute.
 self.services[region][regionid] = pseudo_random_int
 self.services[region][regionname] = region + 
 str(pseudo_random_int)
 self.services[region][regionendpoint] = http://region; + 
 str(pseudo_random_int) + :8080/client
 self.region = Region.create(self.api_client,
 self.services[region]
 )
 Secondly, setup method code should be placed in try and catch blocks
 =
 Test Error:
 =
 Error Message:
 Execute cmd: addregion failed, due to: errorCode: 431, errorText:Region with 
 id: 1 already exists
   begin captured stdout  -
 === TestName: test_createRegionWithExistingRegionName | Status : EXCEPTION ===
 -  end captured stdout  --
   begin captured logging  
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: STARTED 
 : TC: test_createRegionWithExistingRegionName :::
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Payload: 
 {'endpoint': 'http://region1:8080/client', 'name': 'region1', 'id': 1, 
 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'addRegion', 'signature': 'jZQivyHVubuotqAzSjRPxUJmAn4=', 
 'response': 'json'}
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Sending GET 
 Cmd : addRegion===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?endpoint=http%3A%2F%2Fregion1%3A8080%2Fclientname=region1id=1apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=addRegionsignature=jZQivyHVubuotqAzSjRPxUJmAn4%3Dresponse=json
  HTTP/1.1 431 123
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: 
 Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: marvinRequest : 
 CmdName: marvin.cloudstackAPI.addRegion.addRegionCmd object at 0x3341e50 
 Exception: ['Traceback (most recent 

[jira] [Resolved] (CLOUDSTACK-7178) [Automation] Escalations test cases failing with import error while importing BOOLEAN

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye resolved CLOUDSTACK-7178.


Resolution: Fixed

 [Automation] Escalations test cases failing with import error while importing 
 BOOLEAN
 -

 Key: CLOUDSTACK-7178
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7178
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.5.0
Reporter: Gaurav Aradhye
Assignee: Gaurav Aradhye
  Labels: automation
 Fix For: 4.5.0


 Following test cases failing while importing BOOLEAN
 test_escalations_ip_addresses.py
 test_escalations_snapshtos.py
 Resolution:
 Remove the import as it is not used anywhere in the code.
 Also modify the imports to not use import *



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7125) [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be backedup before creating a Template from it

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye resolved CLOUDSTACK-7125.


Resolution: Fixed

 [Automation] Fix test_blocker_bugs script to wait for the Snapshot to be 
 backedup before creating a Template from it
 

 Key: CLOUDSTACK-7125
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7125
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 Failed to create Template as Snapshot is not BackedUp yet
 =
 Error:
 =
 CloudstackAPIException: Execute cmd: createtemplate failed, due to: 
 errorCode: 431, errorText:Snapshot id=3 is not in BackedUp state yet and 
 can't be used for template creation
 test_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): CRITICAL: EXCEPTION: 
 test_02_check_size_snapshotTemplate: ['Traceback (most recent call last):\n', 
 '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
 testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate\n
 self.services[template]\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot\nreturn 
 Template(apiclient.createTemplate(cmd).__dict__)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate\nresponse = 
 self.connection.marvinRequest(command, response_type=response, 
 method=method)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest\nraise e\n', CloudstackAPIException: Execute 
 cmd: createtemplate failed, due to: errorCode: 431, errorText:Snapshot id=3 
 is not in BackedUp state yet and can't be used for template creation\n]
 -  end captured logging  -
 Stacktrace
   File /usr/lib/python2.7/unittest/case.py, line 332, in run
 testMethod()
   File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_blocker_bugs.py,
  line 891, in test_02_check_size_snapshotTemplate
 self.services[template]
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 1164, in create_from_snapshot
 return Template(apiclient.createTemplate(cmd).__dict__)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 794, in createTemplate
 response = self.connection.marvinRequest(command, response_type=response, 
 method=method)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 380, in marvinRequest
 raise e
 'Execute cmd: createtemplate failed, due to: errorCode: 431, 
 errorText:Snapshot id=3 is not in BackedUp state yet and can\'t be used for 
 template creation\n  begin captured stdout  
 -\n=== TestName: test_02_check_size_snapshotTemplate | 
 Status : EXCEPTION ===\n\n\n-  end captured stdout  
 --\n  begin captured logging  
 \ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: 
 STARTED : TC: test_02_check_size_snapshotTemplate 
 :::\ntest_02_check_size_snapshotTemplate 
 (integration.component.test_blocker_bugs.TestTemplates): DEBUG: Payload: 
 {\'account\': u\'test-TestTemplates-test_01_create_template-PV1LCJ\', 
 \'domainid\': u\'7ccbf6bc-08ed-11e4-887d-928d578f5db8\', \'volumeid\': 
 u\'7aa4cc3c-5c23-4b30-a30d-b48bd735ebcc\', \'apiKey\': 
 u\'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA\',
  \'command\': \'createSnapshot\', \'signature\': 
 \'xX9H+dRDsmZwsicoTcSlP+yZo7g=\', \'response\': 
 \'json\'}\ntest_02_check_size_snapshotTemplate 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7127) Fix test_regions.py script - addregion failed, Region with id: 1 already exists

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073258#comment-14073258
 ] 

ASF subversion and git services commented on CLOUDSTACK-7127:
-

Commit ca59f01602823a6d6fe84233f3a3d3ea499efa06 in cloudstack's branch 
refs/heads/4.4-forward from [~gauravaradhye]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca59f01 ]

CLOUDSTACK-7127: Fix for addRegion failure, avoiding regionid 1 while creating 
new region through test case


 Fix test_regions.py script -  addregion failed, Region with id: 1 already 
 exists
 

 Key: CLOUDSTACK-7127
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7127
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 ===
 Code Snippet from test_regions.py:
 ===
def setUp(self):
 pseudo_random_int = choice(xrange(1, 200)) -- BUG: Region with ID=1 
 already exists on the CloudStack Setup. In case if 1 is chosen the testsuite 
 fails to execute.
 self.services[region][regionid] = pseudo_random_int
 self.services[region][regionname] = region + 
 str(pseudo_random_int)
 self.services[region][regionendpoint] = http://region; + 
 str(pseudo_random_int) + :8080/client
 self.region = Region.create(self.api_client,
 self.services[region]
 )
 Secondly, setup method code should be placed in try and catch blocks
 =
 Test Error:
 =
 Error Message:
 Execute cmd: addregion failed, due to: errorCode: 431, errorText:Region with 
 id: 1 already exists
   begin captured stdout  -
 === TestName: test_createRegionWithExistingRegionName | Status : EXCEPTION ===
 -  end captured stdout  --
   begin captured logging  
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: STARTED 
 : TC: test_createRegionWithExistingRegionName :::
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Payload: 
 {'endpoint': 'http://region1:8080/client', 'name': 'region1', 'id': 1, 
 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'addRegion', 'signature': 'jZQivyHVubuotqAzSjRPxUJmAn4=', 
 'response': 'json'}
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): DEBUG: Sending GET 
 Cmd : addRegion===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?endpoint=http%3A%2F%2Fregion1%3A8080%2Fclientname=region1id=1apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=addRegionsignature=jZQivyHVubuotqAzSjRPxUJmAn4%3Dresponse=json
  HTTP/1.1 431 123
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: 
 Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 'CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists\n']
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: addregion failed, due to: errorCode: 
 431, errorText:Region with id: 1 already exists
 test_createRegionWithExistingRegionName 
 (integration.component.test_regions.TestRegions): ERROR: marvinRequest : 
 CmdName: marvin.cloudstackAPI.addRegion.addRegionCmd object at 0x3341e50 
 Exception: ['Traceback (most 

[jira] [Assigned] (CLOUDSTACK-7135) [Automation] Fix the script test_baremetal.py - Can't have more than one Guest network in zone with network type Basic

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7135:
--

Assignee: Gaurav Aradhye  (was: Ashutosk Kelkar)

 [Automation] Fix the script test_baremetal.py - Can't have more than one 
 Guest network in zone with network type Basic
 

 Key: CLOUDSTACK-7135
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7135
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 
 Error Message:
 
 test_baremetal (integration.component.test_baremetal.TestBaremetal): DEBUG: 
 Sending GET Cmd : createNetwork===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAzoneid=1displaytext=defaultBaremetalNetworknetworkofferingid=84c3e203-139e-4412-ab81-8a6abecb3e35response=jsonname=defaultBaremetalNetworkcommand=createNetworksignature=alemHuTsxw31sTOaAyaZn2Cw4N8%3D
  HTTP/1.1 431 165
 test_baremetal (integration.component.test_baremetal.TestBaremetal): ERROR: 
 Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj\nraise 
 cloudstackException.CloudstackAPIException(respname, errMsg)\n', 
 CloudstackAPIException: Execute cmd: createnetwork failed, due to: 
 errorCode: 431, errorText:Can't have more than one Guest network in zone with 
 network type Basic\n]
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse
 response_cls)
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 150, in getResultObj
 raise cloudstackException.CloudstackAPIException(respname, errMsg)
 CloudstackAPIException: Execute cmd: createnetwork failed, due to: errorCode: 
 431, errorText:Can't have more than one Guest network in zone with network 
 type Basic
 test_baremetal (integration.component.test_baremetal.TestBaremetal): ERROR: 
 marvinRequest : CmdName: marvin.cloudstackAPI.createNetwork.createNetworkCmd 
 object at 0x302ebd0 Exception: ['Traceback (most recent call last):\n', '  
 File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 
 CloudstackAPIException: Execute cmd: createnetwork failed, due to: 
 errorCode: 431, errorText:Can't have more than one Guest network in zone with 
 network type Basic\n]
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest
 raise self.__lastError
 CloudstackAPIException: Execute cmd: createnetwork failed, due to: errorCode: 
 431, errorText:Can't have more than one Guest network in zone with network 
 type Basic
 test_baremetal (integration.component.test_baremetal.TestBaremetal): 
 CRITICAL: EXCEPTION: test_baremetal: ['Traceback (most recent call last):\n', 
 '  File /usr/lib/python2.7/unittest/case.py, line 332, in run\n
 testMethod()\n', '  File 
 /home/jenkins/workspace/xenrt-reg-basic-xs/cloudstack.git/test/integration/component/test_baremetal.py,
  line 110, in test_baremetal\nnetwork = Network.create(self.apiclient, 
 self.services[network], zoneid=self.zoneid, 
 networkofferingid=networkoffering.id)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/lib/base.py,
  line 2591, in create\nreturn 
 Network(apiclient.createNetwork(cmd).__dict__)\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 1854, in createNetwork\nresponse = 
 self.connection.marvinRequest(command, response_type=response, 
 method=method)\n', '  File 
 

[jira] [Updated] (CLOUDSTACK-7146) [Automation] Fix the scripts test_assign_vm.py, test_project_limits.py,test_project_resources.py,test_ps_domain_limits.py - Cleanup of domain should be done after

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-7146:
---

Assignee: Girish Shilamkar  (was: Gaurav Aradhye)

 [Automation] Fix the scripts test_assign_vm.py, 
 test_project_limits.py,test_project_resources.py,test_ps_domain_limits.py - 
 Cleanup of domain should be done after cleaning up account in it
 --

 Key: CLOUDSTACK-7146
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7146
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Girish Shilamkar
Priority: Critical
 Fix For: 4.5.0


 
 Error Messages:
 
 ---
 One:
 ---
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Payload: 
 {'signature': 'ctoosHX10fXC2XJv8iFdUiNqV5Q=', 'apiKey': 
 u'K1eKecmH_8ipIelDho9Wm-HZm0WhiIw-2cGFZveZJdKOwB_Cchln9O4QBNxkyy8U8UHCRt_leTpa-yvEb04EOA',
  'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: 
 Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.41
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=ctoosHX10fXC2XJv8iFdUiNqV5Q%3DapiKey=K1eKecmH_8ipIelDho9Wm-HZm0WhiIw-2cGFZveZJdKOwB_Cchln9O4QBNxkyy8U8UHCRt_leTpa-yvEb04EOAcommand=queryAsyncJobResultresponse=jsonjobid=ebbf78c7-5a1d-4051-8404-26314a59151a
  HTTP/1.1 200 477
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Response : 
 {jobprocstatus : 0, created : u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): ERROR:  __poll: 
 Exception Occurred :Job failed: {jobprocstatus : 0, created : 
 u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'} 
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-adv-xs/work.63/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 105, in __poll
 % async_response)
 Exception: Job failed: {jobprocstatus : 0, created : 
 u'2014-07-11T16:11:24+', cmd : 
 u'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd', userid : 
 u'ce302410-0901-11e4-a9bc-5a9383355ca2', jobstatus : 2, jobid : 
 u'ebbf78c7-5a1d-4051-8404-26314a59151a', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : uCan't delete the 
 domain yet because it has 1 accounts to cleanup}, accountid : 
 u'ce30160a-0901-11e4-a9bc-5a9383355ca2'}
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): DEBUG: Response : 
 FAILED
 test_16_move_across_subdomain_volume_and_account_limit 
 (integration.component.test_assign_vm.TestVMOwnership): ERROR: marvinRequest 
 : CmdName: marvin.cloudstackAPI.deleteDomain.deleteDomainCmd object at 
 0x3844810 Exception: ['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-adv-xs/work.63/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 375, in marvinRequest\nraise self.__lastError\n', 'Exception: Job 
 failed: {jobprocstatus : 0, created : u\'2014-07-11T16:11:24+\', cmd : 
 u\'org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd\', userid : 
 u\'ce302410-0901-11e4-a9bc-5a9383355ca2\', jobstatus : 2, jobid : 
 

[jira] [Assigned] (CLOUDSTACK-6770) [Automation]: Test case failure in test_primary_storage.py

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-6770:
--

Assignee: Gaurav Aradhye  (was: Bharat Kumar)

 [Automation]: Test case failure in test_primary_storage.py
 --

 Key: CLOUDSTACK-6770
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6770
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Harikrishna Patnala
Assignee: Gaurav Aradhye
 Fix For: 4.4.0

 Attachments: test_01_primary_storage_iscsi_REPORT.rtf, 
 test_01_primary_storage_nfs_REPORT.rtf, vmops.log


 There are test case failures in test_primary_storage.py
 1) 
 integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_iscsi
 2) 
 integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_nfs
 Attached test reports and management server logs



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-7134) [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is being deployed in a Basic Zone deployment

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7134:
--

Assignee: Gaurav Aradhye  (was: Girish Shilamkar)

 [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is 
 being deployed in a Basic Zone deployment
 ---

 Key: CLOUDSTACK-7134
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7134
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 =
 Error Message:
 =
 est_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Response : {jobprocstatus : 0, created : u'2014-07-11T16:46:43+', 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 1, jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', jobresultcode : 0, jobresulttype : 
 u'object', jobresult : {domain : u'ROOT', domainid : 
 u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', haenable : False, templatename : 
 u'Cent OS Template-9UKJWR', securitygroup : [{egressrule : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 description : u'Default Security Group', tags : [], ingressrule : [], id : 
 u'980df1d5-b24b-4851-b86c-2fd149692a57', name : u'default'}], zoneid : 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', cpunumber : 1, ostypeid : 12, 
 passwordenabled : True, instancename : u'i-150-92-VM', id : 
 u'e391e779-2efe-4c6a-ad1f-e03d0867165f', hostname : u'swordtail', displayvm : 
 True, state : u'Running', guestosid : 
 u'7cd2c9a6-08ed-11e4-887d-928d578f5db8', details : {hypervisortoolsversion : 
 u'xenserver56'}, memory : 128, serviceofferingid : 
 u'5a70bf03-2147-4426-80a9-11d76f658c7b', zonename : u'XenRT-Zone-0', 
 isdynamicallyscalable : False, displayname : u'VM', tags : [], nic : 
 [{networkid : u'd792af3b-8e8d-4830-aa96-0933f42c71a3', macaddress : 
 u'06:95:c6:00:00:12', type : u'Shared', broadcasturi : u'vlan://untagged', 
 traffictype : u'Guest', netmask : u'255.255.240.0', ipaddress : 
 u'10.220.114.151', id : u'1ba07040-dbaa-419e-8941-a7ba6f922676', networkname 
 : u'guestNetworkForBasicZone', gateway : u'10.220.112.1', isdefault : True}], 
 cpuspeed : 100, jobstatus : 0, templateid : 
 u'b9946974-966c-4a74-8c57-c9a55e08542d', password : u'kU8pbbvtg', 
 affinitygroup : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', hostid 
 : u'71c113f0-a559-4c9f-95b0-1bfeec463a9c', name : 
 u'VM-e391e779-2efe-4c6a-ad1f-e03d0867165f', created : 
 u'2014-07-11T16:46:43+', hypervisor : u'XenServer', jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', rootdevicetype : u'ROOT', 
 rootdeviceid : 0, serviceofferingname : u'Tiny Instance', templatedisplaytext 
 : u'Cent OS Template'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Payload: {'account': 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 'domainid': u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', 'zoneid': 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'associateIpAddress', 'signature': 
 '52qNzGUlB0gK2dd/0r/tdZKGWaE=', 'response': 'json'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Sending GET Cmd : associateIpAddress===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?account=test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XDdomainid=7ccbf6bc-08ed-11e4-887d-928d578f5db8zoneid=ae56b8ba-3fd6-4f63-b71f-32128f86688aapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=associateIpAddresssignature=52qNzGUlB0gK2dd%2F0r%2FtdZKGWaE%3Dresponse=json
  HTTP/1.1 533 129
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 ERROR: Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 

[jira] [Assigned] (CLOUDSTACK-7134) [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is being deployed in a Basic Zone deployment

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7134:
--

Assignee: Gaurav Aradhye  (was: Ashutosk Kelkar)

 [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is 
 being deployed in a Basic Zone deployment
 ---

 Key: CLOUDSTACK-7134
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7134
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 =
 Error Message:
 =
 est_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Response : {jobprocstatus : 0, created : u'2014-07-11T16:46:43+', 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 1, jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', jobresultcode : 0, jobresulttype : 
 u'object', jobresult : {domain : u'ROOT', domainid : 
 u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', haenable : False, templatename : 
 u'Cent OS Template-9UKJWR', securitygroup : [{egressrule : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 description : u'Default Security Group', tags : [], ingressrule : [], id : 
 u'980df1d5-b24b-4851-b86c-2fd149692a57', name : u'default'}], zoneid : 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', cpunumber : 1, ostypeid : 12, 
 passwordenabled : True, instancename : u'i-150-92-VM', id : 
 u'e391e779-2efe-4c6a-ad1f-e03d0867165f', hostname : u'swordtail', displayvm : 
 True, state : u'Running', guestosid : 
 u'7cd2c9a6-08ed-11e4-887d-928d578f5db8', details : {hypervisortoolsversion : 
 u'xenserver56'}, memory : 128, serviceofferingid : 
 u'5a70bf03-2147-4426-80a9-11d76f658c7b', zonename : u'XenRT-Zone-0', 
 isdynamicallyscalable : False, displayname : u'VM', tags : [], nic : 
 [{networkid : u'd792af3b-8e8d-4830-aa96-0933f42c71a3', macaddress : 
 u'06:95:c6:00:00:12', type : u'Shared', broadcasturi : u'vlan://untagged', 
 traffictype : u'Guest', netmask : u'255.255.240.0', ipaddress : 
 u'10.220.114.151', id : u'1ba07040-dbaa-419e-8941-a7ba6f922676', networkname 
 : u'guestNetworkForBasicZone', gateway : u'10.220.112.1', isdefault : True}], 
 cpuspeed : 100, jobstatus : 0, templateid : 
 u'b9946974-966c-4a74-8c57-c9a55e08542d', password : u'kU8pbbvtg', 
 affinitygroup : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', hostid 
 : u'71c113f0-a559-4c9f-95b0-1bfeec463a9c', name : 
 u'VM-e391e779-2efe-4c6a-ad1f-e03d0867165f', created : 
 u'2014-07-11T16:46:43+', hypervisor : u'XenServer', jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', rootdevicetype : u'ROOT', 
 rootdeviceid : 0, serviceofferingname : u'Tiny Instance', templatedisplaytext 
 : u'Cent OS Template'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Payload: {'account': 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 'domainid': u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', 'zoneid': 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'associateIpAddress', 'signature': 
 '52qNzGUlB0gK2dd/0r/tdZKGWaE=', 'response': 'json'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Sending GET Cmd : associateIpAddress===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?account=test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XDdomainid=7ccbf6bc-08ed-11e4-887d-928d578f5db8zoneid=ae56b8ba-3fd6-4f63-b71f-32128f86688aapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=associateIpAddresssignature=52qNzGUlB0gK2dd%2F0r%2FtdZKGWaE%3Dresponse=json
  HTTP/1.1 533 129
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 ERROR: Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 

[jira] [Updated] (CLOUDSTACK-7134) [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is being deployed in a Basic Zone deployment

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-7134:
---

Assignee: Girish Shilamkar  (was: Gaurav Aradhye)

 [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is 
 being deployed in a Basic Zone deployment
 ---

 Key: CLOUDSTACK-7134
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7134
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Girish Shilamkar
Priority: Critical
 Fix For: 4.5.0


 =
 Error Message:
 =
 est_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Response : {jobprocstatus : 0, created : u'2014-07-11T16:46:43+', 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 1, jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', jobresultcode : 0, jobresulttype : 
 u'object', jobresult : {domain : u'ROOT', domainid : 
 u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', haenable : False, templatename : 
 u'Cent OS Template-9UKJWR', securitygroup : [{egressrule : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 description : u'Default Security Group', tags : [], ingressrule : [], id : 
 u'980df1d5-b24b-4851-b86c-2fd149692a57', name : u'default'}], zoneid : 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', cpunumber : 1, ostypeid : 12, 
 passwordenabled : True, instancename : u'i-150-92-VM', id : 
 u'e391e779-2efe-4c6a-ad1f-e03d0867165f', hostname : u'swordtail', displayvm : 
 True, state : u'Running', guestosid : 
 u'7cd2c9a6-08ed-11e4-887d-928d578f5db8', details : {hypervisortoolsversion : 
 u'xenserver56'}, memory : 128, serviceofferingid : 
 u'5a70bf03-2147-4426-80a9-11d76f658c7b', zonename : u'XenRT-Zone-0', 
 isdynamicallyscalable : False, displayname : u'VM', tags : [], nic : 
 [{networkid : u'd792af3b-8e8d-4830-aa96-0933f42c71a3', macaddress : 
 u'06:95:c6:00:00:12', type : u'Shared', broadcasturi : u'vlan://untagged', 
 traffictype : u'Guest', netmask : u'255.255.240.0', ipaddress : 
 u'10.220.114.151', id : u'1ba07040-dbaa-419e-8941-a7ba6f922676', networkname 
 : u'guestNetworkForBasicZone', gateway : u'10.220.112.1', isdefault : True}], 
 cpuspeed : 100, jobstatus : 0, templateid : 
 u'b9946974-966c-4a74-8c57-c9a55e08542d', password : u'kU8pbbvtg', 
 affinitygroup : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', hostid 
 : u'71c113f0-a559-4c9f-95b0-1bfeec463a9c', name : 
 u'VM-e391e779-2efe-4c6a-ad1f-e03d0867165f', created : 
 u'2014-07-11T16:46:43+', hypervisor : u'XenServer', jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', rootdevicetype : u'ROOT', 
 rootdeviceid : 0, serviceofferingname : u'Tiny Instance', templatedisplaytext 
 : u'Cent OS Template'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Payload: {'account': 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 'domainid': u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', 'zoneid': 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'associateIpAddress', 'signature': 
 '52qNzGUlB0gK2dd/0r/tdZKGWaE=', 'response': 'json'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Sending GET Cmd : associateIpAddress===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?account=test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XDdomainid=7ccbf6bc-08ed-11e4-887d-928d578f5db8zoneid=ae56b8ba-3fd6-4f63-b71f-32128f86688aapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=associateIpAddresssignature=52qNzGUlB0gK2dd%2F0r%2FtdZKGWaE%3Dresponse=json
  HTTP/1.1 533 129
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 ERROR: Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 

[jira] [Updated] (CLOUDSTACK-7134) [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is being deployed in a Basic Zone deployment

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye updated CLOUDSTACK-7134:
---

Assignee: Girish Shilamkar  (was: Gaurav Aradhye)

 [Automation] Fix the script test_reset_ssh_keypair.py - Advanced Zone VM is 
 being deployed in a Basic Zone deployment
 ---

 Key: CLOUDSTACK-7134
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7134
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Girish Shilamkar
Priority: Critical
 Fix For: 4.5.0


 =
 Error Message:
 =
 est_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Response : {jobprocstatus : 0, created : u'2014-07-11T16:46:43+', 
 cmd : u'org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 1, jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', jobresultcode : 0, jobresulttype : 
 u'object', jobresult : {domain : u'ROOT', domainid : 
 u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', haenable : False, templatename : 
 u'Cent OS Template-9UKJWR', securitygroup : [{egressrule : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 description : u'Default Security Group', tags : [], ingressrule : [], id : 
 u'980df1d5-b24b-4851-b86c-2fd149692a57', name : u'default'}], zoneid : 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', cpunumber : 1, ostypeid : 12, 
 passwordenabled : True, instancename : u'i-150-92-VM', id : 
 u'e391e779-2efe-4c6a-ad1f-e03d0867165f', hostname : u'swordtail', displayvm : 
 True, state : u'Running', guestosid : 
 u'7cd2c9a6-08ed-11e4-887d-928d578f5db8', details : {hypervisortoolsversion : 
 u'xenserver56'}, memory : 128, serviceofferingid : 
 u'5a70bf03-2147-4426-80a9-11d76f658c7b', zonename : u'XenRT-Zone-0', 
 isdynamicallyscalable : False, displayname : u'VM', tags : [], nic : 
 [{networkid : u'd792af3b-8e8d-4830-aa96-0933f42c71a3', macaddress : 
 u'06:95:c6:00:00:12', type : u'Shared', broadcasturi : u'vlan://untagged', 
 traffictype : u'Guest', netmask : u'255.255.240.0', ipaddress : 
 u'10.220.114.151', id : u'1ba07040-dbaa-419e-8941-a7ba6f922676', networkname 
 : u'guestNetworkForBasicZone', gateway : u'10.220.112.1', isdefault : True}], 
 cpuspeed : 100, jobstatus : 0, templateid : 
 u'b9946974-966c-4a74-8c57-c9a55e08542d', password : u'kU8pbbvtg', 
 affinitygroup : [], account : 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', hostid 
 : u'71c113f0-a559-4c9f-95b0-1bfeec463a9c', name : 
 u'VM-e391e779-2efe-4c6a-ad1f-e03d0867165f', created : 
 u'2014-07-11T16:46:43+', hypervisor : u'XenServer', jobid : 
 u'e7c495f1-6324-4253-a453-494e2a36ae02', rootdevicetype : u'ROOT', 
 rootdeviceid : 0, serviceofferingname : u'Tiny Instance', templatedisplaytext 
 : u'Cent OS Template'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Payload: {'account': 
 u'test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XD', 
 'domainid': u'7ccbf6bc-08ed-11e4-887d-928d578f5db8', 'zoneid': 
 u'ae56b8ba-3fd6-4f63-b71f-32128f86688a', 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'associateIpAddress', 'signature': 
 '52qNzGUlB0gK2dd/0r/tdZKGWaE=', 'response': 'json'}
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 DEBUG: Sending GET Cmd : associateIpAddress===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?account=test-TestResetSSHKeypair-test_01_reset_keypair_normal_user-D073XDdomainid=7ccbf6bc-08ed-11e4-887d-928d578f5db8zoneid=ae56b8ba-3fd6-4f63-b71f-32128f86688aapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=associateIpAddresssignature=52qNzGUlB0gK2dd%2F0r%2FtdZKGWaE%3Dresponse=json
  HTTP/1.1 533 129
 test_01_reset_keypair_normal_user 
 (integration.component.test_reset_ssh_keypair.TestResetSSHKeyUserRights): 
 ERROR: Exception:['Traceback (most recent call last):\n', '  File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 308, in __parseAndGetResponse\nresponse_cls)\n', '  File 
 

[jira] [Assigned] (CLOUDSTACK-7074) [Automation] [BVT] test_01_primary_storage_nfs failing during PreparePrimaryStorageForMaintenanceCmd

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7074:
--

Assignee: Gaurav Aradhye  (was: Ashutosk Kelkar)

 [Automation] [BVT] test_01_primary_storage_nfs failing during 
 PreparePrimaryStorageForMaintenanceCmd
 

 Key: CLOUDSTACK-7074
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7074
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Simulator
Affects Versions: 4.5.0
 Environment: Master - 4.5 build
 BVT run from simulator 
Reporter: Rayees Namathponnan
Assignee: Gaurav Aradhye
Priority: Blocker
 Fix For: 4.5.0

 Attachments: vmops.rar


 Steps to reproduce 
 Run BVT from simulator, test case 
 integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_nfs
  fails with below error 
 2014-07-06 23:17:10,745 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-124:ctx-fedceda0 job-223) Executing AsyncJobVO {id:223, use
 rId: 2, accountId: 2, instanceType: StoragePool, instanceId: 4, cmd: 
 org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageFor
 MaintenanceCmd, cmdInfo: 
 {response:json,id:54e824e0-8431-3e45-b35d-a4f9b547df56,ctxDetails:{\com.cloud.storage.StoragePool\:\54
 e824e0-8431-3e45-b35d-a4f9b547df56\},cmdEventType:MAINT.PREPARE.PS,ctxUserId:2,httpmethod:GET,uuid:54e824e0-8431-3e45-b35d-a
 4f9b547df56,ctxAccountId:2,ctxStartEventId:720,apiKey:XhIrLnYTF-2c2uBt22f_kAbgMMuKDbHrjPyLKSOca9k5o08kGxZiiFVG-m637OyA71QLs9MRgbK
 2twbtvYcQNg,signature:6Ppi5k2c5/wYcs3i4XmPDq1SWGc\u003d}, cmdVersion: 0, 
 status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: n
 ull, initMsid: 95530185772, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-07-06 23:17:10,746 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
 (Work-Job-Executor-72:ctx-01201e17 job-221/job-222 ctx-68ee52cf) Deployme
 ntPlanner allocation algorithm: com.cloud.deploy.FirstFitPlanner@2553e6
 2014-07-06 23:17:10,746 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
 (Work-Job-Executor-72:ctx-01201e17 job-221/job-222 ctx-68ee52cf) Trying t
 o allocate a host and storage pools from dc:1, pod:null,cluster:null, 
 requested cpu: 500, requested ram: 134217728
 2014-07-06 23:17:10,746 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
 (Work-Job-Executor-72:ctx-01201e17 job-221/job-222 ctx-68ee52cf) Is ROOT
 volume READY (pool already allocated)?: No
 2014-07-06 23:17:10,746 DEBUG [c.c.d.FirstFitPlanner] 
 (Work-Job-Executor-72:ctx-01201e17 job-221/job-222 ctx-68ee52cf) Searching 
 all possible
  resources under this Zone: 1
 2014-07-06 23:17:10,747 DEBUG [c.c.d.FirstFitPlanner] 
 (Work-Job-Executor-72:ctx-01201e17 job-221/job-222 ctx-68ee52cf) Listing 
 clusters in or
 der of aggregate capacity, that have (atleast one host with) enough CPU and 
 RAM capacity under this Zone: 1
 2014-07-06 23:17:10,749 DEBUG [c.c.a.ApiServlet] 
 (1061680681@qtp-1957555412-3:ctx-d0db1f98) ===START===  172.16.88.7 -- GET  
 jobid=6c848209-6
 f65-41cb-b80a-c62c32bce55dapiKey=XhIrLnYTF-2c2uBt22f_kAbgMMuKDbHrjPyLKSOca9k5o08kGxZiiFVG-m637OyA71QLs9MRgbK2twbtvYcQNgcommand=queryAsyncJo
 bResultresponse=jsonsignature=sxMFd6BpPKZJpsDRjRAZHif1w30%3D
 2014-07-06 23:17:10,762 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-124:ctx-fedceda0 job-223) Unexpected exception while 
 executing
 org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd
 com.cloud.exception.InvalidParameterValueException: Primary storage with id 4 
 is not ready for migration, as the status is:Maintenance
 at 
 com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:1221)
 at 
 com.cloud.storage.StorageManagerImpl.preparePrimaryStorageForMaintenance(StorageManagerImpl.java:179)
 at 
 org.apache.cloudstack.api.command.admin.storage.PreparePrimaryStorageForMaintenanceCmd.execute(PreparePrimaryStorageForMaintenance
 Cmd.java:103)
 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:507)
 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)

[jira] [Updated] (CLOUDSTACK-6680) AutoScaling without NetScaler

2014-07-24 Thread tuna (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

tuna updated CLOUDSTACK-6680:
-

Fix Version/s: (was: 4.4.0)
   Future

 AutoScaling without NetScaler
 -

 Key: CLOUDSTACK-6680
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6680
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: tuna
Assignee: tuna
 Fix For: Future


 AutoScaling without using Netscaler device. Work only with XenServer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-7138) [Automation] Fix the script test_escalations_vpncustomergateways.py - Fail to find customer gateway

2014-07-24 Thread Gaurav Aradhye (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Aradhye reassigned CLOUDSTACK-7138:
--

Assignee: Gaurav Aradhye  (was: Ashutosk Kelkar)

 [Automation] Fix the script test_escalations_vpncustomergateways.py - Fail 
 to find customer gateway
 -

 Key: CLOUDSTACK-7138
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7138
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Gaurav Aradhye
Priority: Critical
 Fix For: 4.5.0


 =
 Error Message:
 =
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: Sending GET Cmd : deleteVpnCustomerGateway===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=C%2FYs0Z0CIZwnMXhXLn3c5hUxC44%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=deleteVpnCustomerGatewayid=fd1ce29a-eba1-4933-8048-f6750144507fresponse=json
  HTTP/1.1 200 89
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: === Jobid: 65e64b4c-e08a-43f1-9c9b-6f090495d4fb Started ===
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: Payload: {'signature': 'movzhb8jh4K2t40vRU8Qfi3oR1w=', 'apiKey': 
 u'Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMA',
  'command': 'queryAsyncJobResult', 'response': 'json', 'jobid': 
 u'65e64b4c-e08a-43f1-9c9b-6f090495d4fb'}
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: Sending GET Cmd : queryAsyncJobResult===
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.220.135.73
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?signature=movzhb8jh4K2t40vRU8Qfi3oR1w%3DapiKey=Ra1mlXzCZU0K1l4MKDWdRbQDU67PCQuRnKYv3hyc-Q8hSvCSFjB32UtifLbS6oYpMeKaf0BCuUidMw0LqZeCMAcommand=queryAsyncJobResultresponse=jsonjobid=65e64b4c-e08a-43f1-9c9b-6f090495d4fb
  HTTP/1.1 200 459
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: Response : {jobprocstatus : 0, created : u'2014-07-11T16:07:31+', 
 cmd : 
 u'org.apache.cloudstack.api.command.user.vpn.DeleteVpnCustomerGatewayCmd', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 2, jobid : 
 u'65e64b4c-e08a-43f1-9c9b-6f090495d4fb', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : u'Fail to find customer 
 gateway with 3 !'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  ERROR:  __poll: Exception Occurred :Job failed: {jobprocstatus : 0, 
 created : u'2014-07-11T16:07:31+', cmd : 
 u'org.apache.cloudstack.api.command.user.vpn.DeleteVpnCustomerGatewayCmd', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 2, jobid : 
 u'65e64b4c-e08a-43f1-9c9b-6f090495d4fb', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : u'Fail to find customer 
 gateway with 3 !'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'} 
 Traceback (most recent call last):
   File 
 /local/jenkins/workspace/xenrt-reg-basic-xs/work.64/env/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 105, in __poll
 % async_response)
 Exception: Job failed: {jobprocstatus : 0, created : 
 u'2014-07-11T16:07:31+', cmd : 
 u'org.apache.cloudstack.api.command.user.vpn.DeleteVpnCustomerGatewayCmd', 
 userid : u'9f654606-08ed-11e4-887d-928d578f5db8', jobstatus : 2, jobid : 
 u'65e64b4c-e08a-43f1-9c9b-6f090495d4fb', jobresultcode : 530, jobresulttype : 
 u'object', jobresult : {errorcode : 530, errortext : u'Fail to find customer 
 gateway with 3 !'}, accountid : u'9f6536a2-08ed-11e4-887d-928d578f5db8'}
 test_01_list_vpncustomergateways_pagination 
 (integration.component.test_escalations_vpncustomergateways.TestVpnCustomerGateways):
  DEBUG: Response : FAILED
 test_01_list_vpncustomergateways_pagination 
 

[jira] [Commented] (CLOUDSTACK-6036) CloudStack stops the machine for no reason

2014-07-24 Thread Tomasz Zieba (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073335#comment-14073335
 ] 

Tomasz Zieba commented on CLOUDSTACK-6036:
--

Hello,

After a little investigation, we have some facts. Error stopping the machine is 
always associated with an entry in the logs of the content:

2014-07-24 17:00:34,918 DEBUG [vm.dao.VMInstanceDaoImpl] (HA-Worker-2:work-15) 
Unable to update VM[User|Win-HD-tune]: DB Data={Host=null; State=Stopped; 
updated=55; time=Thu Jul 24 17:00:34 CEST 2014} New Data: {Host=2; 
State=Running; updated=55; time=Thu Jul 24 17:00:34 CEST 2014} Stale Data: 
{Host=2; State=Stopping; updated=54; time=Thu Jul 24 17:00:13 CEST 2014}

and then:

2014-07-24 17:00:34,919 DEBUG [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-2:work-15) Stop was unsuccessful.  Rescheduling
2014-07-24 17:00:34,919 INFO  [cloud.ha.HighAvailabilityManagerImpl] 
(HA-Worker-2:work-15) Rescheduling HAWork[15-Stop-10-Stopping-Scheduled] to try 
again at Thu Jul 24 17:10:48 CEST 2014

After analyzing the logs of the database:

633 Query UPDATE vm_instance SET vm_instance.update_time='2014-07-24 
15:00:34', vm_instance.update_count=vm_instance.update_count+1, 
vm_instance.last_host_id=2, vm_instance.state='Stopped', 
vm_instance.host_id=null, vm_instance.pod_id=1 WHERE vm_instance.id = 10  AND 
vm_instance.state = 'Stopping'  AND vm_instance.host_id = 2  AND 
vm_instance.update_count = 54
633 Query UPDATE vm_instance SET vm_instance.update_time='2014-07-24 
15:00:34', vm_instance.update_count=vm_instance.update_count+1, 
vm_instance.state='Running', vm_instance.host_id=2, vm_instance.pod_id=1 WHERE 
vm_instance.id = 10  AND vm_instance.state = 'Stopping'  AND 
vm_instance.host_id = 2  AND vm_instance.update_count = 54

As can be seen ACS tries to update the entry twice but twice looking 
vm_instance.update_count field with a value of 54 
So the first update causes the counter vm_instance.update_count increased to 55 
so once the second SQL Update command executed incorrectly.

My guess is that the situation is related to a race condition in the HA-Worker 
threads, which by default is 5 

In the test environment, we try to change ha.workers value to 1 and we will see 
if the situation repeats itself.


  CloudStack stops the machine for no reason
 ---

 Key: CLOUDSTACK-6036
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6036
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.1
 Environment: ACS 4.2.1 after upgrade from 3.0.2
 ACS 4.2.1 clean install
 XCP 1.1
Reporter: Tomasz Zieba
Assignee: Koushik Das
Priority: Critical
  Labels: 4.5ReviewNeeded
 Fix For: 4.4.0

 Attachments: management-server.log.2014-02-19.gz, 
 management-server.log.2014-02-20.gz, management-server.log.2014-02-24.txt


 After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error 
 associated with self-stopping machine after changing the offering. 
 Steps to reproduce: 
 1. Running instance of the machine 
 2. Stop with the operating system 
 3. Change offering of machine
 4. Start the machine 
 5. Waiting for 10 minutes 
 6. CloudStack stops the machine for no reason
 7. Restart the machine 
 In the logs you can find information:
 2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
 2014-02-05 06:27:00,974 DEBUG [agent.transport.Request] 
 (DirectAgent-316:null) Seq 50-1756626952: Processing:  { Ans: , MgmtId: 
 160544475005497, via: 50, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.ClusterSyncAnswer:{_clusterId:2,_newStates:{i-41-824-VM:{t:f32a4fee-b64e-4868-9c52-2a27e32d4c0e,u:Running,v:viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4}},_isExecuted:false,result:true,wait:0}}]
  }
 2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState = 
 Running
 2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState = 
 Running
 2014-02-05 06:36:01,240 DEBUG [agent.transport.Request] 
 (HA-Worker-1:work-1511) Seq 51-1374970375: Sending  { Cmd , MgmtId: 
 160544475005497, via: 51, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-41-824-VM,wait:0}}]
  }
 2014-02-05 06:36:01,240 DEBUG [agent.transport.Request] 
 (HA-Worker-1:work-1511) Seq 51-1374970375: Executing:  { Cmd , MgmtId: 
 160544475005497, via: 51, Ver: v1, Flags: 100111, 
 

[jira] [Updated] (CLOUDSTACK-7149) Issues with deployment of Cloudstack with dvSwitch on vmware vSphere 5.5

2014-07-24 Thread Alireza Eskandari (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alireza Eskandari updated CLOUDSTACK-7149:
--

Attachment: (was: logs.txt)

 Issues with deployment of Cloudstack with dvSwitch on vmware vSphere 5.5
 

 Key: CLOUDSTACK-7149
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7149
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Install and Setup, Network 
 Controller, VMware
Affects Versions: 4.3.0
 Environment: vCenter 5.5
 2 x ESXi 5.5 as hosts
Reporter: Alireza Eskandari
Priority: Critical
  Labels: 4.3.0, dvSwitch, vmware
 Attachments: logs.txt

   Original Estimate: 336h
  Remaining Estimate: 336h

 I can't deploy Zone with vmware hypervisor on dvSwitch. After I set 
 configurations, Cloudstack starts to create Zone, Pod, cluster and etc. and 
 everything looks normal but CS could not set any configuration on dvSwitch.
 CS begins to create system VMs but after cloning of system VMs completed, CS 
 delete them because of unsuccessful dvSwitch configuration and recreate a new 
 one.
 But when I try to deploy on Standard vSwitch, everything works well without 
 problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-7149) Issues with deployment of Cloudstack with dvSwitch on vmware vSphere 5.5

2014-07-24 Thread Alireza Eskandari (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alireza Eskandari updated CLOUDSTACK-7149:
--

Description: 
I can't deploy Zone with vmware hypervisor on dvSwitch. After I set 
configurations, Cloudstack starts to create Zone, Pod, cluster and etc. and 
everything looks normal but CS could not set any configuration on dvSwitch.
CS begins to create system VMs but after cloning of system VMs completed, CS 
delete them because of unsuccessful dvSwitch configuration and recreate a new 
one.
But when I try to deploy on Standard vSwitch, everything works well without 
problem.

  was:
I can't deploy Zone with vmware hypervisor on dvSwitch. After I set 
configurations, Cloudstack starts to create Zone, Pod, cluster and etc. and 
everything looks normal but CS could not set any configuration on dvSwitch.
CS begins to create system VMs but after cloning of system VMs completed, CS 
delete them because of unsuccessful dvSwitch configuration and recreate a new 
one.
But when I try to deploy on Standard vSwitch, everything works well without 
problem.




2014-07-08 14:44:39,764 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare volume at new device 
{capacityInKB:0,key:-2,backing:{diskMode:persistent,fileName:[SharedStorageCS]
 
s-54-VM/ROOT-54-01.vmdk,datastore:{value:datastore-14,type:Datastore}},connectable:{startConnected:true,allowGuestControl:false,connected:true},controllerKey:200,unitNumber:1}
2014-07-08 14:44:39,764 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) VM s-54-VM will be started with NIC 
device type: E1000
2014-07-08 14:44:39,764 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare NIC device based on NicTO: 
{deviceId:0,networkRateMbps:-1,defaultNic:false,uuid:53f70468-065a-484b-b6b5-9148d4ea9b52,mac:02:00:16:fa:00:36,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false,name:vSwitch0,,vmwaresvs}
2014-07-08 14:44:39,773 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare network on vmwaresvs null 
with name prefix: cloud.private
2014-07-08 14:44:39,773 WARN  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Unrecognized broadcast type in 
VmwareResource, type: LinkLocal. Use vlan info from labeling: untagged
2014-07-08 14:44:39,773 INFO  [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Detected vswitch name as undefined. 
Defaulting to vSwitch0
2014-07-08 14:44:39,916 INFO  [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Network 
cloud.private.untagged.0.1-vSwitch0 is ready on vSwitch vSwitch0
2014-07-08 14:44:39,916 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Preparing NIC device on network 
cloud.private.untagged.0.1-vSwitch0
2014-07-08 14:44:39,916 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare NIC at new device 
{operation:ADD,device:{addressType:Manual,macAddress:02:00:16:fa:00:36,key:-3,backing:{network:{value:network-23,type:Network},deviceName:cloud.private.untagged.0.1-vSwitch0},connectable:{startConnected:true,allowGuestControl:true,connected:true},unitNumber:0}}
2014-07-08 14:44:39,917 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare NIC device based on NicTO: 
{deviceId:1,networkRateMbps:-1,defaultNic:false,uuid:eaa2b684-0ec0-47c2-be20-f138d0790856,ip:172.16.71.62,netmask:255.255.255.0,gateway:172.16.71.1,mac:06:fc:6e:00:00:02,broadcastType:Native,type:Management,isSecurityGroupEnabled:false,name:vSwitch0,,vmwaresvs}
2014-07-08 14:44:39,925 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare network on vmwaresvs null 
with name prefix: cloud.private
2014-07-08 14:44:39,926 INFO  [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Detected vswitch name as undefined. 
Defaulting to vSwitch0
2014-07-08 14:44:40,063 INFO  [c.c.h.v.m.HypervisorHostHelper] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Network 
cloud.private.untagged.0.1-vSwitch0 is ready on vSwitch vSwitch0
2014-07-08 14:44:40,063 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Preparing NIC device on network 
cloud.private.untagged.0.1-vSwitch0
2014-07-08 14:44:40,064 DEBUG [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare NIC at new device 
{operation:ADD,device:{addressType:Manual,macAddress:06:fc:6e:00:00:02,key:-4,backing:{network:{value:network-23,type:Network},deviceName:cloud.private.untagged.0.1-vSwitch0},connectable:{startConnected:true,allowGuestControl:true,connected:true},unitNumber:1}}
2014-07-08 14:44:40,064 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-411:ctx-86a12e4e 172.16.71.54) Prepare NIC device based on NicTO: 

[jira] [Updated] (CLOUDSTACK-7149) Issues with deployment of Cloudstack with dvSwitch on vmware vSphere 5.5

2014-07-24 Thread Alireza Eskandari (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alireza Eskandari updated CLOUDSTACK-7149:
--

Attachment: (was: logs.txt)

 Issues with deployment of Cloudstack with dvSwitch on vmware vSphere 5.5
 

 Key: CLOUDSTACK-7149
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7149
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller, Install and Setup, Network 
 Controller, VMware
Affects Versions: 4.3.0
 Environment: vCenter 5.5
 2 x ESXi 5.5 as hosts
Reporter: Alireza Eskandari
Priority: Critical
  Labels: 4.3.0, dvSwitch, vmware
 Attachments: logs.txt

   Original Estimate: 336h
  Remaining Estimate: 336h

 I can't deploy Zone with vmware hypervisor on dvSwitch. After I set 
 configurations, Cloudstack starts to create Zone, Pod, cluster and etc. and 
 everything looks normal but CS could not set any configuration on dvSwitch.
 CS begins to create system VMs but after cloning of system VMs completed, CS 
 delete them because of unsuccessful dvSwitch configuration and recreate a new 
 one.
 But when I try to deploy on Standard vSwitch, everything works well without 
 problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7053) [Automation] Tasks for writing automated test cases for few product bugs

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073578#comment-14073578
 ] 

ASF subversion and git services commented on CLOUDSTACK-7053:
-

Commit 59f25d243661cf4bd058482e1f0f14f008a93bd5 in cloudstack's branch 
refs/heads/master from SrikanteswaraRao Talluri
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=59f25d2 ]

CLOUDSTACK-7053: automated tests for 4.2.x bugs- management server components


 [Automation] Tasks for writing automated test cases for few product bugs
 

 Key: CLOUDSTACK-7053
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7053
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.5.0
Reporter: Srikanteswararao Talluri
Assignee: Srikanteswararao Talluri
 Fix For: 4.5.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-6815) CallContext contains incorrect UUID for Account

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk reassigned CLOUDSTACK-6815:
-

Assignee: Alena Prokharchyk

 CallContext contains incorrect UUID for Account
 ---

 Key: CLOUDSTACK-6815
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6815
 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: Ubuntu 12.04
Reporter: Mike Tutkowski
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 Copy/paste of an e-mail I sent to CloudStack dev@:
 Hi,
 I noticed while executing the createStoragePool command that the following 
 does not work entirely as expected:
 Account csAccount = CallContext.current().getCallingAccount();
 The Account that is returned has the expected name and id, but its UUID is 
 not correct.
 For example, I see the account name of admin and an id of 2 (in my case, 
 both are correct); however, the UUID is different each time I run the 
 createStoragePool command.
 I assume the UUID should be what's in the account table for the applicable 
 row, right?
 Anyone have any thoughts on this?
 Thanks!



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk reassigned CLOUDSTACK-4322:
-

Assignee: Alena Prokharchyk

 Delete domain with force option is not returning failed as response incase of 
 accounts under that domain needs cleanup.
 ---

 Key: CLOUDSTACK-4322
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
Reporter: Sanjay Tripathi
Assignee: Alena Prokharchyk
 Fix For: 4.5.0

 Attachments: DomainDeleteFailed_logs.txt, del_domain_fail.JPG


 deleteDomain with cleanup = true, CS is not allowing deletion of domain if 
 there is any account under that domain needs clean up; though these accounts 
 are removed and admin can't see them in the listaccounts call. 
 From the end user perspective, CS should return success in case of force 
 delete domain and handle the cleanup of sub-domains/accounts internally.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-4451) associateIPaddress requires zone id but apidoc says it's optional

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk updated CLOUDSTACK-4451:
--

Fix Version/s: (was: Future)
   4.5.0

 associateIPaddress requires zone id but apidoc says it's optional
 -

 Key: CLOUDSTACK-4451
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 apidoc for associateIPaddress says that zone id is optional:
 http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
 but it's required:
 Try calling it with cloudmonkey without any arguments.
 Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': 
 [], u'errortext': u'Unable to figure out zone to assign ip to'}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk updated CLOUDSTACK-4322:
--

Fix Version/s: (was: Future)
   4.5.0

 Delete domain with force option is not returning failed as response incase of 
 accounts under that domain needs cleanup.
 ---

 Key: CLOUDSTACK-4322
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
Reporter: Sanjay Tripathi
Assignee: Alena Prokharchyk
 Fix For: 4.5.0

 Attachments: DomainDeleteFailed_logs.txt, del_domain_fail.JPG


 deleteDomain with cleanup = true, CS is not allowing deletion of domain if 
 there is any account under that domain needs clean up; though these accounts 
 are removed and admin can't see them in the listaccounts call. 
 From the end user perspective, CS should return success in case of force 
 delete domain and handle the cleanup of sub-domains/accounts internally.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-4451) associateIPaddress requires zone id but apidoc says it's optional

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk reassigned CLOUDSTACK-4451:
-

Assignee: Alena Prokharchyk

 associateIPaddress requires zone id but apidoc says it's optional
 -

 Key: CLOUDSTACK-4451
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 apidoc for associateIPaddress says that zone id is optional:
 http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
 but it's required:
 Try calling it with cloudmonkey without any arguments.
 Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': 
 [], u'errortext': u'Unable to figure out zone to assign ip to'}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6815) CallContext contains incorrect UUID for Account

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-6815.
---

Resolution: Cannot Reproduce

Mike, I can't reproduce it. I assume you observed the problem in 
SolidFireSharedPrimaryDataStoreLifeCycle class, createSolidFireVolume method? I 
couldn't exercise this call, what I did was:

* copy pasted the line below to the StorageManagerImpl, createPool method:
Account csAccount = CallContext.current().getCallingAccount();

Attached the debugger to see what csAccount.getUuid() returns, and it always 
returned the UUID of the account taken from cloud.account table. And it was 
consistent for the several calls I've executed.

 CallContext contains incorrect UUID for Account
 ---

 Key: CLOUDSTACK-6815
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6815
 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: Ubuntu 12.04
Reporter: Mike Tutkowski
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 Copy/paste of an e-mail I sent to CloudStack dev@:
 Hi,
 I noticed while executing the createStoragePool command that the following 
 does not work entirely as expected:
 Account csAccount = CallContext.current().getCallingAccount();
 The Account that is returned has the expected name and id, but its UUID is 
 not correct.
 For example, I see the account name of admin and an id of 2 (in my case, 
 both are correct); however, the UUID is different each time I run the 
 createStoragePool command.
 I assume the UUID should be what's in the account table for the applicable 
 row, right?
 Anyone have any thoughts on this?
 Thanks!



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-4322.
---

Resolution: Not a Problem

 Delete domain with force option is not returning failed as response incase of 
 accounts under that domain needs cleanup.
 ---

 Key: CLOUDSTACK-4322
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
Reporter: Sanjay Tripathi
Assignee: Alena Prokharchyk
 Fix For: 4.5.0

 Attachments: DomainDeleteFailed_logs.txt, del_domain_fail.JPG


 deleteDomain with cleanup = true, CS is not allowing deletion of domain if 
 there is any account under that domain needs clean up; though these accounts 
 are removed and admin can't see them in the listaccounts call. 
 From the end user perspective, CS should return success in case of force 
 delete domain and handle the cleanup of sub-domains/accounts internally.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-4322) Delete domain with force option is not returning failed as response incase of accounts under that domain needs cleanup.

2014-07-24 Thread Alena Prokharchyk (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073636#comment-14073636
 ] 

Alena Prokharchyk commented on CLOUDSTACK-4322:
---

In the context of deleteDomain call, force option doesn't mean that the 
domain will be removed even if corresponding details cleanup fails. It means 
that as a part of the call, we attempt to cleanup the resources of the domain. 
Here is what API doc says:

@Parameter(name = ApiConstants.CLEANUP,
   type = CommandType.BOOLEAN,
   description = true if all domain resources (child domains, 
accounts) have to be cleaned up, false otherwise)

If something fails along the way in the domain clenaup process, it will be left 
in Inactive state till account/domain cleanup process will attempt  to clenaup 
again (this task runs periodically). Only after cleanup is successful, the 
domain resource will be marked as removed.



 Delete domain with force option is not returning failed as response incase of 
 accounts under that domain needs cleanup.
 ---

 Key: CLOUDSTACK-4322
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4322
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.0, 4.2.0
Reporter: Sanjay Tripathi
Assignee: Alena Prokharchyk
 Fix For: 4.5.0

 Attachments: DomainDeleteFailed_logs.txt, del_domain_fail.JPG


 deleteDomain with cleanup = true, CS is not allowing deletion of domain if 
 there is any account under that domain needs clean up; though these accounts 
 are removed and admin can't see them in the listaccounts call. 
 From the end user perspective, CS should return success in case of force 
 delete domain and handle the cleanup of sub-domains/accounts internally.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-4451) associateIPaddress requires zone id but apidoc says it's optional

2014-07-24 Thread Alena Prokharchyk (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073638#comment-14073638
 ] 

Alena Prokharchyk commented on CLOUDSTACK-4451:
---

ZoneId is not required because it can be derived from the objects retrieved by 
passing networkId/vpcId to the associateIpAddress call. If those parameters are 
not passed, then the zoneId is required. 

I'm going to update the error message from 'Unable to figure out zone to 
assign ip to' to Unable to figure out zone to assign ip to. Please specify 
either zoneId, or networkId, or vpcId in the call'

 associateIPaddress requires zone id but apidoc says it's optional
 -

 Key: CLOUDSTACK-4451
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 apidoc for associateIPaddress says that zone id is optional:
 http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
 but it's required:
 Try calling it with cloudmonkey without any arguments.
 Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': 
 [], u'errortext': u'Unable to figure out zone to assign ip to'}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-4451) associateIPaddress requires zone id but apidoc says it's optional

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073652#comment-14073652
 ] 

ASF subversion and git services commented on CLOUDSTACK-4451:
-

Commit e15c20ec056df568d8c406370a708e80e9d8 in cloudstack's branch 
refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e15c20e ]

CLOUDSTACK-4451: more descriptive error message to associateIpAddress API call 
identifying why zoneId can't be figured out


 associateIPaddress requires zone id but apidoc says it's optional
 -

 Key: CLOUDSTACK-4451
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 apidoc for associateIPaddress says that zone id is optional:
 http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
 but it's required:
 Try calling it with cloudmonkey without any arguments.
 Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': 
 [], u'errortext': u'Unable to figure out zone to assign ip to'}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-4451) associateIPaddress requires zone id but apidoc says it's optional

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-4451.
---

Resolution: Fixed

Fixed with e15c20ec056df568d8c406370a708e80e9d8

 associateIPaddress requires zone id but apidoc says it's optional
 -

 Key: CLOUDSTACK-4451
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Assignee: Alena Prokharchyk
 Fix For: 4.5.0


 apidoc for associateIPaddress says that zone id is optional:
 http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
 but it's required:
 Try calling it with cloudmonkey without any arguments.
 Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': 
 [], u'errortext': u'Unable to figure out zone to assign ip to'}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-3414) Physical Netwok traffic lable update requires Management Server restart

2014-07-24 Thread Alena Prokharchyk (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073668#comment-14073668
 ] 

Alena Prokharchyk commented on CLOUDSTACK-3414:
---

Reassigning the bug to the UI team. UI should throw a notification that MS 
should be restarted after physical network label gets changed.

 Physical Netwok traffic lable update requires Management Server restart 
 

 Key: CLOUDSTACK-3414
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3414
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
 Fix For: Future


 Setup :  VMWARE Adv Zone. 
 Note: This issue may not be specific to VMWARE
 Steps:
 1. Tried to configure Adv Zone with VMWARE 
 2. Configure Physical network 1 with Management Traffic with invalid traffic 
 label ( Ex: vSwitch0,,vmwaresvs) 
 3. Configure Physical network 2 with public  guest Traffic with correct 
 DVSwitch traffic label ( Ex: newdv1,,vmwaredvs) 
 4. Now System VM's  are failed to start as it failed to create network for 
 Mgmt traffic.
 2013-07-09 14:00:50,521 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Prepare NIC device based on NicTO: 
 {deviceId:0,networkRateMbps:-1,defaultNic:false,uuid:789e034d-e287-4389-beac-29a10326c0ea,mac:02:00:41:48:00:05,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false}
 2013-07-09 14:00:50,525 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Prepare network on vmwaresvs 
 P[vSwitch0,,vmwaresvs:untagged] with name prefix: cloud.private
 2013-07-09 14:00:50,525 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Unrecognized broadcast type in VmwareResource, 
 type: LinkLocal. Use vlan info from labeling: untagged
 2013-07-09 14:00:50,552 ERROR [vmware.mo.HypervisorHostHelper] 
 (DirectAgent-7:10.102.192.18) Unable to find vSwitchvSwitch0,,vmwaresvs
 2013-07-09 14:00:50,553 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) StartCommand failed due to Exception: 
 java.lang.Exception
 Message: Unable to find vSwitchvSwitch0,,vmwaresvs
 java.lang.Exception: Unable to find vSwitchvSwitch0,,vmwaresvs
 at 
 com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-09 14:00:50,556 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-7:null) Seq 1-763953202: Cancelling because one of the answers 
 is false and it is stop on error.
 2013-07-09 14:00:50,557 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-7:null) Seq 1-763953202: Response Received:
 6. Now updated Mgmt traffic label to vSwitch0. 
 7. DB got updated automatically .
 8. But System Vm's are still failed to start with this 
 9. Restarted Management server (server cloudstack-management stop/ start)
 10. Now system VM's are up with network name vSwitch0.
 Expected results :
 1. Changes to Physical network traffic labels should be dynamic, 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-3414) Physical Netwok traffic lable update requires Management Server restart

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk updated CLOUDSTACK-3414:
--

Component/s: (was: Management Server)
 UI
 Doc

 Physical Netwok traffic lable update requires Management Server restart 
 

 Key: CLOUDSTACK-3414
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3414
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
 Fix For: Future


 Setup :  VMWARE Adv Zone. 
 Note: This issue may not be specific to VMWARE
 Steps:
 1. Tried to configure Adv Zone with VMWARE 
 2. Configure Physical network 1 with Management Traffic with invalid traffic 
 label ( Ex: vSwitch0,,vmwaresvs) 
 3. Configure Physical network 2 with public  guest Traffic with correct 
 DVSwitch traffic label ( Ex: newdv1,,vmwaredvs) 
 4. Now System VM's  are failed to start as it failed to create network for 
 Mgmt traffic.
 2013-07-09 14:00:50,521 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Prepare NIC device based on NicTO: 
 {deviceId:0,networkRateMbps:-1,defaultNic:false,uuid:789e034d-e287-4389-beac-29a10326c0ea,mac:02:00:41:48:00:05,broadcastType:LinkLocal,type:Control,isSecurityGroupEnabled:false}
 2013-07-09 14:00:50,525 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Prepare network on vmwaresvs 
 P[vSwitch0,,vmwaresvs:untagged] with name prefix: cloud.private
 2013-07-09 14:00:50,525 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) Unrecognized broadcast type in VmwareResource, 
 type: LinkLocal. Use vlan info from labeling: untagged
 2013-07-09 14:00:50,552 ERROR [vmware.mo.HypervisorHostHelper] 
 (DirectAgent-7:10.102.192.18) Unable to find vSwitchvSwitch0,,vmwaresvs
 2013-07-09 14:00:50,553 WARN  [vmware.resource.VmwareResource] 
 (DirectAgent-7:10.102.192.18) StartCommand failed due to Exception: 
 java.lang.Exception
 Message: Unable to find vSwitchvSwitch0,,vmwaresvs
 java.lang.Exception: Unable to find vSwitchvSwitch0,,vmwaresvs
 at 
 com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2013-07-09 14:00:50,556 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-7:null) Seq 1-763953202: Cancelling because one of the answers 
 is false and it is stop on error.
 2013-07-09 14:00:50,557 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-7:null) Seq 1-763953202: Response Received:
 6. Now updated Mgmt traffic label to vSwitch0. 
 7. DB got updated automatically .
 8. But System Vm's are still failed to start with this 
 9. Restarted Management server (server cloudstack-management stop/ start)
 10. Now system VM's are up with network name vSwitch0.
 Expected results :
 1. Changes to Physical network traffic labels should be dynamic, 



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-2575) Change Network ACL API name

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk resolved CLOUDSTACK-2575.
---

Resolution: Won't Fix

 Change Network ACL API name
 ---

 Key: CLOUDSTACK-2575
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2575
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
 Fix For: Future


 createNetworkACL, listNetworkACLs and deleteNetworkACL APIs actually create 
 ACL items and not the list (container). These APIs need to be deprecated and 
 replaced with following APIs
 createNetworkACLItem, listNetworkACLItems and deleteNetworkACLItem
 related Doc:
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+deny+rules



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-2575) Change Network ACL API name

2014-07-24 Thread Alena Prokharchyk (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073673#comment-14073673
 ] 

Alena Prokharchyk commented on CLOUDSTACK-2575:
---

-1 from me as well. We should leave the names as they are for backwards 
compatibility, and just make sure that the documentation explains the API use 
well. 

 Change Network ACL API name
 ---

 Key: CLOUDSTACK-2575
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2575
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
 Fix For: Future


 createNetworkACL, listNetworkACLs and deleteNetworkACL APIs actually create 
 ACL items and not the list (container). These APIs need to be deprecated and 
 replaced with following APIs
 createNetworkACLItem, listNetworkACLItems and deleteNetworkACLItem
 related Doc:
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+deny+rules



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-2663) request for adding networkupgrade support to shared network

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk updated CLOUDSTACK-2663:
--

Issue Type: New Feature  (was: Improvement)

 request for adding networkupgrade support to shared network 
 

 Key: CLOUDSTACK-2663
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2663
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Reporter: sadhu suresh
Priority: Minor
 Fix For: Future


 In case of shared networks, there is no support for network upgrade.Right now 
  this support applicable to isolated networks  .
  when we try to upgrade the networking offering its failing  with below  
 message
 http://10.147.59.194:8096/client/api?command=updateNetworkid=221networkofferingid=ecef78b3-01d7-4730-9560-13eac7195c4fchangecidr=falseresponse=xml
 NetworkOffering and domain suffix upgrade can be perfomed for Isolated 
 networks only
 It will be good ,if we add this support in future.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-3621) NPE when registering an invalid template

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk updated CLOUDSTACK-3621:
--

Fix Version/s: (was: Future)
   4.5.0

 NPE when registering an invalid template
 

 Key: CLOUDSTACK-3621
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3621
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: Future
Reporter: Prasanna Santhanam
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.5.0


 Used an invalid uuid in the registerTemplate call and ended up with the 
 following NPE
 2013-07-18 10:14:03,235 DEBUG [cloud.api.ApiDispatcher] 
 (ApiServer-7:ctx-eb976040) Object entity uuid = 
 bb62589e-e3cd-11e2-ad39-ea6434daa8ba does not exist in the database.
 2013-07-18 10:14:03,235 INFO  [cloud.api.ApiServer] 
 (ApiServer-7:ctx-eb976040) Unable to execute API command registertemplate due 
 to invalid value. Invalid parameter ostypeid 
 value=bb62589e-e3cd-11e2-ad39-ea6434daa8ba due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.
 2013-07-18 10:14:03,236 DEBUG [cloudstack.context.CallContext] 
 (ApiServer-7:ctx-eb976040) Context removed CallContext[acct=1; user=1; 
 session=eb976040-e59d-437a-ba25-eda9a4075286]
 2013-07-18 10:14:11,625 DEBUG [cloudstack.context.CallContext] 
 (ApiServer-8:ctx-809a4f40) Setting calling context: CallContext[acct=1; 
 user=1; session=809a4f40-37e6-42a2-bce7-373985d7870a]
 2013-07-18 10:14:11,640 ERROR [cloud.api.ApiServer] 
 (ApiServer-8:ctx-809a4f40) unhandled exception executing api command: 
 registerTemplate
 java.lang.NullPointerException
 at 
 com.cloud.template.TemplateAdapterBase.prepare(TemplateAdapterBase.java:128)
 at 
 com.cloud.template.TemplateAdapterBase.prepare(TemplateAdapterBase.java:235)
 at 
 com.cloud.template.HypervisorTemplateAdapter.prepare(HypervisorTemplateAdapter.java:112)
 at 
 com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:345)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.RegisterTemplateCmd.execute(RegisterTemplateCmd.java:245)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:532)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:376)
 at com.cloud.api.ApiServer.handle(ApiServer.java:307)
 at org.apache.http.protocol.HttpService.doService(HttpService.java:375)
 at 
 org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290)
 at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:994)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
 at java.lang.Thread.run(Thread.java:680)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-3621) NPE when registering an invalid template

2014-07-24 Thread Alena Prokharchyk (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alena Prokharchyk reassigned CLOUDSTACK-3621:
-

Assignee: Alena Prokharchyk

 NPE when registering an invalid template
 

 Key: CLOUDSTACK-3621
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3621
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: Future
Reporter: Prasanna Santhanam
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.5.0


 Used an invalid uuid in the registerTemplate call and ended up with the 
 following NPE
 2013-07-18 10:14:03,235 DEBUG [cloud.api.ApiDispatcher] 
 (ApiServer-7:ctx-eb976040) Object entity uuid = 
 bb62589e-e3cd-11e2-ad39-ea6434daa8ba does not exist in the database.
 2013-07-18 10:14:03,235 INFO  [cloud.api.ApiServer] 
 (ApiServer-7:ctx-eb976040) Unable to execute API command registertemplate due 
 to invalid value. Invalid parameter ostypeid 
 value=bb62589e-e3cd-11e2-ad39-ea6434daa8ba due to incorrect long value 
 format, or entity does not exist or due to incorrect parameter annotation for 
 the field in api cmd class.
 2013-07-18 10:14:03,236 DEBUG [cloudstack.context.CallContext] 
 (ApiServer-7:ctx-eb976040) Context removed CallContext[acct=1; user=1; 
 session=eb976040-e59d-437a-ba25-eda9a4075286]
 2013-07-18 10:14:11,625 DEBUG [cloudstack.context.CallContext] 
 (ApiServer-8:ctx-809a4f40) Setting calling context: CallContext[acct=1; 
 user=1; session=809a4f40-37e6-42a2-bce7-373985d7870a]
 2013-07-18 10:14:11,640 ERROR [cloud.api.ApiServer] 
 (ApiServer-8:ctx-809a4f40) unhandled exception executing api command: 
 registerTemplate
 java.lang.NullPointerException
 at 
 com.cloud.template.TemplateAdapterBase.prepare(TemplateAdapterBase.java:128)
 at 
 com.cloud.template.TemplateAdapterBase.prepare(TemplateAdapterBase.java:235)
 at 
 com.cloud.template.HypervisorTemplateAdapter.prepare(HypervisorTemplateAdapter.java:112)
 at 
 com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:345)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.template.RegisterTemplateCmd.execute(RegisterTemplateCmd.java:245)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:532)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:376)
 at com.cloud.api.ApiServer.handle(ApiServer.java:307)
 at org.apache.http.protocol.HttpService.doService(HttpService.java:375)
 at 
 org.apache.http.protocol.HttpService.handleRequest(HttpService.java:290)
 at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:994)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
 at java.lang.Thread.run(Thread.java:680)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Rayees Namathponnan (JIRA)
Rayees Namathponnan created CLOUDSTACK-7179:
---

 Summary: [Automation] Router deployment failing while calling 
patchviasocket.pl during router configuration
 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.5.0


This issue is observed in automation environment, there are many router 
deployment failure, this issue observed while programming patchviasocket.pl

2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Executing: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
r-384-VM -p 
%template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
2014-07-23 22:50:24,973 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
2014-07-23 22:50:27,974 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) Could not connect to 169.254.3.89
2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
(Script-7:null) Interrupting script.
2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) Timed out: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
r-384-VM -p 
%template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 .  Output is:
2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) passcmd failed:timeout





2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Request:Seq 1-586986832060423:  { Cmd , MgmtId: 29066118877352, via: 1, 
Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
 }
2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Processing command: com.cloud.agent.api.StopCommand
2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
continue
2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
continue
2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
use the default hypervisor
2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-3:null) Failed to get vm status in case of 
checkboforecleanup is true
org.libvirt.LibvirtException: Domain not found: no domain with matching name 
'r-384-VM'
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.domainLookupByName(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
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:722)
2014-07-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
continue




2014-07-23 22:52:56,334 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
continue
2014-07-23 22:52:56,334 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
use the default hypervisor
2014-07-23 22:52:56,336 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-3:null) Failed to get 

[jira] [Updated] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-7179:
---

Assignee: edison su

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.domainLookupByName(Unknown Source)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,334 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073721#comment-14073721
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7179:
-

Logs are in https://citrix.sharefile.com/d/s8cc32aac0354ae48

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.domainLookupByName(Unknown Source)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 

[jira] [Resolved] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi resolved CLOUDSTACK-6464.


Resolution: Fixed

Resolving based on commits

 [KVM:basic zone- upgrade to  4.3],after   any vm restart,all the nics  are 
 plugged to default bridge even though trafiic labels are being used
 --

 Key: CLOUDSTACK-6464
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6464
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: sadhu suresh
Priority: Critical
 Fix For: 4.4.0, 4.3.1


  Steps:
 1. create a KVM basic zone with 2 nics on host (pre 4.3 build)
 2.use cloudbr0 for management and cloudbr1 for guest by specifying the 
 traffic labels in the physical networks.
 3.deploy few vms
 4.upgrade to felton GA build as per the Upgrade instructions.
 actual result:
 Upgrade successful but all the vnets that were attached to cloudbr1 before 
 upgrade are attached to cloudbr0.
 Due to this network connectivity is lost.
 Expected result:
 Even after upgrade ,all the vnets should be attached to the same bridge as 
 before upgrade.
 ex:
 before Upgrade : this vms(i-5-616-VM) nic was attached to cloudbr1 and after 
 upgrade and VM stop/start.
 the network rules are getting programmed in cloudbr0 .check below output
 ,984 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-2:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
 default_network_rules --vmname i-5-616-VM --vmid 616 --vmip 10.x.x245 --vmmac 
 06:14:48:00:00:7f --vif vnet15 --brname cloudbr0 --nicsecips 0:
 dumpxml output for i-5-616-VM after upgrade( after VM restart)
 *
 virsh # dumpxml 38
 domain type='kvm' id='38'
 namei-5-616-VM/name
 uuid87557942-1393-49b3-a73e-ae24c40541d1/uuid
 descriptionOther CentOS (64-bit)/description
 memory unit='KiB'2097152/memory
 currentMemory unit='KiB'2097152/currentMemory
 vcpu placement='static'1/vcpu
 cputune
 shares1000/shares
 /cputune
 os
 type arch='x86_64' machine='rhel6.2.0'hvm/type
 boot dev='cdrom'/
 boot dev='hd'/
 /os
 features
 acpi/
 apic/
 pae/
 /features
 cpu
 /cpu
 clock offset='utc'/
 on_poweroffdestroy/on_poweroff
 on_rebootrestart/on_reboot
 on_crashdestroy/on_crash
 devices
 emulator/usr/libexec/qemu-kvm/emulator
 disk type='file' device='disk'
 driver name='qemu' type='qcow2' cache='none'/
 source 
 file='/mnt/041e5d8e-d9c1-346d-aea9-cd9c7b80a211/75544e9d-a4c9-4a94-943e-b20827676a27'/
 target dev='hda' bus='ide'/
 alias name='ide0-0-0'/
 address type='drive' controller='0' bus='0' target='0' unit='0'/
 /disk
 disk type='file' device='cdrom'
 driver name='qemu' type='raw' cache='none'/
 target dev='hdc' bus='ide'/
 readonly/
 alias name='ide0-1-0'/
 address type='drive' controller='0' bus='1' target='0' unit='0'/
 /disk
 controller type='usb' index='0'
 alias name='usb0'/
 address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/
 /controller
 controller type='ide' index='0'
 alias name='ide0'/
 address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/
 /controller
 interface type='bridge'
 mac address='06:14:48:00:00:7f'/
 source bridge='cloudbr0'/
 target dev='vnet15'/
 model type='e1000'/
 bandwidth
 inbound average='25600' peak='25600'/
 outbound average='25600' peak='25600'/
 /bandwidth
 alias name='net0'/
 address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/
 /interface
 serial type='pty'
 source path='/dev/pts/12'/
 target port='0'/
 alias name='serial0'/
 /serial
 console type='pty' tty='/dev/pts/12'
 source path='/dev/pts/12'/
 target type='serial' port='0'/
 alias name='serial0'/
 /console
 input type='tablet' bus='usb'
 alias name='input0'/
 /input
 input type='mouse' bus='ps2'/
 graphics type='vnc' port='5912' autoport='yes' listen='10.x.x.3'
 listen type='address' address='10.147.37.3'/
 /graphics
 video
 model type='cirrus' vram='9216' heads='1'/
 alias name='video0'/
 address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/
 /video
 memballoon model='virtio'
 alias name='balloon0'/
 address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/
 /memballoon
 /devices
 seclabel type='none'/
 /domain
 its also applicable to new vm deployments.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6882) Doc generator should be generate doc for plugins

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6882:
---

Priority: Major  (was: Critical)

 Doc generator should be generate doc for plugins 
 -

 Key: CLOUDSTACK-6882
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6882
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Doc
Reporter: Rayees Namathponnan
 Fix For: 4.4.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7173) Resizing of data volume is throwing java NPE

2014-07-24 Thread Animesh Chaturvedi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073725#comment-14073725
 ] 

Animesh Chaturvedi commented on CLOUDSTACK-7173:


MikeT I see a commit from you in related area, could this be a regression?

 Resizing of data volume is throwing java NPE
 

 Key: CLOUDSTACK-7173
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7173
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.5.0
Reporter: shweta agarwal
Priority: Critical
 Fix For: 4.5.0

 Attachments: log.tar.gz


 Repro steps :
 1. Create a Vm  with data disk
 2 . try to resize the data disk
 Bug :
 Resize will fail Ms log shows :
 2014-07-23 05:34:53,366 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-5:ctx-2f1038c6 job-300/job-301) Unable to complete 
 AsyncJobVO {id:301, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.storage.VmWorkResizeVolume, cmdInfo: 
 rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtSZXNpemVWb2x1bWVU03zH0Fe-ggIAB0oAC2N1cnJlbnRTaXplSgAHbmV3U2l6ZVoACHNocmlua09rSgAIdm9sdW1lSWRMAApuZXdNYXhJb3BzdAAQTGphdmEvbGFuZy9Mb25nO0wACm5ld01pbklvcHNxAH4AAUwAFG5ld1NlcnZpY2VPZmZlcmluZ0lkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACACZ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbAFABQAAACtwcHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAABA,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 233845177509765, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Wed Jul 23 05:34:53 EDT 2014}, job origin:300
 java.lang.NullPointerException
 at 
 com.cloud.storage.VmWorkResizeVolume.getNewMinIops(VmWorkResizeVolume.java:59)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateResizeVolume(VolumeApiServiceImpl.java:2630)
 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 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
 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.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 $Proxy183.handleVmWorkJob(Unknown Source)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:507)
 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:464)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 

[jira] [Updated] (CLOUDSTACK-6169) assignVirtualMachine leaves associated tags assigned to old account

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6169:
---

Assignee: Prachi Damle

 assignVirtualMachine leaves associated tags assigned to old account
 ---

 Key: CLOUDSTACK-6169
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6169
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0, 4.3.0, 4.4.0
Reporter: Marcus Sorensen
Assignee: Prachi Damle
 Fix For: 4.4.0


 I'm not 100% sure this is a bug, but it seems so. If you move a virtual 
 machine between accounts via 'assignVirtualMachine', then list the virtual 
 machine, any associated resource tags show the old account/domainid. This is 
 confusing, but could also be a bad information leak



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-5991) [UI]Infinite scrolling should be enabled to the Ldap user add page

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-5991:
---

Issue Type: Improvement  (was: Bug)

 [UI]Infinite scrolling should be enabled to the Ldap user add page
 --

 Key: CLOUDSTACK-5991
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5991
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.3.0
Reporter: Kiran Koneti
  Labels: Ldap
 Fix For: 4.4.0

 Attachments: LDAP_Loading.jpg


 I have added 1 users to the Ldap server and when i try to add the users 
 to the CS and click the Add Ldap User button in the UI it is atking too long 
 time to respond as it is waiting for all the users to load and finally a 
 warning is given by the browser saying the web page was not responsive.To 
 aviod this we can enable the infinite scrolling to this page which will 
 resolve the problem.
 Attaching the Screenshot for further reference.
 To navigate to the Add ldap page the path is as below:
 defaultpage--Accounts--Add LdapAccount.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6225) resize volume fails on CentOS 6, Ubuntu 12.04

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi resolved CLOUDSTACK-6225.


Resolution: Fixed

Resolving based on commits from Marcus

 resize volume fails on CentOS 6, Ubuntu 12.04
 -

 Key: CLOUDSTACK-6225
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6225
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.4.0
Reporter: Marcus Sorensen
 Fix For: 4.4.0


 Libvirt  1.1.0 does not support the resize flag 1 
 (VIR_STORAGE_VOL_RESIZE_ALLOCATE), this affects CentOS 6.5 and older. I'm 
 patching this now.
 The libvirt that ships with Ubuntu 12.04 does not support resizing at all. Or 
 rather, 'virsh' does, but /usr/lib/libvirt.so.0.9.8 does not implement 
 resize. We need to discuss our ongoing support for older Ubuntu versions.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6829) [UI]If no storage is available for migrate volume UI should popup no storage available if you try to migrate volume

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6829:
---

Assignee: Jessica Wang

 [UI]If no storage is available for migrate volume UI should popup no storage 
 available if you try to migrate volume
 -

 Key: CLOUDSTACK-6829
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6829
 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: prashant kumar mishra
Assignee: Jessica Wang
 Fix For: 4.4.0

 Attachments: screenshot-1.jpg


 if no storage is available for migration , UI should pop up same message 
 instead empty drop down list .  
 steps to repo
 ===
 1-prepare a CS setup with one primary storage
 2-create a volume and attach to vm
 3-and attach to vm
 4-try to migrate volume
 Expected
 ===
 since there is no other storage UI should pop up no storage available
 Actual
 ==
 UI popup show drop down list of storage with nothing in list 
 API
 
 http://10.147.38.181:8080/client/api?command=findStoragePoolsForMigrationid=bbedf40d-d2da-40e4-b0d3-55e4a70682d8response=jsonsessionkey=%2B3QBQd4DLtoNPX9sZ%2FfZu2GNiJ8%3D_=1401779685525
 response 
 
 { findstoragepoolsformigrationresponse : { } }



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6826) Ability to gracefully expire urls and clean them up when ssvm is destroyed

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6826:
---

Assignee: Nitin Mehta

 Ability to gracefully expire urls and clean them up when ssvm is destroyed
 --

 Key: CLOUDSTACK-6826
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6826
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.5.0


 There should be ability to gracefully expire urls and clean them up before 
 ssvm is destroyed. Currently ssvm can be destroyed even if the agent is in 
 alert state. Also the cleanup mechanism needs to be enahanced to take care of 
 multiple ssvms and sending the cleaning up command to the right ssvm.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6705) [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6705:
---

Assignee: Murali Reddy

 [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range
 

 Key: CLOUDSTACK-6705
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6705
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Network Controller
Affects Versions: 4.4.0
 Environment: Latest build from 4.4 branch with commit 
 e6961fd21bb6d793302c234d0f409f66dc498072
Reporter: Sanjeev N
Assignee: Murali Reddy
 Fix For: 4.4.0


 [SDN] VNI range is not allowing more than 2147483647 as a maximum vnet range
 1.Bring up CS in advanced zone
 2.Create physical network with GRE isolation
 3.In guest network creation give vnet/vni range as 1-4294967295
 Result:
 ==
 Failed to add above vnet range.
 2014-05-19 10:37:40,383 WARN  [c.c.n.NetworkServiceImpl] 
 (API-Job-Executor-27:job-31 ctx-ff496cfb) Unable to parse vnet range:
 java.lang.NumberFormatException: For input string: 4294967100
 at 
 java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
 at java.lang.Integer.parseInt(Integer.java:495)
 at java.lang.Integer.parseInt(Integer.java:527)
 at 
 com.cloud.network.NetworkServiceImpl.validateVlanRange(NetworkServiceImpl.java:2749)
 at 
 com.cloud.network.NetworkServiceImpl.addOrRemoveVnets(NetworkServiceImpl.java:2640)
 at 
 com.cloud.network.NetworkServiceImpl.updatePhysicalNetwork(NetworkServiceImpl.java:2622)
 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 
 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 com.sun.proxy.$Proxy154.updatePhysicalNetwork(Unknown Source)
 at 
 org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd.execute(UpdatePhysicalNetworkCmd.java:99)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:119)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
 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 
 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:453)
 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-19 10:37:40,394 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-27:job-31) Unexpected exception while executing 
 

[jira] [Updated] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure Unexpected exception

2014-07-24 Thread Animesh Chaturvedi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Animesh Chaturvedi updated CLOUDSTACK-6772:
---

Assignee: Jessica Wang

 [UI]need to change popup message  fo Attach volume failure  Unexpected 
 exception
 --

 Key: CLOUDSTACK-6772
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6772
 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: prashant kumar mishra
Assignee: Jessica Wang
Priority: Minor
 Fix For: 4.4.0

 Attachments: management-server.log


 step to reproduce
 ==
 1-tried to attach a volume( size available  size on PS)
 2-Attach volume failed 
 3-UI pop up a message  Unexpected exception
 Expected
 ===
 we should clearly pop up message like  no suitable primary storage found
 Logs
 
 2014-05-27 10:01:51,360 DEBUG [c.c.s.StorageManagerImpl] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Insufficient 
 un-allocated capacity on: 1 for volume allocation: [Vol[8|vm=null|DATADISK]] 
 since its allocated percentage: 1.6727310608597301 has crossed the allocated 
 pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
 2014-05-27 10:01:51,361 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) 
 ClusterScopeStoragePoolAllocator returning 0 suitable storage pools
 2014-05-27 10:01:51,364 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) 
 ZoneWideStoragePoolAllocator to find storage pool
 2014-05-27 10:01:51,372 WARN  [o.a.c.e.o.VolumeOrchestrator] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Unable to find 
 suitable primary storage when creating volume fifty
 2014-05-27 10:01:51,381 ERROR [c.c.v.VmWorkJobHandlerProxy] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Invocation 
 exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable 
 to find suitable primary storage when creating volume fifty
 2014-05-27 10:01:51,382 INFO  [c.c.v.VmWorkJobHandlerProxy] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Rethrow 
 exception com.cloud.utils.exception.CloudRuntimeException: Unable to find 
 suitable primary storage when creating volume fifty
 2014-05-27 10:01:51,382 DEBUG [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Done with run of VM work 
 job: com.cloud.storage.VmWorkAttachVolume for VM 6, job origin: 38
 2014-05-27 10:01:51,384 ERROR [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Unable to complete 
 AsyncJobVO {id:39, userId: 2, accountId: 2, instanceType: null, instanceId: 
 null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo: 
 rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAZ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAg,
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: Tue May 27 10:01:50 EDT 2014}, job origin:38
 com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable 
 primary storage when creating volume fifty
 at 
 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:447)
 at 
 org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:734)
 at 
 com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1186)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1054)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2475)
 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 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073752#comment-14073752
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7179:
-

Also observed below error

2014-07-24 01:13:58,858 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-2:null) Executing: /usr/sh
are/cloudstack-common/scripts/vm/network/security_group.py 
destroy_network_rules_for_vm --vmname r-802-VM
2014-07-24 01:13:59,021 WARN  [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-4:null) LibvirtException
org.libvirt.LibvirtException: internal error process exited while connecting to 
monitor: char device redirected to /de
v/pts/2
qemu-kvm: -drive 
file=/mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/f053f16a-5b3f-4b96-a56c-1c84a7e8a72a,if=none,id=drive-virtio-disk0,format=qcow2,cache=none:
 could not open disk image 
/mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/f053f16a-5b3f-4b96-a56c-1c84a7e8a72a: 
Invalid argument

at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.domainCreateXML(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1252)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3830)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1346)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
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:722)
2014-07-24 01:13:59,021 DEBUG [kvm.storage.KVMStoragePoolManager] 
(agentRequest-Handler-4:null) Disconnecting disk 
f053f16a-5b3f-4b96-a56c-1c84a7e8a72a
2014-07-24 01:13:59,021 DEBUG [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-4:null) Trying to fetch storage pool 
4f3ad80a-b796-3db3-b126-9c12b5b5eafc from libvirt
2014-07-24 01:13:59,037 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-2:null) Execution is successful.
2014-07-24 01:13:59,037 DEBUG [kvm.resource.LibvirtComputingResource] (

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread edison su (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073766#comment-14073766
 ] 

edison su commented on CLOUDSTACK-7179:
---

Is there a network connection issue for primary storage?

 Executing: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh -i 
nfs1-ccp.citrix.com -p /home/common/automation/SC_QA_AUTO4/primary2 -m 
/mnt/e9b0d73b-9890-3aae-8934-44bd194592e0 -h 10.223.50.66
2014-07-23 22:50:34,976 DEBUG [kvm.resource.KVMHAMonitor] (Thread-1037:null) 
Exit value is 1
2014-07-23 22:50:34,976 DEBUG [kvm.resource.KVMHAMonitor] (Thread-1037:null) 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
131: echo: write error: Input/output error
2014-07-23 22:50:34,976 WARN  [kvm.resource.KVMHAMonitor] (Thread-1037:null) 
write heartbeat failed: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
131: echo: write error: Input/output error, retry: 0


Then agent restart automatically, mgt server shutdown some routers because of 
vm sync, as agent reports some routers in running state, while the mgt server 
still thinks this routers are in the starting state.

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073776#comment-14073776
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7179:
-

I can see primary storages in good state now

[root@Rack2Host11 agent]# mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext=system_u:object_r:tmpfs_t:s0)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
nfs1-ccp.citrix.com:/home/common/automation/SC_QA_AUTO4/primary2 on 
/mnt/e9b0d73b-9890-3aae-8934-44bd194592e0 type nfs 
(rw,noac,actimeo=0,vers=4,addr=10.223.240.164,clientaddr=10.223.50.66)
nfs1-ccp.citrix.com:/home/common/automation/SC_QA_AUTO4/primary on 
/mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc type nfs 
(rw,noac,actimeo=0,vers=4,addr=10.223.240.164,clientaddr=10.223.50.66)
[root@Rack2Host11 agent]# cd /mnt/e9b0d73b-9890-3aae-8934-44bd194592e0
[root@Rack2Host11 e9b0d73b-9890-3aae-8934-44bd194592e0]# ls
10e29d9f-6950-4993-a654-6bd8bc7afd03  532e314f-746a-43e0-9073-253c4c58a4a4  
abdcea2e-a90d-4727-80fe-e70035baff47
1f5ceccd-bc65-47d3-aace-d4d0b4bbf5f4  5e9b6182-8f74-440d-b95d-4df761304fd1  
af10c3eb-ffde-4468-8cbb-b3fb78d4c243
2493d5fe-82c0-4ea9-aebe-fce0c2be8369  68a91b13-21e5-4e02-9ae3-7f5fb90adbdf  
b0108034-d80a-42eb-b2b7-a74ac56166e5
31dcb62e-9200-4669-9113-5c4f76233e76  7ce366e7-1fe4-4164-b493-8afe4d48b9f9  
b80c54fa-55b0-408f-8281-dc1923a73d8c
36075a10-1c9f-4653-8895-e8c592ea23db  7ee7471e-a681-4a47-92b5-1c074ba61fb3  
be93c338-b3a7-49a1-9acd-02cc67dc2500
37f82fa0-3f12-4b84-8a98-53dc3f1e448d  8610a779-035b-41e4-b391-efae1aedb315  
c59e2fcc-6325-4071-b90b-ed9612aac28b
380598b1-27bd-4e23-a895-dd8a1142d112  866ace2c-726c-49cb-9924-71bb06558070  
cdfedf0f-4df9-4671-99d7-2dab703a1220
3992016b-c1ed-4f16-921f-2309ee94473d  9d0da2c6-f4e7-4607-b473-ba5459ed2eb3  
fd0d8220-b52f-4984-9201-9f4b29aedd68
3ddd95f4-752a-4b72-9398-00f66c852f59  9fd46da7-924d-4e52-a2fb-52fbf945188b  
KVMHA
3f16d0d0-79a7-4569-98ce-bd7993e5c527  a2cc149e-12a9-11e4-b040-1a6f7bb0d0a8
450e3b26-ac4b-490d-bbcc-61447d7a99a7  a2cc4694-12a9-11e4-b040-1a6f7bb0d0a8
[root@Rack2Host11 e9b0d73b-9890-3aae-8934-44bd194592e0]#


 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread edison su (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073794#comment-14073794
 ] 

edison su commented on CLOUDSTACK-7179:
---

But at 2014-07-23 22:50:34, there are connection issues, and that's when the 
router start failure happened, right?
Do you see the router starting failure before? or just happened yesterday? 
There is no code change these days around router start. So I guess it's due to 
the primary storage network connectivity issue.

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.domainLookupByName(Unknown Source)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 

[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread Rayees Namathponnan (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073806#comment-14073806
 ] 

Rayees Namathponnan commented on CLOUDSTACK-7179:
-

DO you want to redeploy and check ? i can do that // 

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.domainLookupByName(Unknown Source)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 

[jira] [Resolved] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-4364.
-

Resolution: Fixed

 Restore VM - needs to log usage event for volume
 

 Key: CLOUDSTACK-4364
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.5.0


 Restore VM - needs to log usage event for volume so that any customer can 
 charge for the newly creat4ed volume



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6821) Disk allocated for primary storage remain unchanged after volume deletion

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta updated CLOUDSTACK-6821:


Fix Version/s: (was: 4.4.0)
   4.5.0

 Disk allocated for primary storage  remain unchanged after volume deletion 
 ---

 Key: CLOUDSTACK-6821
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6821
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.4.0
Reporter: prashant kumar mishra
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.5.0

 Attachments: Logs_Db.rar


 steps to repo
 ===
 1-prepare one cluster+one primary storage (say ps1) CS setup 
 2-deploy a vm
 3-create volume and attach to vm
 4-detach volume
 5-add another primary storage ps2
 6-migrate volume to ps
 7-Check Disk allocated for PS
 8-delete the volume wait for storage cleanup thread to run 
 9-check Disk allocated
 Expected
 
 Disk allocated should be zero since only volume got deleted
 Actual
 ==
 Disk allocated remains unchanged  
 DB
 ==
 mysql select * from storage_pool where id=4\G;
 *** 1. row ***
id: 4
  name: pm2
  uuid: c6e5687b-caa5-3d8c-9347-9ca24a0b69e8
 pool_type: NetworkFilesystem
  port: 2049
data_center_id: 1
pod_id: 1
cluster_id: 1
used_bytes: 804126720
capacity_bytes: 34390016000
  host_address: 10.147.29.216
 user_info: NULL
  path: /var/unixmen_share/pm2
   created: 2014-06-02 14:42:14
   removed: NULL
   update_time: NULL
status: Up
 storage_provider_name: DefaultPrimary
 scope: CLUSTER
hypervisor: NULL
   managed: 0
 capacity_iops: NULL
 1 row in set (0.00 sec)
 ERROR:
 No query specified
 mysql select * from storage_pool_view where id=4\G;
 *** 1. row ***
 id: 4
   uuid: c6e5687b-caa5-3d8c-9347-9ca24a0b69e8
   name: pm2
 status: Up
   path: /var/unixmen_share/pm2
  pool_type: NetworkFilesystem
   host_address: 10.147.29.216
created: 2014-06-02 14:42:14
removed: NULL
 capacity_bytes: 34390016000
  capacity_iops: NULL
  scope: CLUSTER
 hypervisor: NULL
  storage_provider_name: DefaultPrimary
 cluster_id: 1
   cluster_uuid: c9094153-1980-4765-934a-827e27ccbac6
   cluster_name: cl1
   cluster_type: CloudManaged
 data_center_id: 1
   data_center_uuid: ae6be023-91c9-47d0-9ce1-0898c4429ed4
   data_center_name: zn1
   data_center_type: Advanced
 pod_id: 1
   pod_uuid: 8465eac0-b4e5-467d-942a-fadac6c27e65
   pod_name: pd1
tag: NULL
 disk_used_capacity: 21474836480
 disk_reserved_capacity: 0
 job_id: NULL
   job_uuid: NULL
 job_status: NULL
 job_account_id: NULL
 1 row in set (0.00 sec)
 ERROR:
 No query specified
 =there was only one volume which got deleted .
 mysql select * from volumes where pool_id=4\G;
 *** 1. row ***
 id: 22
 account_id: 2
  domain_id: 1
pool_id: 4
   last_pool_id: 1
instance_id: NULL
  device_id: NULL
   name: new12
   uuid: f041aff6-883d-4d29-9226-0f4e8b76d981
   size: 21474836480
 folder: /var/unixmen_share/pm2
   path: 441126db-2d02-47b6-9b5f-48b43e443b37
 pod_id: 1
 data_center_id: 1
 iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
  pool_type: NULL
   disk_offering_id: 4
template_id: NULL
 first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2014-06-02 15:05:21
   attached: NULL
updated: 2014-06-02 15:08:26
removed: 2014-06-02 15:08:26
  state: Expunged
 chain_info: NULL
   update_count: 6
  disk_type: NULL
 vm_snapshot_chain_size: NULL
 iso_id: NULL

[jira] [Resolved] (CLOUDSTACK-5281) resource limit shouldnt be counted for resources with display flag = 0

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-5281.
-

Resolution: Fixed

 resource limit shouldnt be counted for resources with display flag = 0
 --

 Key: CLOUDSTACK-5281
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5281
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: Future


 Resource limit shouldnt be counted for resources with display flag = 0
 These are resources created by admin and hidden from the end user so shouldnt 
 count in the resource count or limit while creating/deleting them. But once 
 the flag is turned on it should start getting counted in the resource count.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-3885) CLONE - Volume Donwload URLs should expire - functionality missing

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-3885.
-

Resolution: Duplicate

Dup of CLOUDSTACK-6599

 CLONE - Volume Donwload URLs should expire - functionality missing
 --

 Key: CLOUDSTACK-3885
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3885
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.3.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.4.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6787) Event Bus - Publishing uuids missing in some cases

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-6787.
-

Resolution: Fixed

 Event Bus - Publishing uuids missing in some cases
 --

 Key: CLOUDSTACK-6787
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6787
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.4.0, 4.5.0


 Event Bus - Publishing uuids was missing in some cases



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7179) [Automation] Router deployment failing while calling patchviasocket.pl during router configuration

2014-07-24 Thread edison su (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073819#comment-14073819
 ] 

edison su commented on CLOUDSTACK-7179:
---

Yes, better to have a redeploy.

 [Automation] Router deployment failing while calling patchviasocket.pl 
 during router configuration
 

 Key: CLOUDSTACK-7179
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.5.0
 Environment: KVM RHEL 6.3
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Blocker
 Fix For: 4.5.0


 This issue is observed in automation environment, there are many router 
 deployment failure, this issue observed while programming patchviasocket.pl
 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Executing: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
 2014-07-23 22:50:24,973 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
 2014-07-23 22:50:27,974 DEBUG 
 [resource.virtualnetwork.VirtualRoutingResource] 
 (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
 2014-07-23 22:50:28,661 WARN  [kvm.resource.LibvirtComputingResource] 
 (Script-7:null) Interrupting script.
 2014-07-23 22:50:28,662 WARN  [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) Timed out: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n 
 r-384-VM -p 
 %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
  .  Output is:
 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-5:null) passcmd failed:timeout
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Request:Seq 1-586986832060423:  { Cmd , 
 MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:false,checkBeforeCleanup:true,vmName:r-384-VM,wait:0}}]
  }
 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Processing command: 
 com.cloud.agent.api.StopCommand
 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then 
 use the default hypervisor
 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource] 
 (agentRequest-Handler-3:null) Failed to get vm status in case of 
 checkboforecleanup is true
 org.libvirt.LibvirtException: Domain not found: no domain with matching name 
 'r-384-VM'
 at org.libvirt.ErrorHandler.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.processError(Unknown Source)
 at org.libvirt.Connect.domainLookupByName(Unknown Source)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection] 
 (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM, 
 continue
 2014-07-23 22:52:56,334 DEBUG 

[jira] [Commented] (CLOUDSTACK-7166) [Automation] Delete Snapshot command fails with NPE

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073869#comment-14073869
 ] 

ASF subversion and git services commented on CLOUDSTACK-7166:
-

Commit 165618ac9ac2937fbb1d7ff0da89de1abba4ccc1 in cloudstack's branch 
refs/heads/master from Edison Su
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=165618a ]

CLOUDSTACK-7166: fix NPE


 [Automation] Delete Snapshot command fails with NPE
 ---

 Key: CLOUDSTACK-7166
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7166
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue is observed in KVM automation run, delete snapshot command fails 
 with NPE
 2014-07-22 09:12:13,363 WARN  [c.c.u.AccountManagerImpl] 
 (API-Job-Executor-9:ctx-19b7e7dc job-3170 ctx-5c41370c) Failed to cleanup 
 account Acct[7318b4fd
 -38fb-45eb-863a-34ace7abf8a9-test-TestSnapshotOnRootVolume-test_04_concurrent_snapshots_create_volume-Q5F695]
  due to
 java.lang.NullPointerException
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:626)
 at sun.reflect.GeneratedMethodAccessor535.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.$Proxy179.deleteSnapshotDirsForAccount(Unknown 
 Source)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:707)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:666)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1438)
 at sun.reflect.GeneratedMethodAccessor529.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.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 com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:187)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:121)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:104)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
 at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
 at 
 

[jira] [Resolved] (CLOUDSTACK-7166) [Automation] Delete Snapshot command fails with NPE

2014-07-24 Thread edison su (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su resolved CLOUDSTACK-7166.
---

Resolution: Fixed

 [Automation] Delete Snapshot command fails with NPE
 ---

 Key: CLOUDSTACK-7166
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7166
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue is observed in KVM automation run, delete snapshot command fails 
 with NPE
 2014-07-22 09:12:13,363 WARN  [c.c.u.AccountManagerImpl] 
 (API-Job-Executor-9:ctx-19b7e7dc job-3170 ctx-5c41370c) Failed to cleanup 
 account Acct[7318b4fd
 -38fb-45eb-863a-34ace7abf8a9-test-TestSnapshotOnRootVolume-test_04_concurrent_snapshots_create_volume-Q5F695]
  due to
 java.lang.NullPointerException
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:626)
 at sun.reflect.GeneratedMethodAccessor535.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.$Proxy179.deleteSnapshotDirsForAccount(Unknown 
 Source)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:707)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:666)
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1438)
 at sun.reflect.GeneratedMethodAccessor529.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.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 com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:187)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:121)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:104)
 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:507)
 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] [Resolved] (CLOUDSTACK-7164) [Automation] NPE observed while deleting account

2014-07-24 Thread edison su (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su resolved CLOUDSTACK-7164.
---

Resolution: Fixed

 [Automation] NPE observed while deleting account 
 -

 Key: CLOUDSTACK-7164
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7164
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM (RHEL 6.3)
 Master 4.5
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue observed in KVM automation run, NPE observed while deleting NPE
 2014-07-22 07:45:15,223 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-04c38067) Zone 1 is ready to launch secondary storage VM
 2014-07-22 07:45:15,230 DEBUG [c.c.n.NetworkModelImpl] 
 (Work-Job-Executor-111:ctx-fabfa66d job-2638/job-2639 ctx-a62364f5) Service 
 SecurityGroup is not
 supported in the network id=385
 2014-07-22 07:45:15,231 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-117:ctx-e28a5cb1 job-2646) Unexpected exception while 
 executing org.apache
 .cloudstack.api.command.admin.account.DeleteAccountCmd
 java.lang.NullPointerException
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1409)
 at sun.reflect.GeneratedMethodAccessor529.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.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 com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:187)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:121)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:104)
 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:507)
 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:464)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 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-07-22 07:45:15,232 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-117:ctx-e28a5cb1 job-2646) Complete async job-2646, 
 jobStatus: FAILED,
  resultCode: 530, result: 
 

[jira] [Commented] (CLOUDSTACK-7164) [Automation] NPE observed while deleting account

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073870#comment-14073870
 ] 

ASF subversion and git services commented on CLOUDSTACK-7164:
-

Commit 2f832fddff4786dbc3cafd5934cf65e3c6f2db99 in cloudstack's branch 
refs/heads/master from Edison Su
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2f832fd ]

CLOUDSTACK-7164: fix NPE


 [Automation] NPE observed while deleting account 
 -

 Key: CLOUDSTACK-7164
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7164
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM (RHEL 6.3)
 Master 4.5
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue observed in KVM automation run, NPE observed while deleting NPE
 2014-07-22 07:45:15,223 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-04c38067) Zone 1 is ready to launch secondary storage VM
 2014-07-22 07:45:15,230 DEBUG [c.c.n.NetworkModelImpl] 
 (Work-Job-Executor-111:ctx-fabfa66d job-2638/job-2639 ctx-a62364f5) Service 
 SecurityGroup is not
 supported in the network id=385
 2014-07-22 07:45:15,231 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-117:ctx-e28a5cb1 job-2646) Unexpected exception while 
 executing org.apache
 .cloudstack.api.command.admin.account.DeleteAccountCmd
 java.lang.NullPointerException
 at 
 com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1409)
 at sun.reflect.GeneratedMethodAccessor529.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.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 com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source)
 at 
 org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:187)
 at 
 org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:121)
 at 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:104)
 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:507)
 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:464)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 

[jira] [Commented] (CLOUDSTACK-7165) [Automation] NPE observed during restart and expunge VM

2014-07-24 Thread edison su (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073876#comment-14073876
 ] 

edison su commented on CLOUDSTACK-7165:
---

Don't know how to fix it quickly, so assign it to Min.

 [Automation] NPE observed during restart and expunge VM 
 

 Key: CLOUDSTACK-7165
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7165
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM (RHEL 6.3)
Reporter: Rayees Namathponnan
Assignee: Min Chen
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue is observed with latest  automation run . NPE observed during 
 restart abd expunge VM 
 2014-07-22 10:52:34,081 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-06101cd2) ===START===  10.150.19.7 -- GET  
 command=expungeVirtualMachineid=f991f7fa-1376-486b-be92-894638942c14response=jsonsessionkey=HKY1QrnQ2q8iKG%2FGN%2FaRArKCny4%3D_=1406051549738
 2014-07-22 10:52:34,099 ERROR [c.c.a.ApiServer] 
 (catalina-exec-10:ctx-06101cd2 ctx-e8e32432) unhandled exception executing 
 api command: [Ljava.lang.String;@23210413
 java.lang.NullPointerException
 at 
 com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:494)
 at 
 com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:482)
 at sun.reflect.GeneratedMethodAccessor146.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.$Proxy102.checkAccess(Unknown Source)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.doAccessChecks(ParamProcessWorker.java:232)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.processParameters(ParamProcessWorker.java:217)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.handle(ParamProcessWorker.java:89)
 at 
 com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:635)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 

[jira] [Updated] (CLOUDSTACK-7165) [Automation] NPE observed during restart and expunge VM

2014-07-24 Thread edison su (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su updated CLOUDSTACK-7165:
--

Assignee: Min Chen  (was: edison su)

 [Automation] NPE observed during restart and expunge VM 
 

 Key: CLOUDSTACK-7165
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7165
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
 Environment: KVM (RHEL 6.3)
Reporter: Rayees Namathponnan
Assignee: Min Chen
Priority: Critical
 Fix For: 4.5.0

 Attachments: Jully_22_KVM.rar


 This issue is observed with latest  automation run . NPE observed during 
 restart abd expunge VM 
 2014-07-22 10:52:34,081 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-06101cd2) ===START===  10.150.19.7 -- GET  
 command=expungeVirtualMachineid=f991f7fa-1376-486b-be92-894638942c14response=jsonsessionkey=HKY1QrnQ2q8iKG%2FGN%2FaRArKCny4%3D_=1406051549738
 2014-07-22 10:52:34,099 ERROR [c.c.a.ApiServer] 
 (catalina-exec-10:ctx-06101cd2 ctx-e8e32432) unhandled exception executing 
 api command: [Ljava.lang.String;@23210413
 java.lang.NullPointerException
 at 
 com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:494)
 at 
 com.cloud.user.AccountManagerImpl.checkAccess(AccountManagerImpl.java:482)
 at sun.reflect.GeneratedMethodAccessor146.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.$Proxy102.checkAccess(Unknown Source)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.doAccessChecks(ParamProcessWorker.java:232)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.processParameters(ParamProcessWorker.java:217)
 at 
 com.cloud.api.dispatch.ParamProcessWorker.handle(ParamProcessWorker.java:89)
 at 
 com.cloud.api.dispatch.DispatchChain.dispatch(DispatchChain.java:37)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:635)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
 at 
 com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317)
 at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 

[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui

2014-07-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073885#comment-14073885
 ] 

ASF subversion and git services commented on CLOUDSTACK-5641:
-

Commit 2ed22b3ba7e67ad96bd741635eec75b9192275cb in cloudstack's branch 
refs/heads/master from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2ed22b3 ]

CLOUDSTACK-5641: Local disk usage on host don't show up in the admin's webui. 
Correcting the view to include capacity type 9 which is local storage. Also 
changing the response to just pick the used bytes coming in through the view 
which now stands corrected.
Verified that the dashboard and storage pool view works fine.


 Local disk usage on host don't show up in the admin's webui
 ---

 Key: CLOUDSTACK-5641
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Nitin Mehta
 Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG


 Local disk usage on storage pool view don't show up in the admin's webui.
 I have local storage enabled in the environment. I have VMs on the storage 
 but since upgrading to 4.2 the UI does not show space utilization on the 
 local storage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Reopened] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui

2014-07-24 Thread Nitin Mehta (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta reopened CLOUDSTACK-5641:
-

  Assignee: Nitin Mehta

 Local disk usage on host don't show up in the admin's webui
 ---

 Key: CLOUDSTACK-5641
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Attachments: CS_4.2_5641.JPG, CS_master_5641.JPG


 Local disk usage on storage pool view don't show up in the admin's webui.
 I have local storage enabled in the environment. I have VMs on the storage 
 but since upgrading to 4.2 the UI does not show space utilization on the 
 local storage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


  1   2   >