[jira] [Updated] (CLOUDSTACK-1877) Failed to connect to DB while starting Ubuntu management server after upgrading the packages from 4.0 to 4.1

[Sudha Ponnaganti (JIRA)]

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

Sudha Ponnaganti updated CLOUDSTACK-1877:
-

Fix Version/s: 4.1.0

> Failed to connect to DB while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> 
>
> Key: CLOUDSTACK-1877
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1877
> 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.1.0
>Reporter: Sailaja Mada
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: 40cloudstack_backup.dmp, 40db.properties, 
> 41db.properties, management-server.log
>
>
> Setup:
> MS : Ubuntu 12.04 with Xen 6.0.2 host , Advanced Networking
> Steps:
> 1. Stop Management Server 
> 2. Upgrade the packages of MS from 4.0 to 4.1
> 3. Start the Management Server.
> DB upgrade failed to start while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> Note: Attached DB properties DB Dump. MS log
> 2013-04-01 17:24:33,869 ERROR [web.context.ContextLoader] (main:null) Context 
> initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'apiServer': Invocation of init method failed; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:135)
>  at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1448)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
> at 
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002)
> at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
> at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
> at 
>

[jira] [Updated] (CLOUDSTACK-1224) Volume snapshot creation failing

[Sudha Ponnaganti (JIRA)]

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

Sudha Ponnaganti updated CLOUDSTACK-1224:
-

Fix Version/s: 4.1.0

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: edison su
>Priority: Critical
> Fix For: 4.1.0
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> 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:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspec

[jira] [Commented] (CLOUDSTACK-1224) Volume snapshot creation failing

[Sudha Ponnaganti (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619605#comment-13619605
 ] 

Sudha Ponnaganti commented on CLOUDSTACK-1224:
--

Set Fix version to 4.1

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: edison su
>Priority: Critical
> Fix For: 4.1.0
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> 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:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAs

[jira] [Created] (CLOUDSTACK-1884) CreateNetworkOffering tests broken due to database reference

[Hugo Trippaers (JIRA)]

Hugo Trippaers created CLOUDSTACK-1884:
--

 Summary: CreateNetworkOffering tests broken due to database 
reference
 Key: CLOUDSTACK-1884
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1884
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Test
Affects Versions: 4.2.0
Reporter: Hugo Trippaers
Assignee: Kelven Yang
Priority: Blocker


how to replay:
git checkout 5782abf8f80fce929e3d6e20068bc165f2360426
mvn clean test -pl :cloud-server -am

commit:
commit 5782abf8f80fce929e3d6e20068bc165f2360426
Author: Kelven Yang 
Date:   Fri Mar 29 11:01:40 2013 -0700

Update unit test configuraitons to new custom Spring AOP


Results :

Tests in error: 
  
createSharedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createSharedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createSharedNtwkOffWithSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createSharedNtwkOffWithoutSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createIsolatedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createIsolatedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createIsolatedNtwkOffWithSpecifyIpRangesAndSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null
  
createIsolatedNtwkOffWithSpecifyIpRangesAndNoSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
 DB Exception on: null

Tests run: 43, Failures: 0, Errors: 8, Skipped: 2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-752) nTier Apps 2.0 : Support upto 8 VPN Connections

[Pranav Saxena (JIRA)]

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

Pranav Saxena resolved CLOUDSTACK-752.
--

Resolution: Won't Fix

Doesn't require any separate UI . To create more VPN connections , all what one 
needs to do is  create customer gateways and a VPN gateway and then under 
Site-to-Site VPN section , just select the  VPN connection section and click on 
add VPN connection button on the top right hand corner . It’ll display the list 
of customer gateways created and one could choose one of them to create a VPN 
connection.

Thanks !

> nTier Apps 2.0 : Support upto 8 VPN Connections
> ---
>
> Key: CLOUDSTACK-752
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-752
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Kishan Kavala
>Assignee: Brian Federle
> Fix For: 4.2.0
>
>
> This item is a sub task (2.7) of 
> https://issues.apache.org/jira/browse/CLOUDSTACK-621 
> Only 1 VPN Connection is currently supported. Any existing constraints should 
> be relaxed and upto 8 VPN connections should be verified

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1884) CreateNetworkOffering tests broken due to database reference

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619612#comment-13619612
 ] 

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

Commit df6b97c194caa8b34fa14bf5164eb2fe1f26b2b1 in branch refs/heads/master 
from Hugo Trippaers 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=df6b97c ]

Disabling broken test, see CLOUDSTACK-1884. Please revert this commit once the 
test itself is fixed.


> CreateNetworkOffering tests broken due to database reference
> 
>
> Key: CLOUDSTACK-1884
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1884
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Affects Versions: 4.2.0
>Reporter: Hugo Trippaers
>Assignee: Kelven Yang
>Priority: Blocker
>
> how to replay:
> git checkout 5782abf8f80fce929e3d6e20068bc165f2360426
> mvn clean test -pl :cloud-server -am
> commit:
> commit 5782abf8f80fce929e3d6e20068bc165f2360426
> Author: Kelven Yang 
> Date:   Fri Mar 29 11:01:40 2013 -0700
> Update unit test configuraitons to new custom Spring AOP
> Results :
> Tests in error: 
>   
> createSharedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithoutSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndNoSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
> Tests run: 43, Failures: 0, Errors: 8, Skipped: 2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1885) Broken testcases in 4.1

[Hugo Trippaers (JIRA)]

Hugo Trippaers created CLOUDSTACK-1885:
--

 Summary: Broken testcases in 4.1
 Key: CLOUDSTACK-1885
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1885
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Test
Affects Versions: 4.1.0
Reporter: Hugo Trippaers
 Fix For: 4.1.0


The following testcases are marked as excluded in server/pom.xml for 4.1

%regex[.*[0-9]*To[0-9]*.*Test.*]
  
com/cloud/upgrade/AdvanceZone223To224UpgradeTest
  
com/cloud/upgrade/AdvanceZone217To224UpgradeTest
com/cloud/async/*
com/cloud/cluster/*
com/cloud/snapshot/*
com/cloud/storage/dao/*
com/cloud/vm/dao/*
com/cloud/vpc/*
com/cloud/api/ListPerfTest.java
com/cloud/network/vpn/RemoteAccessVpnTest.java

com/cloud/network/security/SecurityGroupManagerImpl2Test.java

These tests should be reviewed and either deleted or fixed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1886) UI:disable scope for primary storage addition in the zone create wizard if the hypervisor is not KVM

[Srikanteswararao Talluri (JIRA)]

Srikanteswararao Talluri created CLOUDSTACK-1886:


 Summary: UI:disable scope for primary storage addition in the zone 
create wizard if the hypervisor is not KVM
 Key: CLOUDSTACK-1886
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1886
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Pranav Saxena
Priority: Critical
 Fix For: 4.2.0


disable scope for primary storage addition in the zone create wizard if the 
hypervisor is not KVM and make default scope as cluster.

Remove "host" from the scope drop down .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1886) UI:disable scope for primary storage addition in the zone create wizard if the hypervisor is not KVM

[Pranav Saxena (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619636#comment-13619636
 ] 

Pranav Saxena commented on CLOUDSTACK-1886:
---

Sanjeev ,

If I see the latest master , for all hypervisors except for KVM , you would see 
"cluster" as the default scope with host in the drop down . Your description 
isn't clear here - it says "disable the scope if not KVM " ? Also make 
"cluster" as default which is already there . So do you want me to remove only 
the "host " option from the dropdown ?

Thanks !

> UI:disable scope for primary storage addition in the zone create wizard if 
> the hypervisor is not KVM
> 
>
> Key: CLOUDSTACK-1886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1886
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> disable scope for primary storage addition in the zone create wizard if the 
> hypervisor is not KVM and make default scope as cluster.
> Remove "host" from the scope drop down .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1887) UI: remove "host" from the drop down list for add primary storage screen

[Srikanteswararao Talluri (JIRA)]

Srikanteswararao Talluri created CLOUDSTACK-1887:


 Summary: UI: remove "host" from the drop down list for add primary 
storage screen
 Key: CLOUDSTACK-1887
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1887
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Pranav Saxena
Priority: Critical
 Fix For: 4.2.0


remove "host" from the drop down list for add primary storage screen

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1886) UI:disable scope for primary storage addition in the zone create wizard if the hypervisor is not KVM

[Srikanteswararao Talluri (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619641#comment-13619641
 ] 

Srikanteswararao Talluri commented on CLOUDSTACK-1886:
--

oh ! i didn't check it with latest code. 

>>So do you want me to remove only the "host " option from the dropdown ?
  yes, i filed another bug for it.

> UI:disable scope for primary storage addition in the zone create wizard if 
> the hypervisor is not KVM
> 
>
> Key: CLOUDSTACK-1886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1886
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> disable scope for primary storage addition in the zone create wizard if the 
> hypervisor is not KVM and make default scope as cluster.
> Remove "host" from the scope drop down .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CLOUDSTACK-528) Failed to create secondary storage

[Nicolas Lamirault (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616407#comment-13616407
 ] 

Nicolas Lamirault edited comment on CLOUDSTACK-528 at 4/2/13 9:22 AM:
--

According to this commit : 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf
  there is only documentation fixes.
As Tamas said, this bug is not only a problem of documentation.
Regards

  was (Author: nlamirault):
According to this commit : 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=095f5523b9832488071579f347035037a9b9babf,
  there is only documentation fixes.
As Tamas said, this bug is not only a problem of documentation.
Regards
  
> Failed to create secondary storage
> --
>
> Key: CLOUDSTACK-528
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller
>Affects Versions: 4.0.0
> Environment: CentOS 
>Reporter: Tamas Monos
>Assignee: Saksham Srivastava
>Priority: Blocker
> Fix For: 4.0.2
>
>
> Hi,
> I cannot add secondary storage to my existing Zone. This prevents the 
> platform from operating.
> API call via GUI captured by tcpdump:
> http://sandbox.veber.co.uk/client/api?command=addSecondaryStorage&zoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1&url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloud&response=json&sessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D&_=1353673985114
> Result:
> Unable to connect due to 
> java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data 
> center: null
> at 
> com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
> at 
> com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
> at 
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
> at 
> com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
> at 
> com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> 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)
> 2012-11-23 12:32:58,518 INFO  [cloud.resource.ResourceManagerImpl] 
> (catalina-exec-23:null) server resources successfully discovered by 
> SecondaryStorage
> 2012-11-23 12:32:58,518 WARN  [cloud.api.ApiDispatcher] 
> (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to 
> add secondary storage
> Debug:
> mysql> select uuid from data_center where name='Watford';
> +--+
> | uuid |
> +--+
> | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 |
> +

[jira] [Updated] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare

[Ram Ganesh (JIRA)]

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

Ram Ganesh updated CLOUDSTACK-1868:
---

Assignee: Sateesh Chodapuneedi

> GetVmStatsCommand throws NullPointerException with VMWare
> -
>
> Key: CLOUDSTACK-1868
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.1.0
>Reporter: Francois Gaudreault
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.1.0
>
>
> We see bunch of these in the log files of CloudStack.  Looks like the 
> GetVmStatsCommand crash with a Null pointer exception. We don't think it's 
> permission related since our CS user on vSphere can see all performance and 
> VM statistics using the vSphere client.
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined 
> to be up and running
> ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) 
> Unable to execute GetVmStatsCommand due to : Exception: 
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN  [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM 
> statistics.
> ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) 
> Unable to execute GetVmStatsCommand due to : Exception: 
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN  [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM 
> statistics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1687) VMSnapshot: VM Fails to Start after a RevertToVMSnapshot Operation

[Mice Xia (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619655#comment-13619655
 ] 

Mice Xia commented on CLOUDSTACK-1687:
--

Cannot reproduce it in my env, Chandan, can you always reproduce it?

> VMSnapshot: VM Fails to Start after a RevertToVMSnapshot Operation
> --
>
> Key: CLOUDSTACK-1687
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1687
> 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: Chandan Purushothama
>Assignee: Mice Xia
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 
> Steps to Reproduce the Bug:
> 
> 1. Deploy Vm.  Attach muiltiple data disks to this VM.
> 2. Log in to the Vm and create few directories and files on the root volume. 
> Create few more directories on each of  the data disks.
> 3. Stop the VM.
> 4. Create VMSnapshot for this VM with "vm_snapshot_type" set to "Disk"
> 5. Start the VM.
> 6. Delete few of the above created directories and add few more directories 
> on the root volume.Delete few of the above created directories and add few 
> more directories on the data disks.
> 7. Stop the VM.
> 8. Revert this Vm to the above created Snapshot.
> 9. Start the VM.
> ===
> Observations:
> ===
> *Management Server Log*
> 2013-03-14 16:06:15,703 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) Executing resource StartCommand: 
> {"vm":{"id":9,"name":"i-3-9-VMSNAP","bootloader":"HVM","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"CentOS
>  5.3 
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"ec119fd35127c44e","params":{"rootDiskController":"ide","nicAdapter":"E1000"},"uuid":"1c64977b-db4f-415e-98ce-83b53a612493","disks":[{"id":14,"name":"ROOT-9","mountPoint":"/export/home/chandan/asf4-131-170/primary","path":"ROOT-9-14-01","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"f42a60c2-0940-305b-bb14-23d8b40f42bc","deviceId":0},{"id":15,"name":"DATA-9","mountPoint":"/export/home/chandan/asf4-131-170/primary","path":"c7adbf5e2509484d8ac4959ae53e6146-01","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"f42a60c2-0940-305b-bb14-23d8b40f42bc","deviceId":1},{"id":16,"name":"NEWDISK-3","mountPoint":"/export/home/chandan/asf4-131-170/primary","path":"fba51dce35d24c19a224090f3cb597e8-01","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"f42a60c2-0940-305b-bb14-23d8b40f42bc","deviceId":2},{"id":9,"name":"CentOS
>  5.3(64-bit) no GUI 
> (vSphere)","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":495,"defaultNic":true,"uuid":"06e76915-e16d-4f60-a311-3a5fbdd7d5ab","ip":"10.1.1.66","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:48:7a:00:07","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://2254","isolationUri":"vlan://2254","isSecurityGroupEnabled":false}]},"hostIp":"10.223.58.2","wait":0}
> 2013-03-14 16:06:15,703 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) VM i-3-9-VMSNAP will be started with NIC device 
> type: E1000
> 2013-03-14 16:06:15,703 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) Drop invalid disk option, volumeTO: 
> {"id":9,"name":"CentOS 5.3(64-bit) no GUI 
> (vSphere)","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}
> 2013-03-14 16:06:15,723 DEBUG [vmware.mo.HostMO] 
> (DirectAgent-242:10.223.58.2) find VM i-3-9-VMSNAP on host
> 2013-03-14 16:06:15,723 DEBUG [vmware.mo.HostMO] 
> (DirectAgent-242:10.223.58.2) load VM cache on host
> 2013-03-14 16:06:15,728 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) VM i-3-9-VMSNAP already exists, tear down 
> devices for reconfiguration
> 2013-03-14 16:06:15,750 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) Prepare ISO volume at existing device 
> {"key":3000,"deviceInfo":{"label":"CD/DVD drive 1","summary":"Remote 
> device"},"backing":{"exclusive":false,"deviceName":""},"connectable":{"startConnected":true,"allowGuestControl":false,"connected":true},"controllerKey":200,"unitNumber":0}
> 2013-03-14 16:06:15,753 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-242:10.223.58.2) Prepare volume at new device 
> {"capacityInKB":0,"key":-2,"backing":{"diskMode":"persistent","fileN

[jira] [Commented] (CLOUDSTACK-1887) UI: remove "host" from the drop down list for add primary storage screen

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619656#comment-13619656
 ] 

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

Commit 8d34b5809d459eac90eea1f01cc5b20dedb39f11 in branch refs/heads/master 
from [~pranav.sax...@citrix.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8d34b58 ]

CLOUDSTACK-1887:removing the host option from the scope field for primary 
storage


> UI: remove "host" from the drop down list for add primary storage screen
> 
>
> Key: CLOUDSTACK-1887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1887
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> remove "host" from the drop down list for add primary storage screen

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1887) UI: remove "host" from the drop down list for add primary storage screen

[Pranav Saxena (JIRA)]

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

Pranav Saxena resolved CLOUDSTACK-1887.
---

Resolution: Fixed

> UI: remove "host" from the drop down list for add primary storage screen
> 
>
> Key: CLOUDSTACK-1887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1887
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> remove "host" from the drop down list for add primary storage screen

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1886) UI:disable scope for primary storage addition in the zone create wizard if the hypervisor is not KVM

[Pranav Saxena (JIRA)]

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

Pranav Saxena resolved CLOUDSTACK-1886.
---

Resolution: Invalid

> UI:disable scope for primary storage addition in the zone create wizard if 
> the hypervisor is not KVM
> 
>
> Key: CLOUDSTACK-1886
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1886
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> disable scope for primary storage addition in the zone create wizard if the 
> hypervisor is not KVM and make default scope as cluster.
> Remove "host" from the scope drop down .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1888) [UI]Child Domain Admin accounts can not set/update the resource limits

[Sailaja Mada (JIRA)]

Sailaja Mada created CLOUDSTACK-1888:


 Summary: [UI]Child Domain Admin accounts can not set/update the  
resource limits
 Key: CLOUDSTACK-1888
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1888
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Sonny Chhen
 Attachments: DomainAdminView.png

Setup: Advanced Networking zone with Xen 6.1 [4.2]

Steps:

1. Create Child domain (CDC1) under ROOT 
2. Create Domain account CDC1Admin1 under Child Domain CDC1
3. Access Management Server as this domain admin account

Observation: Child Domain Admin accounts can not set/update the  resource 
limits. It is supported via API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1881) [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 the 'storage provide name' and 'scope' fields in the cloud.storage_pool table is left blank, due to which we ge

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek reassigned CLOUDSTACK-1881:
--

Assignee: edison su

> [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 the 'storage provide 
> name' and 'scope' fields in the cloud.storage_pool table is left blank, due 
> to which we get a NPE while doing any operation involving primary storage.
> 
>
> Key: CLOUDSTACK-1881
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1881
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
> Environment: 4.0 to 4.2 upgrade
> Host : XEN
>Reporter: Abhinav Roy
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
>
> After doing upgrade from 4.0 to 4.2 , if we try to restart domain router, 
> ssvm or cpvm we get the following NPE
> 2013-04-01 19:43:20,808 ERROR [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-4:job-30) Unexpected exception while executing 
> org.apache.cloudstack.api.command.admin.router.RebootRouterCmd
> java.lang.NullPointerException
> at 
> org.apache.cloudstack.storage.datastore.manager.DefaultPrimaryDataStoreProviderManagerImpl.getPrimaryDataStore(DefaultPrimaryDataStoreProviderManagerImpl.java:62)
> at 
> org.apache.cloudstack.storage.datastore.DataStoreManagerImpl.getPrimaryDataStore(DataStoreManagerImpl.java:71)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:662)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:462)
> at 
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2625)
> at 
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1834)
> at 
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:2883)
> at 
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.rebootRouter(VirtualNetworkApplianceManagerImpl.java:610)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.admin.router.RebootRouterCmd.execute(RebootRouterCmd.java:99)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Reason :
> ===
> 1. In a CS 4.2 setup , when we look at the cloud.storage_pool table contents, 
> we have something like this ..
> mysql> SELECT * FROM cloud.storage_pool;
> +-+--+--+---+--++++-+++---+---+-+-+-++-+-+
> | id  | name | uuid | pool_type | 
> port | data_center_id | pod_id | cluster_id | available_bytes | 
> capacity_bytes | host_address   | user_info | path  | 
> created | removed | update_time | status | storage_provider_id | 
> scope   |
> +-+--+--+---+--++++-+++---+---+-+-+-++-+-+
> | 200 | xen-pri  | cfc506df-7966-3f22-91c9-98b1a617ea56 | NetworkFilesystem | 
> 2049 |  1 |   NULL |   NULL |   0 |  
> 0 | 10.102.192.100 | NULL  | /cpg_vol/abhinav/xen-pri  | 2013-03-26 
> 08:25:11 | NULL| NULL| Up |   3 | ZONE|
>

[jira] [Assigned] (CLOUDSTACK-1879) NPE while migrating volume

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek reassigned CLOUDSTACK-1879:
--

Assignee: edison su

> NPE while migrating volume
> --
>
> Key: CLOUDSTACK-1879
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1879
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
>
> try to migrate a volume from one primary storage to another (irrespective of 
> the storage's scope-zone,cluster)
>  ===START===  10.252.249.129 -- GET  
> command=migrateVolume&storageid=763f7983-6cb8-3ccb-bc4d-30a36d015b21&volumeid=880958ba-8667-4ebe-8b03-cb32f2dbc3c9&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881190825
> 2013-04-02 16:35:55,829 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-4:null) submit async job-101, details: AsyncJobVO {id:101, 
> userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 
> null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, 
> cmdOriginator: null, cmdInfo: 
> {"response":"json","sessionkey":"FDm4fMQ93FjXjXmoBg/KrL6WrTU\u003d","ctxUserId":"2","storageid":"763f7983-6cb8-3ccb-bc4d-30a36d015b21","_":"1364881190825","volumeid":"880958ba-8667-4ebe-8b03-cb32f2dbc3c9","ctxAccountId":"2","ctxStartEventId":"360"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-04-02 16:35:55,832 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
> ===END===  10.252.249.129 -- GET  
> command=migrateVolume&storageid=763f7983-6cb8-3ccb-bc4d-30a36d015b21&volumeid=880958ba-8667-4ebe-8b03-cb32f2dbc3c9&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881190825
> 2013-04-02 16:35:55,836 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Executing 
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-101
> 2013-04-02 16:35:55,869 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-10:job-101) migrate volume failed:java.lang.NullPointerException
> 2013-04-02 16:35:55,869 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Complete async job-101, jobStatus: 1, resultCode: 
> 0, result: null
> 2013-04-02 16:35:55,878 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Done executing 
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-101

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1888) [UI]Child Domain Admin accounts can not set/update the resource limits

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1888:
-

Attachment: DomainAdminView.png

> [UI]Child Domain Admin accounts can not set/update the  resource limits
> ---
>
> Key: CLOUDSTACK-1888
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1888
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Sonny Chhen
> Attachments: DomainAdminView.png
>
>
> Setup: Advanced Networking zone with Xen 6.1 [4.2]
> Steps:
> 1. Create Child domain (CDC1) under ROOT 
> 2. Create Domain account CDC1Admin1 under Child Domain CDC1
> 3. Access Management Server as this domain admin account
> Observation: Child Domain Admin accounts can not set/update the  resource 
> limits. It is supported via API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1867) [VMware] [SystemVMTemplate] is not working with latest cloudstack master

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek reassigned CLOUDSTACK-1867:
--

Assignee: Rohit Yadav

> [VMware] [SystemVMTemplate] is not working with latest cloudstack master
> 
>
> Key: CLOUDSTACK-1867
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1867
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: commit # 355589c1f0c583cbbdc601f74dba504064f81bac
> - Advanced zone with VMware cluster
>Reporter: venkata swamybabu budumuru
>Assignee: Rohit Yadav
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: logs.01.tgz, systemvmTemplate.JPG, xml.txt
>
>
> Steps to reproduce :
> 1. Took the latest system vm template from jenkins 
> http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-2013-03-27-master-vmware.ova
> 2. Seeded the above template using the following 
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>  -m /tmp/1/secondary.campo.vmw.GOLD/ -u 
> http://10.147.28.7/templates/campo/templates/systemvmtemplate-2013-03-27-master-vmware.ova
>  -h vmware -F
> 3. Tried to bring up the advanced zone using ESXi 5.1 
> Observations : 
> (i) Found the following error in vmops.log
> 2013-04-01 11:16:33,856 INFO  [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-6:10.147.40.12) Secondary storage mount point: 
> /mnt/VM/7280707764394.cc4bce7
> 2013-04-01 11:16:33,863 DEBUG [cloud.alert.AlertManagerImpl] 
> (CapacityChecker:null) Done running Capacity Checker ...
> 2013-04-01 11:16:34,832 ERROR [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-6:10.147.40.12) Unable to execute PrimaryStorageDownloadCommand 
> due to exception
> javax.xml.ws.soap.SOAPFaultException:
> Required parameter spec is missing
> while parsing call information for method ImportVApp
> at line 1, column 110
> while parsing SOAP body
> at line 1, column 102
> while parsing SOAP envelope
> at line 1, column 38
> while parsing HTTP request for method importVApp
> on object of type vim.ResourcePool
> at line 1, column 0
> at 
> com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at 
> com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
> at 
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
> at 
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
> at sun.proxy.$Proxy89.importVApp(Unknown Source)
> at 
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.importVmFromOVF(HypervisorHostHelper.java:995)
> at 
> com.cloud.hypervisor.vmware.mo.HostMO.importVmFromOVF(HostMO.java:681)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:478)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:153)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3660)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:414)
> 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:1146)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 11:16:34,836 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-6:null) Seq 5-37990: Response Received:
> 2013-04-01 11:16:34,836 DEBUG [agent.transport.Request] (DirectAgent-6:null) 
> Seq 5-37990: Processing:  { Ans: , MgmtId: 7280707764394, via: 5, Ver: 
> v1, Flags: 110, 
> [{"storage.PrimaryStorageDownloadAnswer":{"templateSize":0,"result

[jira] [Commented] (CLOUDSTACK-1698) VMSnapshot Limitations Violation: Detaching/Attaching VM volume is not allowed if there are VM Snapshots- Currently it is allowed

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619660#comment-13619660
 ] 

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

Commit dedec164e8cce17b861d517fe8e29bb99902e113 in branch refs/heads/master 
from [~mice]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dedec16 ]

fix CLOUDSTACK-1698


> VMSnapshot Limitations Violation: Detaching/Attaching VM volume is not 
> allowed if there are VM Snapshots- Currently it is allowed 
> --
>
> Key: CLOUDSTACK-1698
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1698
> 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: Chandan Purushothama
>Assignee: Mice Xia
>Priority: Critical
> Fix For: 4.2.0
>
>
> 
> Steps to Reproduce:
> 
> Case 1:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" type VM snapshot for a VM 
> which has 1 datadisk. 
> 2. Detach the existing data disk.
> Case 2:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" for a VM which has 1 datadisk. 
> 2. Attach a new data disk.
> ==
> Expected Results as per FS mentioned Limitations:
> ==
> Case 1 and Case 2 should result in rejection of the detacj/attach operations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1878) ZWPS:NPE while enabling local storage while zone wide primary storage in the zone

[Abhinandan Prateek (JIRA)]

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

Abhinandan Prateek reassigned CLOUDSTACK-1878:
--

Assignee: edison su

> ZWPS:NPE while  enabling local storage while zone wide primary storage in the 
> zone 
> ---
>
> Key: CLOUDSTACK-1878
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1878
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: edison su
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> ==
> Have a KVM zone with zone wide primary storage and cluster wide primary 
> storage,
> Modify the zone to use local storage
> Now, host has a problem connecting to  existing storage pools(zone wide 
> storage pools)
> l) Sending Connect to listener: StoragePoolMonitor
> 2013-04-02 16:01:59,609 INFO  [network.security.SecurityGroupListener] 
> (AgentConnectTaskPool-4:null) Received a host startup notification
> 2013-04-02 16:01:59,609 DEBUG [agent.manager.AgentManagerImpl] 
> (AgentConnectTaskPool-4:null) Sending Connect to listener: StoragePoolMonitor
> 2013-04-02 16:01:59,640 DEBUG [storage.listener.StoragePoolMonitor] 
> (AgentConnectTaskPool-3:null) Host 5 connected, sending down storage pool 
> information ...
> 2013-04-02 16:01:59,650 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-1:null) Seq 5-159907842: Processing:  { Ans: , MgmtId: 
> 7566222426160, via: 5, Ver: v1, Flags: 10, 
> [{"Answer":{"result":true,"wait":0}}] }
> 2013-04-02 16:01:59,651 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-15:null) Seq 1-2100232194: Processing:  { Ans: , 
> MgmtId: 7566222426160, via: 1, Ver: v1, Flags: 10, 
> [{"Answer":{"result":true,"wait":0}}] }
> 2013-04-02 16:01:59,659 DEBUG [storage.listener.StoragePoolMonitor] 
> (AgentConnectTaskPool-4:null) Host 1 connected, sending down storage pool 
> information ...
> 2013-04-02 16:01:59,718 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-2:null) Seq 1-2100232194: Processing:  { Ans: , MgmtId: 
> 7566222426160, via: 1, Ver: v1, Flags: 10, 
> [{"Answer":{"result":true,"details":"","wait":0}}] }
> 2013-04-02 16:01:59,721 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-3:null) Seq 5-159907842: Processing:  { Ans: , MgmtId: 
> 7566222426160, via: 5, Ver: v1, Flags: 10, 
> [{"Answer":{"result":true,"details":"","wait":0}}] }
> 2013-04-02 16:01:59,723 DEBUG [cloud.storage.StorageManagerImpl] 
> (AgentConnectTaskPool-4:null) Adding pool null to  host 1
> 2013-04-02 16:01:59,736 DEBUG [cloud.storage.StorageManagerImpl] 
> (AgentConnectTaskPool-3:null) Adding pool null to  host 5
> 2013-04-02 16:01:59,744 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-4:null) Seq 4-590675969: Processing:  { Ans: , MgmtId: 
> 7566222426160, via: 4, Ver: v1, Flags: 110, 
> [{"Answer":{"result":true,"wait":0}}] }
> 2013-04-02 16:01:59,744 DEBUG [agent.transport.Request] 
> (AgentConnectTaskPool-2:null) Seq 4-590675969: Received:  { Ans: , MgmtId: 
> 7566222426160, via: 4, Ver: v1, Flags: 110, { Answer } }
> 2013-04-02 16:01:59,744 INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl] 
> (AgentConnectTaskPool-2:null) Successfully sent out command to start HTTP 
> handling in console proxy agent
> 2013-04-02 16:01:59,753 DEBUG [agent.manager.AgentAttache] 
> (AgentManager-Handler-4:null) Seq 4-590675969: No more commands found
> 2013-04-02 16:01:59,784 DEBUG [agent.transport.Request] 
> (AgentConnectTaskPool-2:null) Seq 4-590675970: Sending  { Cmd , MgmtId: 
> 7566222426160, via: 4, Ver: v1, Flags: 100111, 
> [{"ReadyCommand":{"dcId":1,"hostId":4,"wait":0}}] }
> 2013-04-02 16:01:59,804 DEBUG [agent.transport.Request] 
> (AgentConnectTaskPool-4:null) Seq 1-2100232195: Sending  { Cmd , MgmtId: 
> 7566222426160, via: 1, Ver: v1, Flags: 100011, 
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":1,"uuid":"130ba00a-323f-3b42-b738-0d9580fc21a0","host":"10.147.28.7","path":"/export/home/talluri/kvmp1","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//130ba00a-323f-3b42-b738-0d9580fc21a0","wait":0}}]
>  }
> 2013-04-02 16:01:59,806 DEBUG [agent.transport.Request] 
> (AgentConnectTaskPool-3:null) Seq 5-159907843: Sending  { Cmd , MgmtId: 
> 7566222426160, via: 5, Ver: v1, Flags: 100011, 
> [{"ModifyStoragePoolCommand":{"add":true,"pool":{"id":3,"uuid":"763f7983-6cb8-3ccb-bc4d-30a36d015b21","host":"10.147.28.7","path":"/export/home/talluri/zwps","port":2049,"type":"NetworkFilesystem"},"localPath":"/mnt//763f7983-6cb8-3ccb-bc4d-30a36d015b21","wait":0}}]
>  }
> 2013-04-02 16:01:59,835 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-6:null) Seq 4-590675

[jira] [Commented] (CLOUDSTACK-1700) VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported as a success instead of failure

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619659#comment-13619659
 ] 

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

Commit 4edef1fd305891beb5393b722e96f4a140934f9f in branch refs/heads/master 
from [~mice]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4edef1f ]

fix CLOUDSTACK-1700


> VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported 
> as a success instead of failure
> ---
>
> Key: CLOUDSTACK-1700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1700
> 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: Chandan Purushothama
>Assignee: Mice Xia
> Fix For: 4.2.0
>
>
> ==
> Steps to Reproduce the Bug:
> ==
> 1. CreateVMSnapshot on a VM running on a XenServer that has evaluation license
> ===
> Observations:
> ===
> **JobStatus = 1 implies Success . Observe the Management Server Log Snippet 
> below**
> 2013-03-15 17:40:34,781 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-5:null) submit async job-108, details: AsyncJobVO {id:108, 
> userId: 3, accountId: 3, sessionKey: null, instanceType: null, instanceId: 
> 18, cmd: 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"18","response":"json","sessionkey":"vrHJOCEZnUh0hUqgBw0EUdEvjqs\u003d","virtualmachineid":"41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a","ctxUserId":"3","snapshotmemory":"true","description":"Xen-boron-VMSnapshot-7-1","name":"Xen-boron-VMSnapshot-7-1","_":"1363394459368","ctxAccountId":"3","ctxStartEventId":"164"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7200344900649, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-15 17:40:34,783 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) 
> ===END===  10.216.133.69 -- GET  
> command=createVMSnapshot&virtualmachineid=41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a&snapshotmemory=true&name=Xen-boron-VMSnapshot-7-1&description=Xen-boron-VMSnapshot-7-1&response=json&sessionkey=vrHJOCEZnUh0hUqgBw0EUdEvjqs%3D&_=1363394459368
> 2013-03-15 17:40:34,784 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-5:job-108) Executing 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd for 
> job-108
> 2013-03-15 17:40:34,793 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-5:job-108) Access to Acct[3-boron] granted to Acct[3-boron] by 
> DomainChecker
> 2013-03-15 17:40:34,844 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Sending  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSnapshot-7-1"},"vmName":"i-3-14-VMSNAP","guestOSType":"CentOS
>  5.3 (64-bit)","wait":0}}] }
> 2013-03-15 17:40:34,845 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Executing:  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSn

[jira] [Resolved] (CLOUDSTACK-1698) VMSnapshot Limitations Violation: Detaching/Attaching VM volume is not allowed if there are VM Snapshots- Currently it is allowed

[Mice Xia (JIRA)]

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

Mice Xia resolved CLOUDSTACK-1698.
--

Resolution: Fixed
  Assignee: Chandan Purushothama  (was: Mice Xia)

add checks when attach/detach volumes

master: dedec164e8cce17b861d517fe8e29bb99902e113


> VMSnapshot Limitations Violation: Detaching/Attaching VM volume is not 
> allowed if there are VM Snapshots- Currently it is allowed 
> --
>
> Key: CLOUDSTACK-1698
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1698
> 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: Chandan Purushothama
>Assignee: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
>
> 
> Steps to Reproduce:
> 
> Case 1:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" type VM snapshot for a VM 
> which has 1 datadisk. 
> 2. Detach the existing data disk.
> Case 2:
> 1. Create a "Disk" and "DiskAndMemorySnapshot" for a VM which has 1 datadisk. 
> 2. Attach a new data disk.
> ==
> Expected Results as per FS mentioned Limitations:
> ==
> Case 1 and Case 2 should result in rejection of the detacj/attach operations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1888) [UI]Child Domain Admin accounts can not set/update the resource limits

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1888:
-

Fix Version/s: 4.2.0

> [UI]Child Domain Admin accounts can not set/update the  resource limits
> ---
>
> Key: CLOUDSTACK-1888
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1888
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Sonny Chhen
> Fix For: 4.2.0
>
> Attachments: DomainAdminView.png
>
>
> Setup: Advanced Networking zone with Xen 6.1 [4.2]
> Steps:
> 1. Create Child domain (CDC1) under ROOT 
> 2. Create Domain account CDC1Admin1 under Child Domain CDC1
> 3. Access Management Server as this domain admin account
> Observation: Child Domain Admin accounts can not set/update the  resource 
> limits. It is supported via API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1707) VMSnapshot on XenServer: RevertToSnapshotCmd stops a running VM on XenServer

[Mice Xia (JIRA)]

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

Mice Xia resolved CLOUDSTACK-1707.
--

Resolution: Fixed

if its type is 'Disk', that's the expected result, because snapshot does not 
contain memory 

> VMSnapshot on XenServer: RevertToSnapshotCmd stops a running VM on XenServer
> 
>
> Key: CLOUDSTACK-1707
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1707
> 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: Chandan Purushothama
>Assignee: Mice Xia
>Priority: Critical
> Fix For: 4.2.0
>
>
> 
> Steps to Reproduce:
> 
> 1. Deploy a VM on the XenServer with a Data disk.
> 2. When the VM is running, take a VMSnapshot of the VM.
> 3. Revert to the VMSnapshot and observe the VM slip into Stopped State
> ===
> Observations:
> ===
> **Job Info from the Management Server Log**
>  [root@asfmgmt ~]# grep -i "job-111" 
> /var/log/cloudstack/management/management-server.log
> 2013-03-18 11:25:24,949 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-6:null) submit async job-111, details: AsyncJobVO {id:111, 
> userId: 3, accountId: 3, sessionKey: null, instanceType: null, instanceId: 
> null, cmd: 
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToSnapshotCmd, 
> cmdOriginator: null, cmdInfo: 
> {"response":"json","sessionkey":"lyydAZodgu/Ql7NdWAQPDahV7pY\u003d","ctxUserId":"3","_":"1363631153401","vmsnapshotid":"d3567079-90ce-44b7-8db1-42df53966877","ctxAccountId":"3","ctxStartEventId":"169"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7200344900649, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-18 11:25:24,965 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-8:job-111) Executing 
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToSnapshotCmd for 
> job-111
> 2013-03-18 11:25:24,987 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-8:job-111) Access to 
> com.cloud.vm.snapshot.VMSnapshotVO$$EnhancerByCGLIB$$212b9a33@1d34e286 
> granted to Acct[3-boron] by DomainChecker
> 2013-03-18 11:25:25,003 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-8:job-111) VM state transitted from :Running to Stopping with 
> event: StopRequestedvm's original host id: 5 new host id: 5 host id before 
> state transition: 5
> 2013-03-18 11:25:25,005 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Sending  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100111, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-3-14-VMSNAP","wait":0}}] }
> 2013-03-18 11:25:25,005 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Executing:  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100111, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-3-14-VMSNAP","wait":0}}] }
> 2013-03-18 11:26:19,327 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Received:  { Ans: , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 110, { StopAnswer } }
> 2013-03-18 11:26:19,329 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-8:job-111) VM[User|xen-boron-VM-7] is stopped on the host.  
> Proceeding to release resource held.
> 2013-03-18 11:26:19,355 DEBUG [cloud.network.NetworkModelImpl] 
> (Job-Executor-8:job-111) Service SecurityGroup is not supported in the 
> network id=204
> 2013-03-18 11:26:19,392 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Changing active number of nics for network id=204 on 
> -1
> 2013-03-18 11:26:19,427 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking ElasticLoadBalancerElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,430 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking NiciraNvpElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,431 DEBUG [network.element.NiciraNvpElement] 
> (Job-Executor-8:job-111) Checking if NiciraNvpElement can handle service 
> Connectivity on network boron-TestNetwork-1
> 2013-03-18 11:26:19,432 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking BigSwitchVnsElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,432 DEBUG [network.element.BigSwitchVnsElement] 
> (Job-Executor-8:job-111) Checking if BigSwitchVnsElement can handle service 
> Connectivity on network boron-TestNe

[jira] [Assigned] (CLOUDSTACK-1707) VMSnapshot on XenServer: RevertToSnapshotCmd stops a running VM on XenServer

[Mice Xia (JIRA)]

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

Mice Xia reassigned CLOUDSTACK-1707:


Assignee: Chandan Purushothama  (was: Mice Xia)

> VMSnapshot on XenServer: RevertToSnapshotCmd stops a running VM on XenServer
> 
>
> Key: CLOUDSTACK-1707
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1707
> 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: Chandan Purushothama
>Assignee: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
>
> 
> Steps to Reproduce:
> 
> 1. Deploy a VM on the XenServer with a Data disk.
> 2. When the VM is running, take a VMSnapshot of the VM.
> 3. Revert to the VMSnapshot and observe the VM slip into Stopped State
> ===
> Observations:
> ===
> **Job Info from the Management Server Log**
>  [root@asfmgmt ~]# grep -i "job-111" 
> /var/log/cloudstack/management/management-server.log
> 2013-03-18 11:25:24,949 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-6:null) submit async job-111, details: AsyncJobVO {id:111, 
> userId: 3, accountId: 3, sessionKey: null, instanceType: null, instanceId: 
> null, cmd: 
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToSnapshotCmd, 
> cmdOriginator: null, cmdInfo: 
> {"response":"json","sessionkey":"lyydAZodgu/Ql7NdWAQPDahV7pY\u003d","ctxUserId":"3","_":"1363631153401","vmsnapshotid":"d3567079-90ce-44b7-8db1-42df53966877","ctxAccountId":"3","ctxStartEventId":"169"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7200344900649, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-18 11:25:24,965 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-8:job-111) Executing 
> org.apache.cloudstack.api.command.user.vmsnapshot.RevertToSnapshotCmd for 
> job-111
> 2013-03-18 11:25:24,987 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-8:job-111) Access to 
> com.cloud.vm.snapshot.VMSnapshotVO$$EnhancerByCGLIB$$212b9a33@1d34e286 
> granted to Acct[3-boron] by DomainChecker
> 2013-03-18 11:25:25,003 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-8:job-111) VM state transitted from :Running to Stopping with 
> event: StopRequestedvm's original host id: 5 new host id: 5 host id before 
> state transition: 5
> 2013-03-18 11:25:25,005 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Sending  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100111, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-3-14-VMSNAP","wait":0}}] }
> 2013-03-18 11:25:25,005 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Executing:  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100111, 
> [{"StopCommand":{"isProxy":false,"vmName":"i-3-14-VMSNAP","wait":0}}] }
> 2013-03-18 11:26:19,327 DEBUG [agent.transport.Request] 
> (Job-Executor-8:job-111) Seq 5-1223558560: Received:  { Ans: , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 110, { StopAnswer } }
> 2013-03-18 11:26:19,329 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-8:job-111) VM[User|xen-boron-VM-7] is stopped on the host.  
> Proceeding to release resource held.
> 2013-03-18 11:26:19,355 DEBUG [cloud.network.NetworkModelImpl] 
> (Job-Executor-8:job-111) Service SecurityGroup is not supported in the 
> network id=204
> 2013-03-18 11:26:19,392 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Changing active number of nics for network id=204 on 
> -1
> 2013-03-18 11:26:19,427 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking ElasticLoadBalancerElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,430 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking NiciraNvpElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,431 DEBUG [network.element.NiciraNvpElement] 
> (Job-Executor-8:job-111) Checking if NiciraNvpElement can handle service 
> Connectivity on network boron-TestNetwork-1
> 2013-03-18 11:26:19,432 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-8:job-111) Asking BigSwitchVnsElement to release 
> Nic[23-14-7203787c-a822-4a42-8e47-1873ff53da53-10.1.1.115]
> 2013-03-18 11:26:19,432 DEBUG [network.element.BigSwitchVnsElement] 
> (Job-Executor-8:job-111) Checking if BigSwitchVnsElement can handle service 
> Connectivity on network boron-TestNetwork-1
> 2013-03-18 11:26:19,433 DEBUG [cloud.network.Networ

[jira] [Assigned] (CLOUDSTACK-1700) VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported as a success instead of failure

[Mice Xia (JIRA)]

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

Mice Xia reassigned CLOUDSTACK-1700:


Assignee: Chandan Purushothama  (was: Mice Xia)

> VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported 
> as a success instead of failure
> ---
>
> Key: CLOUDSTACK-1700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1700
> 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: Chandan Purushothama
>Assignee: Chandan Purushothama
> Fix For: 4.2.0
>
>
> ==
> Steps to Reproduce the Bug:
> ==
> 1. CreateVMSnapshot on a VM running on a XenServer that has evaluation license
> ===
> Observations:
> ===
> **JobStatus = 1 implies Success . Observe the Management Server Log Snippet 
> below**
> 2013-03-15 17:40:34,781 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-5:null) submit async job-108, details: AsyncJobVO {id:108, 
> userId: 3, accountId: 3, sessionKey: null, instanceType: null, instanceId: 
> 18, cmd: 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"18","response":"json","sessionkey":"vrHJOCEZnUh0hUqgBw0EUdEvjqs\u003d","virtualmachineid":"41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a","ctxUserId":"3","snapshotmemory":"true","description":"Xen-boron-VMSnapshot-7-1","name":"Xen-boron-VMSnapshot-7-1","_":"1363394459368","ctxAccountId":"3","ctxStartEventId":"164"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7200344900649, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-15 17:40:34,783 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) 
> ===END===  10.216.133.69 -- GET  
> command=createVMSnapshot&virtualmachineid=41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a&snapshotmemory=true&name=Xen-boron-VMSnapshot-7-1&description=Xen-boron-VMSnapshot-7-1&response=json&sessionkey=vrHJOCEZnUh0hUqgBw0EUdEvjqs%3D&_=1363394459368
> 2013-03-15 17:40:34,784 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-5:job-108) Executing 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd for 
> job-108
> 2013-03-15 17:40:34,793 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-5:job-108) Access to Acct[3-boron] granted to Acct[3-boron] by 
> DomainChecker
> 2013-03-15 17:40:34,844 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Sending  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSnapshot-7-1"},"vmName":"i-3-14-VMSNAP","guestOSType":"CentOS
>  5.3 (64-bit)","wait":0}}] }
> 2013-03-15 17:40:34,845 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Executing:  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSnapshot-7-1"},"vmName":"i-3-14-VMSNAP","guestOSType":"CentOS
>  5.3 (64-bit)","wait":0}}] }
> 2013-03-15 17:40:34,845 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-6:null) Seq 5-1223557136: Executing request
> 2013-03-

[jira] [Commented] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[Rohit Yadav (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619666#comment-13619666
 ] 

Rohit Yadav commented on CLOUDSTACK-1839:
-

Chip, I won't be be able to have spare time in next 3 days for db related 
fixes, pl. reassign. Meanwhile I'll try to help out on some cli, systemvm 
issues.

> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> -
>
> Key: CLOUDSTACK-1839
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1839
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Upgrade 4.0 -> 4.1 
>Reporter: Sangeetha Hariharan
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: upgrade-db-dumps.rar
>
>
> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> Scenario 1:
> Fresh install of 4.0.
> Upgrade the set up to 4.1.
> Scenario 2:
> Fresh install of 4.1 and started the management server.
> Comparing the schema between Scenario1 and Scenario2 shows that the Upgraded 
> DB has lot more keys and indexes for many tables compare to the fresh 
> installed 4.1 DB.
> Will attach database dump for both the cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1867) [VMware] [SystemVMTemplate] is not working with latest cloudstack master

[Rohit Yadav (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619667#comment-13619667
 ] 

Rohit Yadav commented on CLOUDSTACK-1867:
-

This is same as: https://issues.apache.org/jira/browse/CLOUDSTACK-1774
I just need to unzip ova, convert ovf to vmx and repackage using ovftool... You 
may do that manually, or I can try to automate this on j.c.o later.

> [VMware] [SystemVMTemplate] is not working with latest cloudstack master
> 
>
> Key: CLOUDSTACK-1867
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1867
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: commit # 355589c1f0c583cbbdc601f74dba504064f81bac
> - Advanced zone with VMware cluster
>Reporter: venkata swamybabu budumuru
>Assignee: Rohit Yadav
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: logs.01.tgz, systemvmTemplate.JPG, xml.txt
>
>
> Steps to reproduce :
> 1. Took the latest system vm template from jenkins 
> http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-2013-03-27-master-vmware.ova
> 2. Seeded the above template using the following 
> /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
>  -m /tmp/1/secondary.campo.vmw.GOLD/ -u 
> http://10.147.28.7/templates/campo/templates/systemvmtemplate-2013-03-27-master-vmware.ova
>  -h vmware -F
> 3. Tried to bring up the advanced zone using ESXi 5.1 
> Observations : 
> (i) Found the following error in vmops.log
> 2013-04-01 11:16:33,856 INFO  [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-6:10.147.40.12) Secondary storage mount point: 
> /mnt/VM/7280707764394.cc4bce7
> 2013-04-01 11:16:33,863 DEBUG [cloud.alert.AlertManagerImpl] 
> (CapacityChecker:null) Done running Capacity Checker ...
> 2013-04-01 11:16:34,832 ERROR [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-6:10.147.40.12) Unable to execute PrimaryStorageDownloadCommand 
> due to exception
> javax.xml.ws.soap.SOAPFaultException:
> Required parameter spec is missing
> while parsing call information for method ImportVApp
> at line 1, column 110
> while parsing SOAP body
> at line 1, column 102
> while parsing SOAP envelope
> at line 1, column 38
> while parsing HTTP request for method importVApp
> on object of type vim.ResourcePool
> at line 1, column 0
> at 
> com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at 
> com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119)
> at 
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
> at 
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
> at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
> at sun.proxy.$Proxy89.importVApp(Unknown Source)
> at 
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.importVmFromOVF(HypervisorHostHelper.java:995)
> at 
> com.cloud.hypervisor.vmware.mo.HostMO.importVmFromOVF(HostMO.java:681)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:478)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:153)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3660)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:414)
> 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:1146)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 11:16:34,836 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-6:null) Seq 5-37990: Response Received:
> 

[jira] [Resolved] (CLOUDSTACK-1700) VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported as a success instead of failure

[Mice Xia (JIRA)]

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

Mice Xia resolved CLOUDSTACK-1700.
--

Resolution: Fixed

> VMSnapshot: In spite of CreateVMSnapshotCmd failure - Async Job is reported 
> as a success instead of failure
> ---
>
> Key: CLOUDSTACK-1700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1700
> 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: Chandan Purushothama
>Assignee: Mice Xia
> Fix For: 4.2.0
>
>
> ==
> Steps to Reproduce the Bug:
> ==
> 1. CreateVMSnapshot on a VM running on a XenServer that has evaluation license
> ===
> Observations:
> ===
> **JobStatus = 1 implies Success . Observe the Management Server Log Snippet 
> below**
> 2013-03-15 17:40:34,781 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-5:null) submit async job-108, details: AsyncJobVO {id:108, 
> userId: 3, accountId: 3, sessionKey: null, instanceType: null, instanceId: 
> 18, cmd: 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"18","response":"json","sessionkey":"vrHJOCEZnUh0hUqgBw0EUdEvjqs\u003d","virtualmachineid":"41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a","ctxUserId":"3","snapshotmemory":"true","description":"Xen-boron-VMSnapshot-7-1","name":"Xen-boron-VMSnapshot-7-1","_":"1363394459368","ctxAccountId":"3","ctxStartEventId":"164"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7200344900649, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-15 17:40:34,783 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) 
> ===END===  10.216.133.69 -- GET  
> command=createVMSnapshot&virtualmachineid=41fce8fd-9fdf-4f2f-bf04-c7173f2e3c2a&snapshotmemory=true&name=Xen-boron-VMSnapshot-7-1&description=Xen-boron-VMSnapshot-7-1&response=json&sessionkey=vrHJOCEZnUh0hUqgBw0EUdEvjqs%3D&_=1363394459368
> 2013-03-15 17:40:34,784 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-5:job-108) Executing 
> org.apache.cloudstack.api.command.user.vmsnapshot.CreateVMSnapshotCmd for 
> job-108
> 2013-03-15 17:40:34,793 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-5:job-108) Access to Acct[3-boron] granted to Acct[3-boron] by 
> DomainChecker
> 2013-03-15 17:40:34,844 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Sending  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSnapshot-7-1"},"vmName":"i-3-14-VMSNAP","guestOSType":"CentOS
>  5.3 (64-bit)","wait":0}}] }
> 2013-03-15 17:40:34,845 DEBUG [agent.transport.Request] 
> (Job-Executor-5:job-108) Seq 5-1223557136: Executing:  { Cmd , MgmtId: 
> 7200344900649, via: 5, Ver: v1, Flags: 100011, 
> [{"CreateVMSnapshotCommand":{"vmState":"Running","volumeTOs":[{"id":23,"name":"ROOT-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"07389d9c-6b97-4ef8-9db0-4167afef078e","size":21474836480,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":0},{"id":24,"name":"DATA-14","mountPoint":"/export/home/chandan/asf4-131-170/primary2","path":"b83505e0-4dbb-460b-8e8d-01b0fe205146","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"067fc155-b77d-3cd4-9599-579c5123a806","deviceId":1}],"target":{"id":18,"snapshotName":"i-3-14-VMSNAP_VS_20130316004034","type":"DiskAndMemory","current":false,"description":"Xen-boron-VMSnapshot-7-1"},"vmName":"i-3-14-VMSNAP","guestOSType":"CentOS
>  5.3 (64-bit)","wait":0}}] }
> 2013-03-15 17:40:34,845 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-6:null) Seq 5-1223557136: Executing request
> 2013-03-15 17:40:34,879 DEBUG [cloud.api.ApiServlet] (

[jira] [Assigned] (CLOUDSTACK-1875) Add JSON output into cloudmonkey

[Rohit Yadav (JIRA)]

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

Rohit Yadav reassigned CLOUDSTACK-1875:
---

Assignee: Rohit Yadav

> Add JSON output into cloudmonkey
> 
>
> Key: CLOUDSTACK-1875
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1875
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Cloudmonkey
>Affects Versions: 4.1.0, Future
>Reporter: Justin Grudzien
>Assignee: Rohit Yadav
>Priority: Minor
>  Labels: newbie, patch
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Data in JSON format is very easy to read for large data sets. Presently, 
> cloudmonkey supports tabular or line based output and looking at large output 
> tends to be problematic. By adding JSON output with filtering, a user can 
> more easily process and consume data. The following items should make 
> cloudmonkey data more easily consumable:
> 1. Need to format empty return messages with proper JSON messaging.
> 2. Need to standardize JSON output messaging.
> A. Add return code [Error|Success] to all calls.
> B. Add called API verb.
> 3. Count is not decreased in output set when filtering completely eliminates 
> a result.
> 4. JSON printing needs to be implemented manually to support colors. Right 
> now json.dumps() pretty prints the output and changing the keys to support 
> colors is problematic.
> 5. Color tagging needs to be added to JSON printing.
> 6. Error messages need to have proper JSON formatting.
> 7. Make color a passable option to a command instead of a config parameter. 
> (i.e. list users account=grudzien color=true)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1879) NPE while migrating volume

[Ram Ganesh (JIRA)]

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

Ram Ganesh updated CLOUDSTACK-1879:
---

Assignee: Devdeep Singh  (was: edison su)

> NPE while migrating volume
> --
>
> Key: CLOUDSTACK-1879
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1879
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Devdeep Singh
>Priority: Blocker
> Fix For: 4.2.0
>
>
> try to migrate a volume from one primary storage to another (irrespective of 
> the storage's scope-zone,cluster)
>  ===START===  10.252.249.129 -- GET  
> command=migrateVolume&storageid=763f7983-6cb8-3ccb-bc4d-30a36d015b21&volumeid=880958ba-8667-4ebe-8b03-cb32f2dbc3c9&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881190825
> 2013-04-02 16:35:55,829 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-4:null) submit async job-101, details: AsyncJobVO {id:101, 
> userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 
> null, cmd: org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, 
> cmdOriginator: null, cmdInfo: 
> {"response":"json","sessionkey":"FDm4fMQ93FjXjXmoBg/KrL6WrTU\u003d","ctxUserId":"2","storageid":"763f7983-6cb8-3ccb-bc4d-30a36d015b21","_":"1364881190825","volumeid":"880958ba-8667-4ebe-8b03-cb32f2dbc3c9","ctxAccountId":"2","ctxStartEventId":"360"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-04-02 16:35:55,832 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) 
> ===END===  10.252.249.129 -- GET  
> command=migrateVolume&storageid=763f7983-6cb8-3ccb-bc4d-30a36d015b21&volumeid=880958ba-8667-4ebe-8b03-cb32f2dbc3c9&response=json&sessionkey=FDm4fMQ93FjXjXmoBg%2FKrL6WrTU%3D&_=1364881190825
> 2013-04-02 16:35:55,836 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Executing 
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-101
> 2013-04-02 16:35:55,869 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-10:job-101) migrate volume failed:java.lang.NullPointerException
> 2013-04-02 16:35:55,869 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Complete async job-101, jobStatus: 1, resultCode: 
> 0, result: null
> 2013-04-02 16:35:55,878 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-10:job-101) Done executing 
> org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-101

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1889:
-

Attachment: resources.png

> [UI] Consumed Resource usage details are not available for all the resources
> 
>
> Key: CLOUDSTACK-1889
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1889
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Sonny Chhen
> Attachments: resources.png
>
>
> Setup: Advanced Networking zone with Xen 6.1 [4.2]
> Steps:
> 1. Create Child domain (CDC1) under ROOT
> 2. Create Domain account CDC1Admin1 under Child Domain CDC1 
> 3. Access Management Server as this domain admin account
> 4. Deploy VM with this account 
> 5. Tried to update resource Count
> Observation: Consumed Resource usage details are not available for all the 
> resources.  It is available only with Total of VM  , Total of IP Address   , 
> Bytes Received ,Bytes Sent.
> API provides the details. 
> http://10.102.192.208:8096/client/api?command=updateResourceCount&domainid=2&resourcetype=9&account=cdc1admin1
>  cloud-stack-version="4.2.0-SNAPSHOT">1cdc1admin1e8377899-c351-47a2-aed5-92c624eebae5cdc19512

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[Sailaja Mada (JIRA)]

Sailaja Mada created CLOUDSTACK-1889:


 Summary: [UI] Consumed Resource usage details are not available 
for all the resources
 Key: CLOUDSTACK-1889
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1889
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Sonny Chhen
 Attachments: resources.png

Setup: Advanced Networking zone with Xen 6.1 [4.2]

Steps:

1. Create Child domain (CDC1) under ROOT
2. Create Domain account CDC1Admin1 under Child Domain CDC1 
3. Access Management Server as this domain admin account
4. Deploy VM with this account 
5. Tried to update resource Count

Observation: Consumed Resource usage details are not available for all the 
resources.  It is available only with Total of VM, Total of IP Address   , 
Bytes Received ,Bytes Sent.

API provides the details. 

http://10.102.192.208:8096/client/api?command=updateResourceCount&domainid=2&resourcetype=9&account=cdc1admin1

1cdc1admin1e8377899-c351-47a2-aed5-92c624eebae5cdc19512


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1887) UI: remove "host" from the drop down list for add primary storage screen

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619708#comment-13619708
 ] 

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

Commit 3d8afb0cfbcf20f4644fb58171f6c587c60f50ba in branch refs/heads/master 
from [~pranav.sax...@citrix.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3d8afb0 ]

CLOUDSTACK-1887:removing the host option from the scope field for primary 
storage


> UI: remove "host" from the drop down list for add primary storage screen
> 
>
> Key: CLOUDSTACK-1887
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1887
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Pranav Saxena
>Priority: Critical
> Fix For: 4.2.0
>
>
> remove "host" from the drop down list for add primary storage screen

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Sailaja Mada (JIRA)]

Sailaja Mada created CLOUDSTACK-1890:


 Summary: listProjects is not listing state in the response
 Key: CLOUDSTACK-1890
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API, UI
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Min Chen
 Attachments: projview.png

Setup:  Advanced Networking Zone with Xen 6.1 [4.2]

Steps:

1. Create projects as admin & Child domain account 
2. Tried to list all the projects.

Observation:
1) listProjects is not listing state in the response
2) State of the project from UI displayed as blank [Attached the sanp]

2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
(userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
-- GET 
command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
 200 { "listprojectsresponse" : { "count":2 ,"project" : [  
{"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
 
{"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
 ] } }

http://10.102.192.208:8096/client/api?command=listProjects&listAll=true


2
ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
proj1
e8377899-c351-47a2-aed5-92c624eebae5
cdc1cdc1admin1
532eaa39-2daf-41ee-ad37-b168f0a34916
proj1
proj1
c579ec3a-9a89-11e2-8880-ca27ffbee488
ROOT<
account>admin


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1890:
-

Attachment: projview.png

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1890:
-

Fix Version/s: 4.2.0

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Sailaja Mada (JIRA)]

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

Sailaja Mada updated CLOUDSTACK-1890:
-

Fix Version/s: 4.1.0

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1891) [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not happening properly after releasing the IP on which LB was configured

[Abhinav Roy (JIRA)]

Abhinav Roy created CLOUDSTACK-1891:
---

 Summary: [AWS style Health Checks]After upgrade from 4.0 to 4.2 , 
cleanup not happening properly after releasing the IP on which LB was configured
 Key: CLOUDSTACK-1891
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1891
 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: Abhinav Roy
Assignee: Rajesh Battala
 Fix For: 4.2.0


Steps :
==
1. Upgrade MS from 4.0 to 4.2
2. Go to the existing Netscaler network, acquire IP and create a LB rule.
3. configure health checks on the LB rule.
4. Release the IP acquired in step 2


Expected behaviour :
=
IP should be relased, LB rule and the LB monitor created on NS device also 
should be deleted.


Observed behaviour :

IP is released
LB rule doesn't get deleted on CS but the corresponding lb vserver is deleted 
from NS
LB health check policy gets deleted on CS but the corresponding monitor doesn't 
get deleted from NS



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-301) Nexus 1000v DVS integration is not functional

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619738#comment-13619738
 ] 

ASF subversion and git services commented on CLOUDSTACK-301:


Commit 009749fb796bc935f610921f1bdc71e8d993198d in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=009749f ]

CLOUDSTACK-301 Nexus 1000v DVS integration is not functional

Moved validateVSMCluster method from CiscoNexusVSMDeviceManagerImpl to 
CiscoNexusVSMElement.

Signed-off-by: Sateesh Chodapuneedi 


> Nexus 1000v DVS integration is not functional
> -
>
> Key: CLOUDSTACK-301
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-301
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: pre-4.0.0
>Reporter: Sailaja Mada
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: api-server.log, catalina.out, management-server.log
>
>
> Setup:  Management Server [ RHEL 6.3]  ,VMWARE - ESXi5   , Nexus : 
> Nexus1000v.4.2.1.SV1.5.1 
> Build :CloudStack-non-OSS-106.tar 
> Steps:
> 1. Deploy VSM @ Vcenter 
> 2. Create port-profile sailajapp
> 3. Set global setting vmware.use.nexus.vswitch to true
> 4. Tried to configure advanced Zone with traffic lable as sailajapp
> Observation:
> It Failed to add Cluster with Nexus Switch .
> ERROR Log:
> 2012-10-09 14:10:04,301 INFO  [hypervisor.vmware.VmwareServerDiscoverer] 
> (catalina-exec-23:null) Detected private network label : sailajapp
> 2012-10-09 14:10:04,303 INFO  [hypervisor.vmware.VmwareServerDiscoverer] 
> (catalina-exec-23:null) Detected public network label : sailajapp
> 2012-10-09 14:10:04,305 INFO  [hypervisor.vmware.VmwareServerDiscoverer] 
> (catalina-exec-23:null) Detected guest network label : sailajapp
> 2012-10-09 14:10:04,310 INFO  [vmware.manager.VmwareManagerImpl] 
> (catalina-exec-23:null) Found empty vsmMapVO.
> 2012-10-09 14:10:04,313 DEBUG [vmware.resource.VmwareContextFactory] 
> (catalina-exec-23:null) initialize VmwareContext. url: 
> https://10.102.125.241/sdk/vimService, username: administrator, password: 
> f**
> 2012-10-09 14:10:13,505 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
> (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage 
> UPintenance mode
> 2012-10-09 14:10:14,053 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 0 routers.
> 2012-10-09 14:10:19,354 INFO  [vmware.manager.VmwareManagerImpl] 
> (catalina-exec-23:null) Calling prepareNetwork : 
> com.cloud.hypervisor.vmware.util.VmwareContext@40e83e52
> 2012-10-09 14:10:19,355 INFO  [vmware.manager.VmwareManagerImpl] 
> (catalina-exec-23:null) Preparing Network on sailajapp
> 2012-10-09 14:10:19,824 INFO  [vmware.mo.HypervisorHostHelper] 
> (catalina-exec-23:null) Found Ethernet port profile sailajapp
> 2012-10-09 14:10:20,298 INFO  [vmware.mo.HypervisorHostHelper] 
> (catalina-exec-23:null) Port profile cloud.private.untagged.0.1-sailajapp not 
> found.
> 2012-10-09 14:10:20,298 ERROR [vmware.mo.HypervisorHostHelper] 
> (catalina-exec-23:null) Failed to retrieve required credentials of Nexus VSM 
> from database.
> 2012-10-09 14:10:20,301 WARN  [hypervisor.vmware.VmwareServerDiscoverer] 
> (catalina-exec-23:null) Unable to connect to Vmware vSphere server. service 
> address: 10.102.125.241
> 2012-10-09 14:10:20,528 WARN  [cloud.resource.ResourceManagerImpl] 
> (catalina-exec-23:null) Unable to find the server resources at 
> http://10.102.125.241/newdc/newcluster
> 2012-10-09 14:10:20,574 WARN  [api.commands.AddClusterCmd] 
> (catalina-exec-23:null) Exception:
> com.cloud.exception.DiscoveryException: Unable to add the external cluster
> at 
> com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:487)
> at 
> com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
> at 
> com.cloud.api.commands.AddClusterCmd.execute(AddClusterCmd.java:153)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
> 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)
> 

[jira] [Created] (CLOUDSTACK-1892) [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a user network is not able to acquire IPs

[Abhinav Roy (JIRA)]

Abhinav Roy created CLOUDSTACK-1892:
---

 Summary: [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2  a 
user network is not able to acquire IPs
 Key: CLOUDSTACK-1892
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1892
 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: Abhinav Roy
Priority: Critical
 Fix For: 4.2.0
 Attachments: upgrade ip aloocation.jpg

Steps :
=
1. Upgrade CS from 4.0 to 4.2
2. Create a user account.
3. Login to the user account and create a network
4. Acquire IPs for the network

Expected behaviour:

IPs should be acquired successfully

Observed behaviour :

IP acuisition fails with  "unable to figure out zone to assign IPs to"




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1892) [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a user network is not able to acquire IPs

[Abhinav Roy (JIRA)]

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

Abhinav Roy updated CLOUDSTACK-1892:


Attachment: upgrade ip aloocation.jpg

Attaching screenshot

> [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2  a user network is not 
> able to acquire IPs
> ---
>
> Key: CLOUDSTACK-1892
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1892
> 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: Abhinav Roy
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: upgrade ip aloocation.jpg
>
>
> Steps :
> =
> 1. Upgrade CS from 4.0 to 4.2
> 2. Create a user account.
> 3. Login to the user account and create a network
> 4. Acquire IPs for the network
> Expected behaviour:
> 
> IPs should be acquired successfully
> Observed behaviour :
> 
> IP acuisition fails with  "unable to figure out zone to assign IPs to"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1891) [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not happening properly after releasing the IP on which LB was configured

[Abhinav Roy (JIRA)]

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

Abhinav Roy updated CLOUDSTACK-1891:


Description: 
Steps :
==
1. Upgrade MS from 4.0 to 4.2
2. Go to the existing Netscaler network, acquire IP and create a LB rule.
3. configure health checks on the LB rule.
4. Release the IP acquired in step 2


Expected behaviour :
=
IP should be relased, LB rule and the LB monitor created on NS device also 
should be deleted.


Observed behaviour :

IP is released
LB rule doesn't get deleted on CS but the corresponding lb vserver is deleted 
from NS
LB health check policy gets deleted on CS but the corresponding monitor doesn't 
get deleted from NS

2013-04-02 17:23:13,735 ERROR [network.resource.NetscalerResource] 
(DirectAgent-29:null) Failed to execute LoadBalancerConfigCommand due to 
com.cloud.utils.exception.ExecutionException: Failed to delete monitor 
:Cloud-Hc-10.102.195.19-22 due to Monitor must be unbound before it can be 
deleted
at 
com.cloud.network.resource.NetscalerResource.removeLBMonitor(NetscalerResource.java:2289)
at 
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:678)
at 
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
at 
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:340)
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-04-02 17:23:13,793 WARN  [network.resource.NetscalerResource] 
(DirectAgent-29:null) Retrying LoadBalancerConfigCommand. Number of retries 
remaining: 1
2013-04-02 17:23:13,823 INFO  [network.resource.NetscalerResource] 
(DirectAgent-29:null) Successfully executed resource LoadBalancerConfigCommand: 
{"loadBalancers":[{"uuid":"eaa5d85c-6d81-43dc-b2a2-9431f2cb9c12","srcIp":"10.102.195.19","srcPort":22,"protocol":"tcp","algorithm":"roundrobin","revoked":true,"alreadyAdded":false,"inline":false,"destinations":[{"destIp":"10.2.113.88","destPort":22,"revoked":true,"alreadyAdded":false},{"destIp":"10.2.112.78","destPort":22,"revoked":true,"alreadyAdded":false}],"healthCheckPolicies":[{"pingPath":"/","responseTime":2,"healthcheckInterval":5,"healthcheckThresshold":2,"unhealthThresshold":1,"revoke":true}]}],"lbStatsVisibility":"guest-network","lbStatsPort":"8081","lbStatsSrcCidrs":"0/0","lbStatsAuth":"admin1:AdMiN123","lbStatsUri":"/admin?stats","accessDetails":{"guest.vlan.tag":"819"},"wait":0}

  was:
Steps :
==
1. Upgrade MS from 4.0 to 4.2
2. Go to the existing Netscaler network, acquire IP and create a LB rule.
3. configure health checks on the LB rule.
4. Release the IP acquired in step 2


Expected behaviour :
=
IP should be relased, LB rule and the LB monitor created on NS device also 
should be deleted.


Observed behaviour :

IP is released
LB rule doesn't get deleted on CS but the corresponding lb vserver is deleted 
from NS
LB health check policy gets deleted on CS but the corresponding monitor doesn't 
get deleted from NS




> [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not 
> happening properly after releasing the IP on which LB was configured
> -
>
> Key: CLOUDSTACK-1891
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1891
> 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: Abhinav Roy
>Assignee: Rajesh Battala
> Fix For: 4.2.0
>
>
> Steps :
> ==
> 1. Upgrade MS from 4.0 to 4.2
> 2. Go to the existing Netscaler network, acquire IP and create a LB rule.
> 3. configure health checks on the LB rule.
> 4. Release the IP acquired in step 2
> Expected behaviour :
> ===

[jira] [Created] (CLOUDSTACK-1893) [AWS Style Health Checks] UI hangs when one tries to create health check policy on a LB rule with VR as LB service provider

[Abhinav Roy (JIRA)]

Abhinav Roy created CLOUDSTACK-1893:
---

 Summary: [AWS Style Health Checks] UI hangs when one tries to 
create health check policy on a LB rule with VR as LB service provider
 Key: CLOUDSTACK-1893
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1893
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Abhinav Roy
 Fix For: 4.2.0
 Attachments: VR LB Health check.jpg

Steps :
=
1. Deploy an advanced zone CS setup
2. Create a network with VR as LB service provider and deploy few VMs on that 
network.
3. Create a LB rule in that network and try to create health check policy on 
that LB rule.


Expected behaviour :
=
1. Since health checks on VR are not supported yet, the process should fail 
gracefully with a error message


Observed behaviour :

The UI hangs with a error message when someone tries to create the health check 
policy

Error seen in MS log

2013-04-02 17:03:22,492 WARN  [user.loadbalancer.CreateLBHealthCheckPolicyCmd] 
(catalina-exec-16:null) Exception: 
com.cloud.exception.InvalidParameterValueException: Failed to create 
HealthCheck policy: Validation Failed (HealthCheck Policy is not supported by 
LB Provider for the LB rule id :)1
at 
com.cloud.network.lb.LoadBalancingRulesManagerImpl.createLBHealthCheckPolicy(LoadBalancingRulesManagerImpl.java:508)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
org.apache.cloudstack.api.command.user.loadbalancer.CreateLBHealthCheckPolicyCmd.create(CreateLBHealthCheckPolicyCmd.java:150)
at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:109)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:401)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:304)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
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-04-02 17:03:22,493 INFO  [cloud.api.ApiServer] (catalina-exec-16:null) 
Failed to create HealthCheck policy: Validation Failed (HealthCheck Policy is 
not supported by LB Provider for the LB rule id :)1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1893) [AWS Style Health Checks] UI hangs when one tries to create health check policy on a LB rule with VR as LB service provider

[Abhinav Roy (JIRA)]

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

Abhinav Roy updated CLOUDSTACK-1893:


Assignee: Pranav Saxena

> [AWS Style Health Checks] UI hangs when one tries to create health check 
> policy on a LB rule with VR as LB service provider
> ---
>
> Key: CLOUDSTACK-1893
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1893
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Abhinav Roy
>Assignee: Pranav Saxena
> Fix For: 4.2.0
>
> Attachments: VR LB Health check.jpg
>
>
> Steps :
> =
> 1. Deploy an advanced zone CS setup
> 2. Create a network with VR as LB service provider and deploy few VMs on that 
> network.
> 3. Create a LB rule in that network and try to create health check policy on 
> that LB rule.
> Expected behaviour :
> =
> 1. Since health checks on VR are not supported yet, the process should fail 
> gracefully with a error message
> Observed behaviour :
> 
> The UI hangs with a error message when someone tries to create the health 
> check policy
> Error seen in MS log
> 2013-04-02 17:03:22,492 WARN  
> [user.loadbalancer.CreateLBHealthCheckPolicyCmd] (catalina-exec-16:null) 
> Exception: 
> com.cloud.exception.InvalidParameterValueException: Failed to create 
> HealthCheck policy: Validation Failed (HealthCheck Policy is not supported by 
> LB Provider for the LB rule id :)1
> at 
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.createLBHealthCheckPolicy(LoadBalancingRulesManagerImpl.java:508)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.loadbalancer.CreateLBHealthCheckPolicyCmd.create(CreateLBHealthCheckPolicyCmd.java:150)
> at 
> com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:109)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:401)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:304)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> 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-04-02 17:03:22,493 INFO  [cloud.api.ApiServer] (catalina-exec-16:null) 
> Failed to create HealthCheck policy: Validation Failed (HealthCheck Policy is 
> not supported by LB Provider for the LB rule id :)1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1893) [AWS Style Health Checks] UI hangs when one tries to create health check policy on a LB rule with VR as LB service provider

[Abhinav Roy (JIRA)]

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

Abhinav Roy updated CLOUDSTACK-1893:


Attachment: VR LB Health check.jpg

Attaching scrrenshot

> [AWS Style Health Checks] UI hangs when one tries to create health check 
> policy on a LB rule with VR as LB service provider
> ---
>
> Key: CLOUDSTACK-1893
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1893
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Abhinav Roy
> Fix For: 4.2.0
>
> Attachments: VR LB Health check.jpg
>
>
> Steps :
> =
> 1. Deploy an advanced zone CS setup
> 2. Create a network with VR as LB service provider and deploy few VMs on that 
> network.
> 3. Create a LB rule in that network and try to create health check policy on 
> that LB rule.
> Expected behaviour :
> =
> 1. Since health checks on VR are not supported yet, the process should fail 
> gracefully with a error message
> Observed behaviour :
> 
> The UI hangs with a error message when someone tries to create the health 
> check policy
> Error seen in MS log
> 2013-04-02 17:03:22,492 WARN  
> [user.loadbalancer.CreateLBHealthCheckPolicyCmd] (catalina-exec-16:null) 
> Exception: 
> com.cloud.exception.InvalidParameterValueException: Failed to create 
> HealthCheck policy: Validation Failed (HealthCheck Policy is not supported by 
> LB Provider for the LB rule id :)1
> at 
> com.cloud.network.lb.LoadBalancingRulesManagerImpl.createLBHealthCheckPolicy(LoadBalancingRulesManagerImpl.java:508)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.loadbalancer.CreateLBHealthCheckPolicyCmd.create(CreateLBHealthCheckPolicyCmd.java:150)
> at 
> com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:109)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:401)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:304)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> 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-04-02 17:03:22,493 INFO  [cloud.api.ApiServer] (catalina-exec-16:null) 
> Failed to create HealthCheck policy: Validation Failed (HealthCheck Policy is 
> not supported by LB Provider for the LB rule id :)1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1894) [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a user is not able to deploy VMs in a project

[Abhinav Roy (JIRA)]

Abhinav Roy created CLOUDSTACK-1894:
---

 Summary: [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a 
user is not able to deploy VMs in a project
 Key: CLOUDSTACK-1894
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1894
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Projects
Affects Versions: 4.2.0
Reporter: Abhinav Roy
 Fix For: 4.2.0


Steps :

1. upgrade from 4.0 to 4.2
2. Create a user account.
3. create a project in that account
4. Browse in to the project view and try to deploy VMs.

Expected behaviour:
===
The VM should be deployed without any issue

Observed behaviour :
==
VM deployment fails with

2013-04-02 17:57:51,209 DEBUG [cloud.user.AccountManagerImpl] 
(catalina-exec-11:null) Access to Acct[5-PrjAcct-user1Project-2] granted to 
Acct[3-user1] by DomainChecker_EnhancerByCloudStack_8eda5c52
2013-04-02 17:57:51,212 INFO  [cloud.api.ApiServer] (catalina-exec-11:null) 
PermissionDenied: Unable to use network with id= 
b29ec01c-360e-4d03-b4e9-09b0633a4d54, permission denied on uuids: []
2013-04-02 17:57:51,213 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) 
===END===  10.101.255.102 -- GET  
command=deployVirtualMachine&zoneId=07ab8ae6-eff5-4fe2-bdae-8929c356ee7f&templateId=d974df3f-3886-4443-a367-1dc77de84960&hypervisor=XenServer&serviceOfferingId=9328a1bd-78fa-4f8f-b3e9-b756af9af730&networkIds=b29ec01c-360e-4d03-b4e9-09b0633a4d54&displayname=projvm1&name=projvm1&response=json&sessionkey=TQLJZNELCpPAalZVMMtb%2F4JlxQY%3D&projectid=227c5af4-5e36-4303-8460-7d691a732ab5&_=1364905654381



NOTE : When teh admin tries to deploy VMs on the same project, it succeeds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1894) [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a user is not able to deploy VMs in a project

[Abhinav Roy (JIRA)]

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

Abhinav Roy updated CLOUDSTACK-1894:


Attachment: After upgrade project VM.jpg

Attaching screenshot

> [Upgrade 4.0 to 4.2] After upgrading from 4.0 to 4.2 a user is not able to 
> deploy VMs in a project
> --
>
> Key: CLOUDSTACK-1894
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1894
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Projects
>Affects Versions: 4.2.0
>Reporter: Abhinav Roy
> Fix For: 4.2.0
>
> Attachments: After upgrade project VM.jpg
>
>
> Steps :
> 
> 1. upgrade from 4.0 to 4.2
> 2. Create a user account.
> 3. create a project in that account
> 4. Browse in to the project view and try to deploy VMs.
> Expected behaviour:
> ===
> The VM should be deployed without any issue
> Observed behaviour :
> ==
> VM deployment fails with
> 2013-04-02 17:57:51,209 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-11:null) Access to Acct[5-PrjAcct-user1Project-2] granted to 
> Acct[3-user1] by DomainChecker_EnhancerByCloudStack_8eda5c52
> 2013-04-02 17:57:51,212 INFO  [cloud.api.ApiServer] (catalina-exec-11:null) 
> PermissionDenied: Unable to use network with id= 
> b29ec01c-360e-4d03-b4e9-09b0633a4d54, permission denied on uuids: []
> 2013-04-02 17:57:51,213 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) 
> ===END===  10.101.255.102 -- GET  
> command=deployVirtualMachine&zoneId=07ab8ae6-eff5-4fe2-bdae-8929c356ee7f&templateId=d974df3f-3886-4443-a367-1dc77de84960&hypervisor=XenServer&serviceOfferingId=9328a1bd-78fa-4f8f-b3e9-b756af9af730&networkIds=b29ec01c-360e-4d03-b4e9-09b0633a4d54&displayname=projvm1&name=projvm1&response=json&sessionkey=TQLJZNELCpPAalZVMMtb%2F4JlxQY%3D&projectid=227c5af4-5e36-4303-8460-7d691a732ab5&_=1364905654381
> NOTE : When teh admin tries to deploy VMs on the same project, it succeeds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1895) [External Devices-SRX, NetScaler] Failed to bring up router vm while configuring the "place holder" nic

[venkata swamybabu budumuru (JIRA)]

venkata swamybabu budumuru created CLOUDSTACK-1895:
--

 Summary: [External Devices-SRX, NetScaler] Failed to bring up 
router vm while configuring the "place holder" nic
 Key: CLOUDSTACK-1895
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1895
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.2.0
 Environment: commit id # 4edef1fd305891beb5393b722e96f4a140934f9f

- advanced zone with 1 Xen Cluster
Reporter: venkata swamybabu budumuru
Assignee: Sheng Yang
Priority: Blocker
 Fix For: 4.2.0


Steps to reproduce :

1. Create a Network offering with the following services

mysql> select * from network_offerings where id=13\G
*** 1. row ***
   id: 13
 name: ExternalDevicesOffering
 uuid: 37b39b54-2129-4983-9fc9-3a3c87a48191
  unique_name: ExternalDevicesOffering
 display_text: ExternalDevicesOffering
  nw_rate: NULL
  mc_rate: 10
 traffic_type: Guest
 tags: NULL
  system_only: 0
 specify_vlan: 0
  service_offering_id: NULL
conserve_mode: 0
  created: 2013-04-02 16:34:08
  removed: NULL
  default: 0
 availability: Optional
 dedicated_lb_service: 0
shared_source_nat_service: 1
 sort_key: 0
 redundant_router_service: 0
state: Enabled
   guest_type: Isolated
   elastic_ip_service: 0
   elastic_lb_service: 0
specify_ip_ranges: 0
   inline: 0
is_persistent: 0

 mysql> select * from ntwk_offering_service_map where network_offering_id=13;
++-++---+-+
| id | network_offering_id | service| provider  | created   
  |
++-++---+-+
| 46 |  13 | Dhcp   | VirtualRouter | 2013-04-02 
16:34:08 |
| 50 |  13 | Dns| VirtualRouter | 2013-04-02 
16:34:08 |
| 49 |  13 | Firewall   | JuniperSRX| 2013-04-02 
16:34:08 |
| 53 |  13 | Lb | Netscaler | 2013-04-02 
16:34:08 |
| 52 |  13 | PortForwarding | JuniperSRX| 2013-04-02 
16:34:08 |
| 51 |  13 | SourceNat  | JuniperSRX| 2013-04-02 
16:34:08 |
| 47 |  13 | StaticNat  | JuniperSRX| 2013-04-02 
16:34:08 |
| 48 |  13 | UserData   | VirtualRouter | 2013-04-02 
16:34:08 |
++-++---+-+
8 rows in set (0.00 sec)

2. create a network using the above network offering.
3. deploy a VM connected to above network.

Observations:

(i) It failed to deploy router VM which eventually resulted in instance 
deployment failure. 

(ii) Here is the snippet from management server log

2013-04-02 12:36:38,344 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-17:job-17) Allocating nics for VM[DomainRouter|r-4-VM]
2013-04-02 12:36:38,346 DEBUG [cloud.network.NetworkManagerImpl] 
(Job-Executor-17:job-17) Allocating nic for vm VM[DomainRouter|r-4-VM] in 
network Ntwk[204|Guest|13] with requested profile NicProfile[0-0-null-null-null
2013-04-02 12:36:38,348 DEBUG [db.Transaction.Transaction] 
(Job-Executor-17:job-17) Rolling back the transaction: Time = 10 Name =  
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
 called by 
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-VirtualMachineManagerImpl.allocate:293-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualMachineManagerImpl.allocate:339-VirtualNetworkApplianceManagerImpl.deployRouter:1609-VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork:1527-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork:1911
2013-04-02 12:36:38,352 DEBUG 
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-17:job-17) 
Lock is released for network id 204 as a part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] 
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(1)-Storage(Volume(3

[jira] [Updated] (CLOUDSTACK-1895) [External Devices-SRX, NetScaler] Failed to bring up router vm while configuring the "place holder" nic

[venkata swamybabu budumuru (JIRA)]

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

venkata swamybabu budumuru updated CLOUDSTACK-1895:
---

Attachment: vmops.log.tgz
api.log.tgz

> [External Devices-SRX, NetScaler] Failed to bring up router vm while 
> configuring the "place holder" nic
> ---
>
> Key: CLOUDSTACK-1895
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1895
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit id # 4edef1fd305891beb5393b722e96f4a140934f9f
> - advanced zone with 1 Xen Cluster
>Reporter: venkata swamybabu budumuru
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: api.log.tgz, vmops.log.tgz
>
>
> Steps to reproduce :
> 1. Create a Network offering with the following services
> mysql> select * from network_offerings where id=13\G
> *** 1. row ***
>id: 13
>  name: ExternalDevicesOffering
>  uuid: 37b39b54-2129-4983-9fc9-3a3c87a48191
>   unique_name: ExternalDevicesOffering
>  display_text: ExternalDevicesOffering
>   nw_rate: NULL
>   mc_rate: 10
>  traffic_type: Guest
>  tags: NULL
>   system_only: 0
>  specify_vlan: 0
>   service_offering_id: NULL
> conserve_mode: 0
>   created: 2013-04-02 16:34:08
>   removed: NULL
>   default: 0
>  availability: Optional
>  dedicated_lb_service: 0
> shared_source_nat_service: 1
>  sort_key: 0
>  redundant_router_service: 0
> state: Enabled
>guest_type: Isolated
>elastic_ip_service: 0
>elastic_lb_service: 0
> specify_ip_ranges: 0
>inline: 0
> is_persistent: 0
>  mysql> select * from ntwk_offering_service_map where network_offering_id=13;
> ++-++---+-+
> | id | network_offering_id | service| provider  | created 
> |
> ++-++---+-+
> | 46 |  13 | Dhcp   | VirtualRouter | 2013-04-02 
> 16:34:08 |
> | 50 |  13 | Dns| VirtualRouter | 2013-04-02 
> 16:34:08 |
> | 49 |  13 | Firewall   | JuniperSRX| 2013-04-02 
> 16:34:08 |
> | 53 |  13 | Lb | Netscaler | 2013-04-02 
> 16:34:08 |
> | 52 |  13 | PortForwarding | JuniperSRX| 2013-04-02 
> 16:34:08 |
> | 51 |  13 | SourceNat  | JuniperSRX| 2013-04-02 
> 16:34:08 |
> | 47 |  13 | StaticNat  | JuniperSRX| 2013-04-02 
> 16:34:08 |
> | 48 |  13 | UserData   | VirtualRouter | 2013-04-02 
> 16:34:08 |
> ++-++---+-+
> 8 rows in set (0.00 sec)
> 2. create a network using the above network offering.
> 3. deploy a VM connected to above network.
> Observations:
> (i) It failed to deploy router VM which eventually resulted in instance 
> deployment failure. 
> (ii) Here is the snippet from management server log
> 2013-04-02 12:36:38,344 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-17:job-17) Allocating nics for VM[DomainRouter|r-4-VM]
> 2013-04-02 12:36:38,346 DEBUG [cloud.network.NetworkManagerImpl] 
> (Job-Executor-17:job-17) Allocating nic for vm VM[DomainRouter|r-4-VM] in 
> network Ntwk[204|Guest|13] with requested profile 
> NicProfile[0-0-null-null-null
> 2013-04-02 12:36:38,348 DEBUG [db.Transaction.Transaction] 
> (Job-Executor-17:job-17) Rolling back the transaction: Time = 10 Name =  
> -AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
>  called by 
> -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-VirtualMachineManagerImpl.allocate:293-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VirtualMachineManagerImpl.allocate:339-VirtualNetworkApplianceManagerImpl.deployRouter:1609-VirtualNetworkApplianceManagerImpl.findOrDeployVir

[jira] [Commented] (CLOUDSTACK-1865) NPE while trying to retrieve storage statistics after upgrade from 4.0 to 4.1

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619844#comment-13619844
 ] 

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

Commit 195a4ee5260a65b9de264dc0477c8da7aafd66a1 in branch refs/heads/4.1 from 
Chip Childers 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=195a4ee ]

CLOUDSTACK-1865: Change StatsCollector to be a manager so that it can 
initialize itself at proper run level


> NPE  while trying to retrieve storage statistics after upgrade from 4.0 to 4.1
> --
>
> Key: CLOUDSTACK-1865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1865
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Sailaja Mada
>Assignee: Kelven Yang
> Attachments: apilog.log, management-server.log
>
>
> Setup:
> MS : Rhel 6.3 with KVM 6.3 host , Advanced Networking
> Steps:
> 1. Stop Management Server and Agent 
> 2. Upgrade the packages from 4.0 to 4,1 
> 3. Start the Management Server.
> Observed NPE while bringing up the Management server after DB upgrade 
> :[attached log]
> 2013-04-01 12:24:06,881 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-2:null) VmStatsCollector is running...
> 2013-04-01 12:24:06,943 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-1:null) There is no secondary storage VM for secondary 
> storage host nfs://10.102.192.100/cpg_vol/sailaja/asf41kvmss
> 2013-04-01 12:24:07,007 ERROR [cloud.server.StatsCollector] 
> (StatsCollector-1:null) Error trying to retrieve storage stats
> java.lang.NullPointerException
> at 
> com.cloud.storage.StorageManagerImpl.getUpHostsInPool(StorageManagerImpl.java:2310)
> at 
> com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:309)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Execution is successful.
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Files /var/cloudstack/management/.ssh/id_rsa and 
> /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud differ
> 2013-04-01 12:24:08,875 INFO  [utils.component.ComponentContext] 
> (Timer-1:null) Configuring 
> com.cloud.utils.crypt.EncryptionSecretKeyChecker_EnhancerByCloudStack_af09bb38

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1865) NPE while trying to retrieve storage statistics after upgrade from 4.0 to 4.1

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619846#comment-13619846
 ] 

Chip Childers commented on CLOUDSTACK-1865:
---

Applied to 4.1:

commit 195a4ee5260a65b9de264dc0477c8da7aafd66a1
Author: Kelven Yang 
Date:   Mon Apr 1 18:25:06 2013 -0700

CLOUDSTACK-1865: Change StatsCollector to be a manager so that it can 
initialize itself at proper run level

> NPE  while trying to retrieve storage statistics after upgrade from 4.0 to 4.1
> --
>
> Key: CLOUDSTACK-1865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1865
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Sailaja Mada
>Assignee: Kelven Yang
> Attachments: apilog.log, management-server.log
>
>
> Setup:
> MS : Rhel 6.3 with KVM 6.3 host , Advanced Networking
> Steps:
> 1. Stop Management Server and Agent 
> 2. Upgrade the packages from 4.0 to 4,1 
> 3. Start the Management Server.
> Observed NPE while bringing up the Management server after DB upgrade 
> :[attached log]
> 2013-04-01 12:24:06,881 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-2:null) VmStatsCollector is running...
> 2013-04-01 12:24:06,943 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-1:null) There is no secondary storage VM for secondary 
> storage host nfs://10.102.192.100/cpg_vol/sailaja/asf41kvmss
> 2013-04-01 12:24:07,007 ERROR [cloud.server.StatsCollector] 
> (StatsCollector-1:null) Error trying to retrieve storage stats
> java.lang.NullPointerException
> at 
> com.cloud.storage.StorageManagerImpl.getUpHostsInPool(StorageManagerImpl.java:2310)
> at 
> com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:309)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Execution is successful.
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Files /var/cloudstack/management/.ssh/id_rsa and 
> /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud differ
> 2013-04-01 12:24:08,875 INFO  [utils.component.ComponentContext] 
> (Timer-1:null) Configuring 
> com.cloud.utils.crypt.EncryptionSecretKeyChecker_EnhancerByCloudStack_af09bb38

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1875) Add JSON output into cloudmonkey

[Chip Childers (JIRA)]

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

Chip Childers reassigned CLOUDSTACK-1875:
-

Assignee: Justin Grudzien  (was: Rohit Yadav)

> Add JSON output into cloudmonkey
> 
>
> Key: CLOUDSTACK-1875
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1875
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Cloudmonkey
>Affects Versions: 4.1.0, Future
>Reporter: Justin Grudzien
>Assignee: Justin Grudzien
>Priority: Minor
>  Labels: newbie, patch
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Data in JSON format is very easy to read for large data sets. Presently, 
> cloudmonkey supports tabular or line based output and looking at large output 
> tends to be problematic. By adding JSON output with filtering, a user can 
> more easily process and consume data. The following items should make 
> cloudmonkey data more easily consumable:
> 1. Need to format empty return messages with proper JSON messaging.
> 2. Need to standardize JSON output messaging.
> A. Add return code [Error|Success] to all calls.
> B. Add called API verb.
> 3. Count is not decreased in output set when filtering completely eliminates 
> a result.
> 4. JSON printing needs to be implemented manually to support colors. Right 
> now json.dumps() pretty prints the output and changing the keys to support 
> colors is problematic.
> 5. Color tagging needs to be added to JSON printing.
> 6. Error messages need to have proper JSON formatting.
> 7. Make color a passable option to a command instead of a config parameter. 
> (i.e. list users account=grudzien color=true)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1877) Failed to connect to DB while starting Ubuntu management server after upgrading the packages from 4.0 to 4.1

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619884#comment-13619884
 ] 

Chip Childers commented on CLOUDSTACK-1877:
---

Are you able to manually access the DB using the cloud user?

> Failed to connect to DB while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> 
>
> Key: CLOUDSTACK-1877
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1877
> 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.1.0
>Reporter: Sailaja Mada
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: 40cloudstack_backup.dmp, 40db.properties, 
> 41db.properties, management-server.log
>
>
> Setup:
> MS : Ubuntu 12.04 with Xen 6.0.2 host , Advanced Networking
> Steps:
> 1. Stop Management Server 
> 2. Upgrade the packages of MS from 4.0 to 4.1
> 3. Start the Management Server.
> DB upgrade failed to start while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> Note: Attached DB properties DB Dump. MS log
> 2013-04-01 17:24:33,869 ERROR [web.context.ContextLoader] (main:null) Context 
> initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'apiServer': Invocation of init method failed; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:135)
>  at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1448)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
> at 
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002)
> at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
> at 
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:10

[jira] [Commented] (CLOUDSTACK-1877) Failed to connect to DB while starting Ubuntu management server after upgrading the packages from 4.0 to 4.1

[Sailaja Mada (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619892#comment-13619892
 ] 

Sailaja Mada commented on CLOUDSTACK-1877:
--

Yes i can connect DB manually .

root@ub12sailaja:~# mysql -u cloud -ppassword
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 759
Server version: 5.5.29-0ubuntu0.12.04.2 (Ubuntu)

Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>


> Failed to connect to DB while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> 
>
> Key: CLOUDSTACK-1877
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1877
> 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.1.0
>Reporter: Sailaja Mada
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: 40cloudstack_backup.dmp, 40db.properties, 
> 41db.properties, management-server.log
>
>
> Setup:
> MS : Ubuntu 12.04 with Xen 6.0.2 host , Advanced Networking
> Steps:
> 1. Stop Management Server 
> 2. Upgrade the packages of MS from 4.0 to 4.1
> 3. Start the Management Server.
> DB upgrade failed to start while starting Ubuntu management server after 
> upgrading the packages from 4.0 to 4.1
> Note: Attached DB properties DB Dump. MS log
> 2013-04-01 17:24:33,869 ERROR [web.context.ContextLoader] (main:null) Context 
> initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'apiServer': Invocation of init method failed; nested exception is 
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null
> at 
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:135)
>  at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1448)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
> at 
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)
> at 
> org.apache.catalina.startup.HostConfig.deployDirectories(HostCon

[jira] [Assigned] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[Chip Childers (JIRA)]

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

Chip Childers reassigned CLOUDSTACK-1839:
-

Assignee: (was: Rohit Yadav)

Unassigned Rohit.  Anyone else want to take this up?

> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> -
>
> Key: CLOUDSTACK-1839
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1839
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Upgrade 4.0 -> 4.1 
>Reporter: Sangeetha Hariharan
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: upgrade-db-dumps.rar
>
>
> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> Scenario 1:
> Fresh install of 4.0.
> Upgrade the set up to 4.1.
> Scenario 2:
> Fresh install of 4.1 and started the management server.
> Comparing the schema between Scenario1 and Scenario2 shows that the Upgraded 
> DB has lot more keys and indexes for many tables compare to the fresh 
> installed 4.1 DB.
> Will attach database dump for both the cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1837) Document additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included in the upgrade procedure from 4.0 -> 4.1

[Sangeetha Hariharan (JIRA)]

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

Sangeetha Hariharan updated CLOUDSTACK-1837:


Priority: Critical  (was: Major)
 Summary: Document additonal Steps ( Restart of all system Vms , copy 
vhd-utils) to be included in the upgrade procedure from 4.0 -> 4.1  (was: 
Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included in 
the upgrade procedure from 4.0 -> 4.1)

> Document additonal Steps ( Restart of all system Vms , copy vhd-utils) to be 
> included in the upgrade procedure from 4.0 -> 4.1
> --
>
> Key: CLOUDSTACK-1837
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1837
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.1.0
> Environment: Upgrade from 4.0 -> 4.1
>Reporter: Sangeetha Hariharan
>Priority: Critical
> Fix For: 4.1.0
>
>
> Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included 
> in the upgrade procedure from 4.0 -> 4.1
> Include the following steps as part of upgrade from 4.0 -> 4.1
>  
> Step to restart all system Vms (SSVM,CPVM and Routers):
> 1. Run the following script to stop, then start, all Secondary Storage VMs, 
> Console Proxy VMs, and virtual routers.Make sure port 8096 is open.
> Run the command once on one management server. Substitute your own IP 
> address of the MySQL instance, the MySQL user to connect as, and the password 
> to use for that user. In addition to those parameters, provide the "-a" 
> arguments. For example:
> # nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -a > 
> sysvm.log 2>&1 &
> # tail -f sysvm.log
> This might take up to an hour or more to run, depending on the number of 
> accounts in the system.
> After the script terminates, check the log to verify correct execution:
> # tail -f sysvm.log
> The content should be like the following:
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> Done stopping and starting console proxy vm(s).
> Stopping and starting 4 running routing vm(s)...
> Done restarting router(s).
> Step 2:
> copy vhd-utils to /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1845) KVM - storage migration often fails

[Marcus Sorensen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619917#comment-13619917
 ] 

Marcus Sorensen commented on CLOUDSTACK-1845:
-

It's tested against 4.1, and I have the 4.0 patch in a review request for jzb.

> KVM - storage migration often fails
> ---
>
> Key: CLOUDSTACK-1845
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1845
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Marcus Sorensen
>Assignee: Marcus Sorensen
>Priority: Critical
> Fix For: 4.0.2, 4.1.0, 4.2.0
>
>
> This is more of a placeholder, I have the fix.
> When storage migration calls CopyVolumeCommand, it assumes that the primary 
> storage has been used/registered before on the KVM host. It does something 
> like a getStoragePool(poolUuid), and if primary storage pool (source or 
> destination) has never been used on the host it will fail. The fix is simply 
> to add the pool if it's not already there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1846) KVM - storage pools can silently fail to be unregistered, leading to failure to register later

[Marcus Sorensen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619916#comment-13619916
 ] 

Marcus Sorensen commented on CLOUDSTACK-1846:
-

It's tested against 4.1, and I have the 4.0 patch in a review request for jzb.

> KVM - storage pools can silently fail to be unregistered, leading to failure 
> to register later
> --
>
> Key: CLOUDSTACK-1846
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1846
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Marcus Sorensen
>Assignee: Marcus Sorensen
>Priority: Critical
> Fix For: 4.0.2, 4.1.0, 4.2.0
>
>
> This is a placeholder, I have a fix.
> A specific deleteStoragePool method attempts to delete a libvirt storage 
> pool, but failures are silently ignored (for example failure to unmount NFS 
> pool because it's in use). Later, when pools are registered, they can fail to 
> register because the mountpoint is in use. Part of my fix is to expose/log 
> failures, and the other part is an attempt to handle the failures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1891) [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not happening properly after releasing the IP on which LB was configured

[Rajesh Battala (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619918#comment-13619918
 ] 

Rajesh Battala commented on CLOUDSTACK-1891:


If you are deleting from the UI, can you verify from the firebug can you post 
which API's are getting called.?
from the last log statement in the above, NS should have delete the LB and its 
associated configurations.

> [AWS style Health Checks]After upgrade from 4.0 to 4.2 , cleanup not 
> happening properly after releasing the IP on which LB was configured
> -
>
> Key: CLOUDSTACK-1891
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1891
> 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: Abhinav Roy
>Assignee: Rajesh Battala
> Fix For: 4.2.0
>
>
> Steps :
> ==
> 1. Upgrade MS from 4.0 to 4.2
> 2. Go to the existing Netscaler network, acquire IP and create a LB rule.
> 3. configure health checks on the LB rule.
> 4. Release the IP acquired in step 2
> Expected behaviour :
> =
> IP should be relased, LB rule and the LB monitor created on NS device also 
> should be deleted.
> Observed behaviour :
> 
> IP is released
> LB rule doesn't get deleted on CS but the corresponding lb vserver is deleted 
> from NS
> LB health check policy gets deleted on CS but the corresponding monitor 
> doesn't get deleted from NS
> 2013-04-02 17:23:13,735 ERROR [network.resource.NetscalerResource] 
> (DirectAgent-29:null) Failed to execute LoadBalancerConfigCommand due to 
> com.cloud.utils.exception.ExecutionException: Failed to delete monitor 
> :Cloud-Hc-10.102.195.19-22 due to Monitor must be unbound before it can be 
> deleted
> at 
> com.cloud.network.resource.NetscalerResource.removeLBMonitor(NetscalerResource.java:2289)
> at 
> com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:678)
> at 
> com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:351)
> at 
> com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:340)
> 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-04-02 17:23:13,793 WARN  [network.resource.NetscalerResource] 
> (DirectAgent-29:null) Retrying LoadBalancerConfigCommand. Number of retries 
> remaining: 1
> 2013-04-02 17:23:13,823 INFO  [network.resource.NetscalerResource] 
> (DirectAgent-29:null) Successfully executed resource 
> LoadBalancerConfigCommand: 
> {"loadBalancers":[{"uuid":"eaa5d85c-6d81-43dc-b2a2-9431f2cb9c12","srcIp":"10.102.195.19","srcPort":22,"protocol":"tcp","algorithm":"roundrobin","revoked":true,"alreadyAdded":false,"inline":false,"destinations":[{"destIp":"10.2.113.88","destPort":22,"revoked":true,"alreadyAdded":false},{"destIp":"10.2.112.78","destPort":22,"revoked":true,"alreadyAdded":false}],"healthCheckPolicies":[{"pingPath":"/","responseTime":2,"healthcheckInterval":5,"healthcheckThresshold":2,"unhealthThresshold":1,"revoke":true}]}],"lbStatsVisibility":"guest-network","lbStatsPort":"8081","lbStatsSrcCidrs":"0/0","lbStatsAuth":"admin1:AdMiN123","lbStatsUri":"/admin?stats","accessDetails":{"guest.vlan.tag":"819"},"wait":0}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1224) Volume snapshot creation failing

[Francois Gaudreault (JIRA)]

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

Francois Gaudreault updated CLOUDSTACK-1224:


Attachment: snapshot.log

management-server.log file for a snapshot attempt.

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: edison su
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> 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:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.Abstra

[jira] [Commented] (CLOUDSTACK-1224) Volume snapshot creation failing

[Francois Gaudreault (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619950#comment-13619950
 ] 

Francois Gaudreault commented on CLOUDSTACK-1224:
-

I just added the management-server log file for a snapshot.  We do see some 
FileNotFound exception coming in.  Is your test VMWare environment is running 
on 5.1? Ours is 5.1.

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: edison su
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> 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:616)
> at 
> org.springframework

[jira] [Assigned] (CLOUDSTACK-1889) [UI] Consumed Resource usage details are not available for all the resources

[Sonny Chhen (JIRA)]

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

Sonny Chhen reassigned CLOUDSTACK-1889:
---

Assignee: Pranav Saxena  (was: Sonny Chhen)

> [UI] Consumed Resource usage details are not available for all the resources
> 
>
> Key: CLOUDSTACK-1889
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1889
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Pranav Saxena
> Attachments: resources.png
>
>
> Setup: Advanced Networking zone with Xen 6.1 [4.2]
> Steps:
> 1. Create Child domain (CDC1) under ROOT
> 2. Create Domain account CDC1Admin1 under Child Domain CDC1 
> 3. Access Management Server as this domain admin account
> 4. Deploy VM with this account 
> 5. Tried to update resource Count
> Observation: Consumed Resource usage details are not available for all the 
> resources.  It is available only with Total of VM  , Total of IP Address   , 
> Bytes Received ,Bytes Sent.
> API provides the details. 
> http://10.102.192.208:8096/client/api?command=updateResourceCount&domainid=2&resourcetype=9&account=cdc1admin1
>  cloud-stack-version="4.2.0-SNAPSHOT">1cdc1admin1e8377899-c351-47a2-aed5-92c624eebae5cdc19512

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1888) [UI]Child Domain Admin accounts can not set/update the resource limits

[Sonny Chhen (JIRA)]

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

Sonny Chhen reassigned CLOUDSTACK-1888:
---

Assignee: Pranav Saxena  (was: Sonny Chhen)

> [UI]Child Domain Admin accounts can not set/update the  resource limits
> ---
>
> Key: CLOUDSTACK-1888
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1888
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: Pranav Saxena
> Fix For: 4.2.0
>
> Attachments: DomainAdminView.png
>
>
> Setup: Advanced Networking zone with Xen 6.1 [4.2]
> Steps:
> 1. Create Child domain (CDC1) under ROOT 
> 2. Create Domain account CDC1Admin1 under Child Domain CDC1
> 3. Access Management Server as this domain admin account
> Observation: Child Domain Admin accounts can not set/update the  resource 
> limits. It is supported via API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[Alex Huang (JIRA)]

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

Alex Huang reassigned CLOUDSTACK-1839:
--

Assignee: Alex Huang

> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> -
>
> Key: CLOUDSTACK-1839
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1839
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Upgrade 4.0 -> 4.1 
>Reporter: Sangeetha Hariharan
>Assignee: Alex Huang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: upgrade-db-dumps.rar
>
>
> Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many 
> tables compare to the fresh installed 4.1 DB.
> Scenario 1:
> Fresh install of 4.0.
> Upgrade the set up to 4.1.
> Scenario 2:
> Fresh install of 4.1 and started the management server.
> Comparing the schema between Scenario1 and Scenario2 shows that the Upgraded 
> DB has lot more keys and indexes for many tables compare to the fresh 
> installed 4.1 DB.
> Will attach database dump for both the cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1830) ZWPS: NPE while create volume from snapshot

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620038#comment-13620038
 ] 

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

Commit 6110e00c549630e8b08fc6ca4818a60ef6a0c919 in branch refs/heads/master 
from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6110e00 ]

CLOUDSTACK-1830: ZWPS: NPE while create volume from snapshot


> ZWPS: NPE while create volume from snapshot 
> 
>
> Key: CLOUDSTACK-1830
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1830
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Harikrishna Patnala
>Priority: Blocker
> Fix For: 4.2.0
>
>
> NPE while creating volume from snapshot:
>  ===START===  10.252.250.64 -- GET  
> command=createVolume&response=json&sessionkey=fBgbfTKbB6aYlrhmnXUliOGoMHk%3D&snapshotid=2d9b142e-6917-4b68-86ce-ab1069f9fbd5&name=v&_=1364475296117
> 2013-03-28 23:51:00,799 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-19:null) submit async job-22, details: AsyncJobVO {id:22, 
> userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 
> 10, cmd: org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"10","response":"json","sessionkey":"fBgbfTKbB6aYlrhmnXUliOGoMHk\u003d","ctxUserId":"2","snapshotid":"2d9b142e-6917-4b68-86ce-ab1069f9fbd5","name":"v","_":"1364475296117","ctxAccountId":"2","ctxStartEventId":"78"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-28 23:51:00,802 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
> ===END===  10.252.250.64 -- GET  
> command=createVolume&response=json&sessionkey=fBgbfTKbB6aYlrhmnXUliOGoMHk%3D&snapshotid=2d9b142e-6917-4b68-86ce-ab1069f9fbd5&name=v&_=1364475296117
> 2013-03-28 23:51:00,805 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-22:job-22) Executing 
> org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-22
> 2013-03-28 23:51:00,840 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-22:job-22) Failed to create volume: 10
> java.lang.NullPointerException
> at 
> com.cloud.vm.VirtualMachineProfileImpl.getHypervisorType(VirtualMachineProfileImpl.java:117)
> at 
> org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.select(ZoneWideStoragePoolAllocator.java:59)
> at 
> org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:99)
> at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
> at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.inv

[jira] [Assigned] (CLOUDSTACK-1224) Volume snapshot creation failing

[edison su (JIRA)]

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

edison su reassigned CLOUDSTACK-1224:
-

Assignee: Kelven Yang  (was: edison su)

VMware resource reports error:
[{"BackupSnapshotAnswer":{"full":true,"result":false,"details":"BackupSnapshotCommand
 exception: java.io.FileNotFoundException: 
https://10.0.22.12/folder/i-2-125-VM/i-2-125-VM.vmsd?dcPath=CloudStack&dsName=NOC_CLOUDSTACKPOC01\nsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)\nsun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)\ncom.cloud.hypervisor.vmware.util.VmwareContext.getResourceContent(VmwareContext.java:419)\ncom.cloud.hypervisor.vmware.mo.VirtualMachineMO.getSnapshotDescriptor(VirtualMachineMO.java:463)\ncom.cloud.hypervisor.vmware.mo.VirtualMachineMO.getCurrentSnapshotDiskChainDatastorePaths(VirtualMachineMO.java:1471)\ncom.cloud.hypervisor.vmware.mo.VirtualMachineMO.cloneFromCurrentSnapshot(VirtualMachineMO.java:1494)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.exportVolumeToSecondaryStroage(VmwareStorageManagerImpl.java:749)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.backupSnapshotToSecondaryStorage(VmwareStorageManagerImpl.java:716)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:216)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.execute(VmwareSecondaryStorageResourceHandler.java:113)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:71)\ncom.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:54)\ncom.cloud.agent.Agent.processRequest(Agent.java:525)\ncom.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\ncom.cloud.utils.nio.Task.run(Task.java:83)\njava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)\njava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)\njava.lang.Thread.run(Thread.java:662)\n","wait":0}}]
 }

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMe

[jira] [Resolved] (CLOUDSTACK-1830) ZWPS: NPE while create volume from snapshot

[edison su (JIRA)]

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

edison su resolved CLOUDSTACK-1830.
---

Resolution: Fixed

> ZWPS: NPE while create volume from snapshot 
> 
>
> Key: CLOUDSTACK-1830
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1830
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Harikrishna Patnala
>Priority: Blocker
> Fix For: 4.2.0
>
>
> NPE while creating volume from snapshot:
>  ===START===  10.252.250.64 -- GET  
> command=createVolume&response=json&sessionkey=fBgbfTKbB6aYlrhmnXUliOGoMHk%3D&snapshotid=2d9b142e-6917-4b68-86ce-ab1069f9fbd5&name=v&_=1364475296117
> 2013-03-28 23:51:00,799 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-19:null) submit async job-22, details: AsyncJobVO {id:22, 
> userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 
> 10, cmd: org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd, 
> cmdOriginator: null, cmdInfo: 
> {"id":"10","response":"json","sessionkey":"fBgbfTKbB6aYlrhmnXUliOGoMHk\u003d","ctxUserId":"2","snapshotid":"2d9b142e-6917-4b68-86ce-ab1069f9fbd5","name":"v","_":"1364475296117","ctxAccountId":"2","ctxStartEventId":"78"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 7566222426160, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-28 23:51:00,802 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
> ===END===  10.252.250.64 -- GET  
> command=createVolume&response=json&sessionkey=fBgbfTKbB6aYlrhmnXUliOGoMHk%3D&snapshotid=2d9b142e-6917-4b68-86ce-ab1069f9fbd5&name=v&_=1364475296117
> 2013-03-28 23:51:00,805 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-22:job-22) Executing 
> org.apache.cloudstack.api.command.user.volume.CreateVolumeCmd for job-22
> 2013-03-28 23:51:00,840 DEBUG [cloud.storage.VolumeManagerImpl] 
> (Job-Executor-22:job-22) Failed to create volume: 10
> java.lang.NullPointerException
> at 
> com.cloud.vm.VirtualMachineProfileImpl.getHypervisorType(VirtualMachineProfileImpl.java:117)
> at 
> org.apache.cloudstack.storage.allocator.ZoneWideStoragePoolAllocator.select(ZoneWideStoragePoolAllocator.java:59)
> at 
> org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:99)
> at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
> at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
> at $Proxy282.allocateToPool(Unknown Source)
> at 
> com.cloud.storage.StorageManagerImpl.findStoragePool(StorageManagerImpl.java:453)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMeth

[jira] [Created] (CLOUDSTACK-1896) S3 and Swift-backed NFS secondary storage uses Db-based lock when DB is not available

[Chiradeep Vittal (JIRA)]

Chiradeep Vittal created CLOUDSTACK-1896:


 Summary: S3 and Swift-backed NFS secondary storage uses Db-based 
lock when DB is not available
 Key: CLOUDSTACK-1896
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1896
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Storage Controller
Affects Versions: 4.1.0, 4.2.0
Reporter: Chiradeep Vittal
Assignee: John Burwell


While perusing NfsSecondaryStorageResource.java, I came across:
 public Answer execute(final DownloadSnapshotFromS3Command cmd) {
   ...
try {

executeWithNoWaitLock(determineSnapshotLockId(accountId, volumeId),
new Callable() {

@Override
public Void call() throws Exception {

}
   }

The executeWithNoWaitLock utility uses the management server database, which is 
not available inside the secondary storage vm. So, my conclusion is that there 
is no way this code works.

Unfortunately the same code has been added to the Swift-backed code as well and 
will therefore break that as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1224) Volume snapshot creation failing

[Francois Gaudreault (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620103#comment-13620103
 ] 

Francois Gaudreault commented on CLOUDSTACK-1224:
-

Ok found something.  Looks like a config issue. 

Since the customer is using folders, the datastore was located under 
OPS/CloudStack, and not just CloudStack like the hosts. So CS is using the same 
path as the host for the datastore.

Let me try to get it to work.  I'll update the ticket once I have more info.



> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.

[jira] [Updated] (CLOUDSTACK-1896) S3-backed NFS secondary storage uses Db-based lock when DB is not available

[Chiradeep Vittal (JIRA)]

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

Chiradeep Vittal updated CLOUDSTACK-1896:
-

Description: 
While perusing NfsSecondaryStorageResource.java, I came across:
 public Answer execute(final DownloadSnapshotFromS3Command cmd) {
   ...
try {

executeWithNoWaitLock(determineSnapshotLockId(accountId, volumeId),
new Callable() {

@Override
public Void call() throws Exception {

}
   }

The executeWithNoWaitLock utility uses the management server database, which is 
not available inside the secondary storage vm. So, my conclusion is that there 
is no way this code works.

This also affects the method deleteSnapshotBackupfromS3

  was:
While perusing NfsSecondaryStorageResource.java, I came across:
 public Answer execute(final DownloadSnapshotFromS3Command cmd) {
   ...
try {

executeWithNoWaitLock(determineSnapshotLockId(accountId, volumeId),
new Callable() {

@Override
public Void call() throws Exception {

}
   }

The executeWithNoWaitLock utility uses the management server database, which is 
not available inside the secondary storage vm. So, my conclusion is that there 
is no way this code works.

Unfortunately the same code has been added to the Swift-backed code as well and 
will therefore break that as well.

Summary: S3-backed NFS secondary storage uses Db-based lock when DB is 
not available  (was: S3 and Swift-backed NFS secondary storage uses Db-based 
lock when DB is not available)

> S3-backed NFS secondary storage uses Db-based lock when DB is not available
> ---
>
> Key: CLOUDSTACK-1896
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1896
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Chiradeep Vittal
>Assignee: John Burwell
>
> While perusing NfsSecondaryStorageResource.java, I came across:
>  public Answer execute(final DownloadSnapshotFromS3Command cmd) {
>...
> try {
> executeWithNoWaitLock(determineSnapshotLockId(accountId, 
> volumeId),
> new Callable() {
> @Override
> public Void call() throws Exception {
> 
> }
>}
> The executeWithNoWaitLock utility uses the management server database, which 
> is not available inside the secondary storage vm. So, my conclusion is that 
> there is no way this code works.
> This also affects the method deleteSnapshotBackupfromS3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1865) NPE while trying to retrieve storage statistics after upgrade from 4.0 to 4.1

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620105#comment-13620105
 ] 

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

Commit f2ad38aa0f5623551fdd0a295219fb948030bd28 in branch refs/heads/master 
from Kelven Yang 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f2ad38a ]

CLOUDSTACK-1865: Change StatsCollector to be a manager so that it can 
initialize itself at proper run level


> NPE  while trying to retrieve storage statistics after upgrade from 4.0 to 4.1
> --
>
> Key: CLOUDSTACK-1865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1865
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Sailaja Mada
>Assignee: Kelven Yang
> Attachments: apilog.log, management-server.log
>
>
> Setup:
> MS : Rhel 6.3 with KVM 6.3 host , Advanced Networking
> Steps:
> 1. Stop Management Server and Agent 
> 2. Upgrade the packages from 4.0 to 4,1 
> 3. Start the Management Server.
> Observed NPE while bringing up the Management server after DB upgrade 
> :[attached log]
> 2013-04-01 12:24:06,881 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-2:null) VmStatsCollector is running...
> 2013-04-01 12:24:06,943 DEBUG [cloud.server.StatsCollector] 
> (StatsCollector-1:null) There is no secondary storage VM for secondary 
> storage host nfs://10.102.192.100/cpg_vol/sailaja/asf41kvmss
> 2013-04-01 12:24:07,007 ERROR [cloud.server.StatsCollector] 
> (StatsCollector-1:null) Error trying to retrieve storage stats
> java.lang.NullPointerException
> at 
> com.cloud.storage.StorageManagerImpl.getUpHostsInPool(StorageManagerImpl.java:2310)
> at 
> com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:309)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Execution is successful.
> 2013-04-01 12:24:08,864 DEBUG [cloud.server.ConfigurationServerImpl] 
> (Timer-1:null) Files /var/cloudstack/management/.ssh/id_rsa and 
> /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud differ
> 2013-04-01 12:24:08,875 INFO  [utils.component.ComponentContext] 
> (Timer-1:null) Configuring 
> com.cloud.utils.crypt.EncryptionSecretKeyChecker_EnhancerByCloudStack_af09bb38

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[Chandan Purushothama (JIRA)]

Chandan Purushothama created CLOUDSTACK-1897:


 Summary: ASF Master Build breaks due to unapproved licenses
 Key: CLOUDSTACK-1897
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Install and Setup
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Priority: Blocker
 Fix For: 4.2.0


I tried to make a build of 4.2.0. It reported Build failure. I see the 
following Information as the reason for the failure.


*
Summary
---
Generated at: 2013-04-02T04:30:54-07:00
Notes: 14
Binaries: 223
Archives: 0
Standards: 6288

Apache Licensed: 6278
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

10 Unknown Licenses

***

Unapproved licenses:

  tools/appliance/definitions/devcloud/zerodisk.sh
  tools/appliance/definitions/devcloud/definition.rb
  tools/appliance/definitions/devcloud/preseed.cfg
  tools/appliance/definitions/devcloud/cleanup.sh
  tools/appliance/definitions/devcloud/base.sh
  tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
  tools/appliance/definitions/systemvmtemplate64/definition.rb
  tools/appliance/definitions/systemvmtemplate64/preseed.cfg
  tools/appliance/definitions/systemvmtemplate64/cleanup.sh
  tools/appliance/definitions/systemvmtemplate64/base.sh

***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[Chandan Purushothama (JIRA)]

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

Chandan Purushothama updated CLOUDSTACK-1897:
-

Priority: Major  (was: Blocker)

> ASF Master Build breaks due to unapproved licenses
> --
>
> Key: CLOUDSTACK-1897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
> Fix For: 4.2.0
>
>
> I tried to make a build of 4.2.0. It reported Build failure. I see the 
> following Information as the reason for the failure.
> *
> Summary
> ---
> Generated at: 2013-04-02T04:30:54-07:00
> Notes: 14
> Binaries: 223
> Archives: 0
> Standards: 6288
> Apache Licensed: 6278
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   tools/appliance/definitions/devcloud/zerodisk.sh
>   tools/appliance/definitions/devcloud/definition.rb
>   tools/appliance/definitions/devcloud/preseed.cfg
>   tools/appliance/definitions/devcloud/cleanup.sh
>   tools/appliance/definitions/devcloud/base.sh
>   tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
>   tools/appliance/definitions/systemvmtemplate64/definition.rb
>   tools/appliance/definitions/systemvmtemplate64/preseed.cfg
>   tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>   tools/appliance/definitions/systemvmtemplate64/base.sh
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1884) CreateNetworkOffering tests broken due to database reference

[Kelven Yang (JIRA)]

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

Kelven Yang resolved CLOUDSTACK-1884.
-

Resolution: Fixed

The fix was already in commit 5782abf8f80fce929e3d6e20068bc165f2360426

> CreateNetworkOffering tests broken due to database reference
> 
>
> Key: CLOUDSTACK-1884
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1884
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Affects Versions: 4.2.0
>Reporter: Hugo Trippaers
>Assignee: Kelven Yang
>Priority: Blocker
>
> how to replay:
> git checkout 5782abf8f80fce929e3d6e20068bc165f2360426
> mvn clean test -pl :cloud-server -am
> commit:
> commit 5782abf8f80fce929e3d6e20068bc165f2360426
> Author: Kelven Yang 
> Date:   Fri Mar 29 11:01:40 2013 -0700
> Update unit test configuraitons to new custom Spring AOP
> Results :
> Tests in error: 
>   
> createSharedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithoutSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndNoSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
> Tests run: 43, Failures: 0, Errors: 8, Skipped: 2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Min Chen (JIRA)]

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

Min Chen updated CLOUDSTACK-1890:
-

Affects Version/s: 4.1.0

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1884) CreateNetworkOffering tests broken due to database reference

[Kelven Yang (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620120#comment-13620120
 ] 

Kelven Yang commented on CLOUDSTACK-1884:
-

Could you try out running mvn clean separately, when multiple goals are 
specified, it seems that maven may sometimes fail to cleanup

> CreateNetworkOffering tests broken due to database reference
> 
>
> Key: CLOUDSTACK-1884
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1884
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Affects Versions: 4.2.0
>Reporter: Hugo Trippaers
>Assignee: Kelven Yang
>Priority: Blocker
>
> how to replay:
> git checkout 5782abf8f80fce929e3d6e20068bc165f2360426
> mvn clean test -pl :cloud-server -am
> commit:
> commit 5782abf8f80fce929e3d6e20068bc165f2360426
> Author: Kelven Yang 
> Date:   Fri Mar 29 11:01:40 2013 -0700
> Update unit test configuraitons to new custom Spring AOP
> Results :
> Tests in error: 
>   
> createSharedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createSharedNtwkOffWithoutSpecifyIpRanges(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithNoVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithVlan(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
>   
> createIsolatedNtwkOffWithSpecifyIpRangesAndNoSourceNat(org.apache.cloudstack.networkoffering.CreateNetworkOfferingTest):
>  DB Exception on: null
> Tests run: 43, Failures: 0, Errors: 8, Skipped: 2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1224) Volume snapshot creation failing

[Francois Gaudreault (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620121#comment-13620121
 ] 

Francois Gaudreault commented on CLOUDSTACK-1224:
-

I confirm snapshots are now working fine.

So Issue was VMWare configuration related:
- Hosts were in /CloudStack while Datastore was in /OPS/CloudStack.

The weird thing is that the primary storage have been created without the "OPS" 
folder, and the VM deployment was working fine. Anyway, you can close this!!

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invo

[jira] [Commented] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Min Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620122#comment-13620122
 ] 

Min Chen commented on CLOUDSTACK-1890:
--

Fixed by patch https://reviews.apache.org/r/10240/, pending Chip's review. The 
affected version should also include 4.1.0, updated the bug to reflect that.

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-715) Make VmWare plugin a non-oss component

[Min Chen (JIRA)]

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

Min Chen reassigned CLOUDSTACK-715:
---

Assignee: (was: Min Chen)

> Make VmWare plugin a non-oss component
> --
>
> Key: CLOUDSTACK-715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-715
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller
>Affects Versions: 4.0.0
>Reporter: Alex Huang
>
> The VmWare component is using a client stub library from vmware and the 
> client stub library is not licensed appropriately.  That's my understanding 
> of why vmware component is not in the apache release.  We should just go 
> against the wsdl that vmware releases.  This is a bug to track against that 
> effort.  If my understanding is not right, please update this bug.
> I assigned it to Kelven for this comments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-715) Make VmWare plugin a non-oss component

[Min Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620125#comment-13620125
 ] 

Min Chen commented on CLOUDSTACK-715:
-

Based on ML discussion, other contributors in the community are willing to take 
this task to convert to use VI JAVA, so make this bug unassigned so that others 
can pick it up.

> Make VmWare plugin a non-oss component
> --
>
> Key: CLOUDSTACK-715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-715
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller
>Affects Versions: 4.0.0
>Reporter: Alex Huang
>
> The VmWare component is using a client stub library from vmware and the 
> client stub library is not licensed appropriately.  That's my understanding 
> of why vmware component is not in the apache release.  We should just go 
> against the wsdl that vmware releases.  This is a bug to track against that 
> effort.  If my understanding is not right, please update this bug.
> I assigned it to Kelven for this comments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-1224) Volume snapshot creation failing

[edison su (JIRA)]

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

edison su closed CLOUDSTACK-1224.
-

Resolution: Won't Fix

> Volume snapshot creation failing
> 
>
> Key: CLOUDSTACK-1224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: vmware cluster, CS 4.1
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: snapshot.log
>
>
> When creating a volume snapshot of the root disk of a VM, the snapshot fails 
> to get created. The exception stack trace is pasted below:
> INFO  [vmware.resource.VmwareResource] (DirectAgent-11:10.223.74.132) 
> Executing resource NetworkUsageCommand
> INFO  [vmware.resource.VmwareResource] (DirectAgent-5:10.223.74.132) 
> Executing resource NetworkUsageCommand
> WARN  [storage.snapshot.SnapshotManagerImpl] (Job-Executor-2:job-17) Storage 
> unavailable
> com.cloud.exception.StorageUnavailableException: Resource [StoragePool:200] 
> is unreachable: Unable to send command to the pool 200 due to there is no 
> enabled hosts up in this cluster
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2322)
> at 
> com.cloud.storage.StorageManagerImpl.sendToPool(StorageManagerImpl.java:2347)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43)
> at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.sendToPool(SnapshotManagerImpl.java:197)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.backupSnapshotToSecondaryStorage(SnapshotManagerImpl.java:668)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:417)
> at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.createSnapshot(SnapshotManagerImpl.java:108)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41)
> 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:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.

[jira] [Commented] (CLOUDSTACK-1890) listProjects is not listing state in the response

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620153#comment-13620153
 ] 

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

Commit 1902fc5e2f954b52bb7bd1604cbeb0120752f256 in branch refs/heads/4.1 from 
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1902fc5 ]

CLOUDSTACK-1890: listProjects is not listing state in the response.


> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1890) listProjects is not listing state in the response

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620156#comment-13620156
 ] 

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

Commit f52820f2fdbede9ad8f4675223a2306b9d89ac51 in branch refs/heads/master 
from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f52820f ]

CLOUDSTACK-1890: listProjects is not listing state in the response.


> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1890) listProjects is not listing state in the response

[Chip Childers (JIRA)]

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

Chip Childers resolved CLOUDSTACK-1890.
---

Resolution: Fixed

applied to 4.1 and cherry-picked to master.

> listProjects is not listing state in the response
> -
>
> Key: CLOUDSTACK-1890
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1890
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Sailaja Mada
>Assignee: Min Chen
> Fix For: 4.1.0, 4.2.0
>
> Attachments: projview.png
>
>
> Setup:  Advanced Networking Zone with Xen 6.1 [4.2]
> Steps:
> 1. Create projects as admin & Child domain account 
> 2. Tried to list all the projects.
> Observation:
> 1) listProjects is not listing state in the response
> 2) State of the project from UI displayed as blank [Attached the sanp]
> 2013-04-02 16:52:59,411 INFO  [cloud.api.ApiServer] (catalina-exec-12:null) 
> (userId=2 accountId=2 sessionId=45961497FF93B9D86F004FAA07E5C581) 10.144.6.39 
> -- GET 
> command=listProjects&response=json&sessionkey=NsDF%2BPjcst3nXPqQdjyvGduXlOs%3D&listAll=true&page=1&pagesize=20&_=1364901881168
>  200 { "listprojectsresponse" : { "count":2 ,"project" : [  
> {"id":"ba89a1e1-39e3-4507-a4d5-7f4cbb53c932","name":"proj1","displaytext":"","domainid":"e8377899-c351-47a2-aed5-92c624eebae5","domain":"cdc1","account":"cdc1admin1","tags":[]},
>  
> {"id":"532eaa39-2daf-41ee-ad37-b168f0a34916","name":"proj1","displaytext":"proj1","domainid":"c579ec3a-9a89-11e2-8880-ca27ffbee488","domain":"ROOT","account":"admin","tags":[]}
>  ] } }
> http://10.102.192.208:8096/client/api?command=listProjects&listAll=true
> 
> 2
> ba89a1e1-39e3-4507-a4d5-7f4cbb53c932
> proj1
> e8377899-c351-47a2-aed5-92c624eebae5
> cdc1cdc1admin1
> 532eaa39-2daf-41ee-ad37-b168f0a34916
> proj1
> proj1
> c579ec3a-9a89-11e2-8880-ca27ffbee488
> ROOT<
> account>admin
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1846) KVM - storage pools can silently fail to be unregistered, leading to failure to register later

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620193#comment-13620193
 ] 

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

Commit 3541aa86e34605e5ac4a99df84c47e6f6e7c71ee in branch refs/heads/4.0 from 
Chip Childers 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3541aa8 ]

CLOUDSTACK-1846, CLOUDSTACK-1845 - KVM Storage, sometimes KVMHA will remount
deleted NFS pools, causing failures when defining new storage pools. Sometimes
a storage pool has never been used on a host, and getStoragePool fails when
copying templates or in storage migration. deleteStoragePool(pool) often fails
silently, leaving no pool defined in libvirt, but a mountpoint left behind.
This patch handles some of these exceptions and brings forward any issues via
logging.

Signed-off-by: Chip Childers 


> KVM - storage pools can silently fail to be unregistered, leading to failure 
> to register later
> --
>
> Key: CLOUDSTACK-1846
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1846
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Marcus Sorensen
>Assignee: Marcus Sorensen
>Priority: Critical
> Fix For: 4.0.2, 4.1.0, 4.2.0
>
>
> This is a placeholder, I have a fix.
> A specific deleteStoragePool method attempts to delete a libvirt storage 
> pool, but failures are silently ignored (for example failure to unmount NFS 
> pool because it's in use). Later, when pools are registered, they can fail to 
> register because the mountpoint is in use. Part of my fix is to expose/log 
> failures, and the other part is an attempt to handle the failures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1846) KVM - storage pools can silently fail to be unregistered, leading to failure to register later

[Chip Childers (JIRA)]

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

Chip Childers resolved CLOUDSTACK-1846.
---

Resolution: Fixed

this has been applied to 4.0, master and 4.1 branches

> KVM - storage pools can silently fail to be unregistered, leading to failure 
> to register later
> --
>
> Key: CLOUDSTACK-1846
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1846
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Marcus Sorensen
>Assignee: Marcus Sorensen
>Priority: Critical
> Fix For: 4.0.2, 4.1.0, 4.2.0
>
>
> This is a placeholder, I have a fix.
> A specific deleteStoragePool method attempts to delete a libvirt storage 
> pool, but failures are silently ignored (for example failure to unmount NFS 
> pool because it's in use). Later, when pools are registered, they can fail to 
> register because the mountpoint is in use. Part of my fix is to expose/log 
> failures, and the other part is an attempt to handle the failures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1845) KVM - storage migration often fails

[Chip Childers (JIRA)]

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

Chip Childers resolved CLOUDSTACK-1845.
---

Resolution: Fixed

this has been applied to 4.0, master and 4.1 branches

> KVM - storage migration often fails
> ---
>
> Key: CLOUDSTACK-1845
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1845
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Marcus Sorensen
>Assignee: Marcus Sorensen
>Priority: Critical
> Fix For: 4.0.2, 4.1.0, 4.2.0
>
>
> This is more of a placeholder, I have the fix.
> When storage migration calls CopyVolumeCommand, it assumes that the primary 
> storage has been used/registered before on the KVM host. It does something 
> like a getStoragePool(poolUuid), and if primary storage pool (source or 
> destination) has never been used on the host it will fail. The fix is simply 
> to add the pool if it's not already there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1874) AWS Regions - Account table in cloud_usage DB has region_id.

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620201#comment-13620201
 ] 

Chip Childers commented on CLOUDSTACK-1874:
---

Is this actually critical?  It seems like it's Minor at best.

> AWS Regions - Account table in cloud_usage DB has region_id.
> 
>
> Key: CLOUDSTACK-1874
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1874
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
> Environment: Build from 4.1
>Reporter: Sangeetha Hariharan
>Assignee: Kishan Kavala
>Priority: Critical
> Fix For: 4.1.0
>
>
> Account table in cloud_usage DB has region_id.
> There should be no region_id in Account table since there is no notion of an 
> account being owned by a region and this notion has been already removed from 
> the cloud DB.
> mysql> desc account;
> +-+-+--+-+-+---+
> | Field   | Type| Null | Key | Default | Extra |
> +-+-+--+-+-+---+
> | id  | bigint(20) unsigned | NO   | PRI | NULL|   |
> | account_name| varchar(100)| YES  | | NULL|   |
> | uuid| varchar(40) | YES  | UNI | NULL|   |
> | type| int(1) unsigned | NO   | | NULL|   |
> | domain_id   | bigint(20) unsigned | YES  | | NULL|   |
> | state   | varchar(10) | NO   | | enabled |   |
> | removed | datetime| YES  | MUL | NULL|   |
> | cleanup_needed  | tinyint(1)  | NO   | | 0   |   |
> | network_domain  | varchar(100)| YES  | | NULL|   |
> | default_zone_id | bigint(20) unsigned | YES  | | NULL|   |
> | region_id   | int(10) unsigned| NO   | | 1   |   |
> +-+-+--+-+-+---+
> 11 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[Rohit Yadav (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620206#comment-13620206
 ] 

Rohit Yadav commented on CLOUDSTACK-1897:
-

This 8e917b1ad3c0d3076b0c6425ea3318a6d6dd5c25 removed the previously ignore 
rules, due to recent bvt merge, don't worry all's fine. Adding them back on 
master.

> ASF Master Build breaks due to unapproved licenses
> --
>
> Key: CLOUDSTACK-1897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
> Fix For: 4.2.0
>
>
> I tried to make a build of 4.2.0. It reported Build failure. I see the 
> following Information as the reason for the failure.
> *
> Summary
> ---
> Generated at: 2013-04-02T04:30:54-07:00
> Notes: 14
> Binaries: 223
> Archives: 0
> Standards: 6288
> Apache Licensed: 6278
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   tools/appliance/definitions/devcloud/zerodisk.sh
>   tools/appliance/definitions/devcloud/definition.rb
>   tools/appliance/definitions/devcloud/preseed.cfg
>   tools/appliance/definitions/devcloud/cleanup.sh
>   tools/appliance/definitions/devcloud/base.sh
>   tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
>   tools/appliance/definitions/systemvmtemplate64/definition.rb
>   tools/appliance/definitions/systemvmtemplate64/preseed.cfg
>   tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>   tools/appliance/definitions/systemvmtemplate64/base.sh
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1868) GetVmStatsCommand throws NullPointerException with VMWare

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620209#comment-13620209
 ] 

Chip Childers commented on CLOUDSTACK-1868:
---

We probably need more logs on this.

Francois, Ilya mentioned that he wasn't able to reproduce this.  Can you 
provide exact steps?

We'll probably need to downgrade from critical if we can't reproduce it, so 
that we can move forward with the release (unless we can reproduce and fix).

> GetVmStatsCommand throws NullPointerException with VMWare
> -
>
> Key: CLOUDSTACK-1868
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.1.0
>Reporter: Francois Gaudreault
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.1.0
>
>
> We see bunch of these in the log files of CloudStack.  Looks like the 
> GetVmStatsCommand crash with a Null pointer exception. We don't think it's 
> permission related since our CS user on vSphere can see all performance and 
> VM statistics using the vSphere client.
> INFO  [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined 
> to be up and running
> ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) 
> Unable to execute GetVmStatsCommand due to : Exception: 
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN  [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM 
> statistics.
> ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) 
> Unable to execute GetVmStatsCommand due to : Exception: 
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN  [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM 
> statistics.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620210#comment-13620210
 ] 

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

Commit 7e54f40a028a909e19756e07ebe05782f31cfd05 in branch refs/heads/master 
from [~bhaisaab]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7e54f40 ]

CLOUDSTACK-1897: Ignore appliance definitions for license checking

Regression caused due to 8e917b1ad3c0d3076b0c6425ea3318a6d6dd5c25

Signed-off-by: Rohit Yadav 


> ASF Master Build breaks due to unapproved licenses
> --
>
> Key: CLOUDSTACK-1897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Assignee: Rohit Yadav
> Fix For: 4.2.0
>
>
> I tried to make a build of 4.2.0. It reported Build failure. I see the 
> following Information as the reason for the failure.
> *
> Summary
> ---
> Generated at: 2013-04-02T04:30:54-07:00
> Notes: 14
> Binaries: 223
> Archives: 0
> Standards: 6288
> Apache Licensed: 6278
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   tools/appliance/definitions/devcloud/zerodisk.sh
>   tools/appliance/definitions/devcloud/definition.rb
>   tools/appliance/definitions/devcloud/preseed.cfg
>   tools/appliance/definitions/devcloud/cleanup.sh
>   tools/appliance/definitions/devcloud/base.sh
>   tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
>   tools/appliance/definitions/systemvmtemplate64/definition.rb
>   tools/appliance/definitions/systemvmtemplate64/preseed.cfg
>   tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>   tools/appliance/definitions/systemvmtemplate64/base.sh
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[Rohit Yadav (JIRA)]

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

Rohit Yadav resolved CLOUDSTACK-1897.
-

Resolution: Fixed

Fixed on master.

> ASF Master Build breaks due to unapproved licenses
> --
>
> Key: CLOUDSTACK-1897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Assignee: Rohit Yadav
> Fix For: 4.2.0
>
>
> I tried to make a build of 4.2.0. It reported Build failure. I see the 
> following Information as the reason for the failure.
> *
> Summary
> ---
> Generated at: 2013-04-02T04:30:54-07:00
> Notes: 14
> Binaries: 223
> Archives: 0
> Standards: 6288
> Apache Licensed: 6278
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   tools/appliance/definitions/devcloud/zerodisk.sh
>   tools/appliance/definitions/devcloud/definition.rb
>   tools/appliance/definitions/devcloud/preseed.cfg
>   tools/appliance/definitions/devcloud/cleanup.sh
>   tools/appliance/definitions/devcloud/base.sh
>   tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
>   tools/appliance/definitions/systemvmtemplate64/definition.rb
>   tools/appliance/definitions/systemvmtemplate64/preseed.cfg
>   tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>   tools/appliance/definitions/systemvmtemplate64/base.sh
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-280) Exception thrown on going to Step 5 of Add VM Instance - CloudRuntimeException: Tags are not defined for physical network in the zone id=1

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620213#comment-13620213
 ] 

Chip Childers commented on CLOUDSTACK-280:
--

Chandan - Does this bug still occur?  If not, can you please resolve it?

> Exception thrown on going to Step 5 of Add VM Instance - 
> CloudRuntimeException: Tags are not defined for physical network in the zone 
> id=1
> --
>
> Key: CLOUDSTACK-280
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-280
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Chandan Purushothama
>Assignee: Chandan Purushothama
> Fix For: 4.1.0
>
> Attachments: UIBug58.PNG
>
>
> 
> Steps to Reproduce:
> 
> 1. Deploy an Advanced Zone Setup with Two Physical Networks. One Physical 
> Network has guest,management,public,storage traffic while the other physical 
> network has guest traffic only. The Setup has one ESXi 5.0 Cluster.
> 2. I created a tag to the Guest Network of Physical Network 1 but did not 
> give a tag to the Guest Network of Physical Network 2.
> 3. Created a Network Offering with guest1 tag.
> 4. On attempting to create a guest network using Network Offering with guest1 
> tag and deploy a VM, an error message is thrown to the User. The 
> corresponding Screenshot has been attached to the bug report.
> http://10.223.131.202:8080/client/api?command=listNetworkOfferings&response=json&sessionkey=eTsL17aGxjvHtARSfuqsE4suKQU%3D&forvpc=false&zoneid=5ebc2a92-d1fe-4b29-bebc-3907baf7085c&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1349593023082
> { "listnetworkofferingsresponse" : 
> {"uuidList":[],"errorcode":530,"errortext":"Internal error executing command, 
> please contact your system administrator"} }
> ===
> Observations:
> ===
> mysql> select * from physical_network;
> +-+--+++---+---+---++-+-+-+
> | id  | uuid | name   | 
> data_center_id | vnet  | speed | domain_id | broadcast_domain_range | 
> state   | created | removed |
> +-+--+++---+---+---++-+-+-+
> | 200 | 62caf2e9-e47b-4ef8-861c-70ec97ac805c | Physical Network 1 |   
>1 | 2540-2550 | NULL  |  NULL | ZONE   | Enabled | 
> 2012-10-07 04:19:50 | NULL|
> | 201 | f2b5d29d-b5fe-4bac-a9b4-8cb212555d30 | Physical Network 2 |   
>1 | 2551-2560 | NULL  |  NULL | ZONE   | Enabled | 
> 2012-10-07 04:19:50 | NULL|
> +-+--+++---+---+---++-+-+-+
> 2 rows in set (0.00 sec)
> mysql> select * from physical_network_tags;
> ++-++
> | id | physical_network_id | tag|
> ++-++
> |  1 | 200 | guest1 |
> ++-++
> 1 row in set (0.00 sec)
> ===
> CloudRuntimeException:
> ===
> 2012-10-06 23:57:37,082 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-5:null) Access granted to Acct[3-mnf] to Domain:1/ by 
> DomainChecker
> 2012-10-06 23:57:37,084 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-5:null) Access to Acct[3-mnf] granted to Acct[3-mnf] by 
> DomainChecker
> 2012-10-06 23:57:37,211 ERROR [cloud.api.ApiDispatcher] 
> (catalina-exec-9:null) Exception while executing ListNetworkOfferingsCmd:
> com.cloud.utils.exception.CloudRuntimeException: Tags are not defined for 
> physical network in the zone id=1
> at 
> com.cloud.configuration.ConfigurationManagerImpl.searchForNetworkOfferings(ConfigurationManagerImpl.java:3442)
> at 
> com.cloud.api.commands.ListNetworkOfferingsCmd.execute(ListNetworkOfferingsCmd.java:179)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
>

[jira] [Assigned] (CLOUDSTACK-1897) ASF Master Build breaks due to unapproved licenses

[Rohit Yadav (JIRA)]

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

Rohit Yadav reassigned CLOUDSTACK-1897:
---

Assignee: Rohit Yadav

> ASF Master Build breaks due to unapproved licenses
> --
>
> Key: CLOUDSTACK-1897
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1897
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Assignee: Rohit Yadav
> Fix For: 4.2.0
>
>
> I tried to make a build of 4.2.0. It reported Build failure. I see the 
> following Information as the reason for the failure.
> *
> Summary
> ---
> Generated at: 2013-04-02T04:30:54-07:00
> Notes: 14
> Binaries: 223
> Archives: 0
> Standards: 6288
> Apache Licensed: 6278
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   tools/appliance/definitions/devcloud/zerodisk.sh
>   tools/appliance/definitions/devcloud/definition.rb
>   tools/appliance/definitions/devcloud/preseed.cfg
>   tools/appliance/definitions/devcloud/cleanup.sh
>   tools/appliance/definitions/devcloud/base.sh
>   tools/appliance/definitions/systemvmtemplate64/zerodisk.sh
>   tools/appliance/definitions/systemvmtemplate64/definition.rb
>   tools/appliance/definitions/systemvmtemplate64/preseed.cfg
>   tools/appliance/definitions/systemvmtemplate64/cleanup.sh
>   tools/appliance/definitions/systemvmtemplate64/base.sh
> ***

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-870) Client UI: Wrong character encoding for some languages

[Chip Childers (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620216#comment-13620216
 ] 

Chip Childers commented on CLOUDSTACK-870:
--

Gavin - Is this still an issue?

> Client UI: Wrong character encoding for some languages
> --
>
> Key: CLOUDSTACK-870
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-870
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.0
> Environment: CentOS6.3 x64 with apache cloudstack master branch
>Reporter: gavin lee
>  Labels: characters, encoding, jetty
> Fix For: 4.1.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> ACS 4.1 uses maven-jetty-plugin for developer runing management server.
> Currently there is character encoding issue for zh_CN, ja and ru_RU, see this 
> screen shot when I use Simplified Chinese: http://snag.gy/sGCn6.jpg
> I tried add utf-8 for page encoding and charset in both jsp file and pom.xml 
> file, but it didn't help.
> There is a way to display correct language, for example Simplified Chinese:
> 1. export LANG=zh_CN.UTF-8
> 2. mvn -pl :cloud-client-ui jetty:run
> 3. using native2ascii to convert resource file: native2ascii -encoding UTF-8 
> messages_zh_CN.properties.back messages_zh_CN.properties
> But the converted resource files are not human recognizable.
> There is no issue in ACS 4.0.x, since it use ant to run and tomcat as webapp 
> container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira