[jira] [Commented] (CLOUDSTACK-6316) [Automation]: Marvin Fixes and new Enhancements

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6316: fixed test data and their references in the test files and few 
more fixes in tests


 [Automation]: Marvin Fixes and new Enhancements
 ---

 Key: CLOUDSTACK-6316
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6316
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, marvin
Reporter: Santhosh Kumar Edukulla
Assignee: Santhosh Kumar Edukulla

 1. Earlier, i added a facility called DeleteDataCenter to clean up a 
 datacenter, it has some issues for deleting, fixed them. This change is under 
 deployDataCenter.py
 2. Earlier Added a new  facility, where we can deploy multiple zones and run 
 regression simultaneously on all zones with multiple hypervisors, 
 2.1 So, user creates the data center with multiple zones and hypervisors.
 2.2 Provides switches like zone and hypervisor to marvinPlugin and all tests 
 are run against that zone. With this patch, added hypervisor switch to 
 nose\marvinplugin.
 3. Fixed an issue in one of the test suite under maint, it is using 
 wait_for_vm function, which is not available.
 4. Added time taken for async job, post some stress scenarios, we want to 
 collect logs and analyze the time taken for various commands, their jobid and 
 time taken, added time taken facility.



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


[jira] [Commented] (CLOUDSTACK-6316) [Automation]: Marvin Fixes and new Enhancements

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6316: added else code in __createUserApiClient function


 [Automation]: Marvin Fixes and new Enhancements
 ---

 Key: CLOUDSTACK-6316
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6316
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, marvin
Reporter: Santhosh Kumar Edukulla
Assignee: Santhosh Kumar Edukulla

 1. Earlier, i added a facility called DeleteDataCenter to clean up a 
 datacenter, it has some issues for deleting, fixed them. This change is under 
 deployDataCenter.py
 2. Earlier Added a new  facility, where we can deploy multiple zones and run 
 regression simultaneously on all zones with multiple hypervisors, 
 2.1 So, user creates the data center with multiple zones and hypervisors.
 2.2 Provides switches like zone and hypervisor to marvinPlugin and all tests 
 are run against that zone. With this patch, added hypervisor switch to 
 nose\marvinplugin.
 3. Fixed an issue in one of the test suite under maint, it is using 
 wait_for_vm function, which is not available.
 4. Added time taken for async job, post some stress scenarios, we want to 
 collect logs and analyze the time taken for various commands, their jobid and 
 time taken, added time taken facility.



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


[jira] [Commented] (CLOUDSTACK-6316) [Automation]: Marvin Fixes and new Enhancements

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

Added few changes for CLOUDSTACK-6316

1. Added pep8 changes, delete dc flag.
2. Now, delete dc works only if flag is set under config.
3. SSH, retries and delay were altered to reduce the time
for ssh connection

Signed-off-by: Santhosh Edukulla santhosh.eduku...@citrix.com
Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org


 [Automation]: Marvin Fixes and new Enhancements
 ---

 Key: CLOUDSTACK-6316
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6316
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, marvin
Reporter: Santhosh Kumar Edukulla
Assignee: Santhosh Kumar Edukulla

 1. Earlier, i added a facility called DeleteDataCenter to clean up a 
 datacenter, it has some issues for deleting, fixed them. This change is under 
 deployDataCenter.py
 2. Earlier Added a new  facility, where we can deploy multiple zones and run 
 regression simultaneously on all zones with multiple hypervisors, 
 2.1 So, user creates the data center with multiple zones and hypervisors.
 2.2 Provides switches like zone and hypervisor to marvinPlugin and all tests 
 are run against that zone. With this patch, added hypervisor switch to 
 nose\marvinplugin.
 3. Fixed an issue in one of the test suite under maint, it is using 
 wait_for_vm function, which is not available.
 4. Added time taken for async job, post some stress scenarios, we want to 
 collect logs and analyze the time taken for various commands, their jobid and 
 time taken, added time taken facility.



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


[jira] [Commented] (CLOUDSTACK-6469) [Automation] Failed to created SSVM and CPVM in vmware advanced zone

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

Commit 4ae75b426bc0193df53f368ceb5a50f63c49aaf1 in cloudstack's branch 
refs/heads/4.4 from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4ae75b4 ]

CLOUDSTACK-6469


 [Automation] Failed to created SSVM and CPVM in vmware advanced zone
 

 Key: CLOUDSTACK-6469
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6469
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: vmware 5.1
 branch 4.4
Reporter: Rayees Namathponnan
Assignee: Mike Tutkowski
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management.rar


 Steps to reproduce 
 Step 1 : Created advanced zone with vmware 5.1
 Step 2 : Wait for SSVM and CPVM
 Result 
 SSVM and CPVM failed to create, observed below error 
 2014-04-21 17:33:33,831 INFO  [c.c.s.r.VmwareStorageProcessor] 
 (DirectAgent-22:ctx-cb35f168 10.223.250.130) Move volume out of 
 volume-wrapper VM
 2014-04-21 17:33:34,816 ERROR [c.c.s.r.VmwareStorageProcessor] 
 (DirectAgent-22:ctx-cb35f168 10.223.250.130) clone volume from base image 
 failed due to Exception: java.lang.RuntimeException
 Message: File [a885cec84fc23dfe8391b749f803bc78] ROOT-2/ROOT-2.vmdk was not 
 found
 java.lang.RuntimeException: File [a885cec84fc23dfe8391b749f803bc78] 
 ROOT-2/ROOT-2.vmdk was not found
 at 
 com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:335)
 at 
 com.cloud.hypervisor.vmware.mo.DatastoreMO.moveDatastoreFile(DatastoreMO.java:247)
 at 
 com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:477)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:81)
 at 
 com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:168)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:469)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-04-21 17:33:34,817 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-22:ctx-cb35f168) Seq 1-2883992611377381
 aslo getting below error while recreating ssvm
 and.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:28e3e559a4f334cdbc7ec313413206fc,ori
 gUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-vmware.ova,uuid:ae520c42-c9b1-11e3-ab7
 9-52b2d980df8a,id:8,format:OVA,accountId:1,checksum:ef593a061f3b7594ab0bfd9b0ed0a0d4,hvm:false,displayText:S
 ystemVM Template 
 (vSphere),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:a885cec8-4fc2-3df
 e-8391-b749f803bc78,id:1,poolType:NetworkFilesystem,host:nfs1-ccp.citrix.com,path:/home/common/automation/SC-CLO
 UD-QA03/primary1,port:2049,url:NetworkFilesystem://nfs1-ccp.citrix.com/home/common/automation/SC-CLOUD-QA03/primary1/?RO
 

[jira] [Commented] (CLOUDSTACK-6472) GenerateUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard commented on CLOUDSTACK-6472:
---

Ce patch is up on review board: https://reviews.apache.org/r/20557/

 GenerateUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Comment Edited] (CLOUDSTACK-6472) GenerateUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard edited comment on CLOUDSTACK-6472 at 4/23/14 7:35 AM:


The patch is up on review board: https://reviews.apache.org/r/20557/


was (Author: pyritschard):
Ce patch is up on review board: https://reviews.apache.org/r/20557/

 GenerateUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Commented] (CLOUDSTACK-6472) GenerateUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard commented on CLOUDSTACK-6472:
---

To reproduce:

1. Wait for cloud-usage to generate records for a running vm.
2. Delete the VM and wait for it to be in 'Expunged' state, it will have a 
non-null 'removed' field in the vm_instance table
3. Issue the GenerateUsageRecords API command, it will fail and log a stack 
trace to the management-server log



 GenerateUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Comment Edited] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard edited comment on CLOUDSTACK-6472 at 4/23/14 7:45 AM:


To reproduce:

1. Wait for cloud-usage to generate records for a running vm.
2. Delete the VM and wait for it to be in 'Expunged' state, it will have a 
non-null 'removed' field in the vm_instance table
3. Issue the listUsageRecords API command, it will fail and log a stack trace 
to the management-server log




was (Author: pyritschard):
To reproduce:

1. Wait for cloud-usage to generate records for a running vm.
2. Delete the VM and wait for it to be in 'Expunged' state, it will have a 
non-null 'removed' field in the vm_instance table
3. Issue the GenerateUsageRecords API command, it will fail and log a stack 
trace to the management-server log



 listUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Updated] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard updated CLOUDSTACK-6472:
--

Summary: listUsageRecords generates NPEs for expunging instances  (was: 
GenerateUsageRecords generates NPEs for expunging instances)

 listUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Commented] (CLOUDSTACK-6472) GenerateUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard commented on CLOUDSTACK-6472:
---

Here is the relevant stacktrace:

2014-04-22 00:18:07,417 ERROR [cloud.api.ApiServer] 
(catalina-exec-2:ctx-60c87510 ctx-22de212f ctx-a88a3dd7) unhandled exception 
executing api command: listUsageRecords
java.lang.NullPointerException
at 
com.cloud.api.ApiResponseHelper.createUsageResponse(ApiResponseHelper.java:3308)
at 
org.apache.cloudstack.api.command.admin.usage.GetUsageRecordsCmd.execute(GetUsageRecordsCmd.java:119)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:531)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:374)
at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:323)
at com.cloud.api.ApiServlet.access$000(ApiServlet.java:53)
at com.cloud.api.ApiServlet$1.run(ApiServlet.java:115)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:112)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:74)
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:615)
at 
org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:647)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at 
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:744)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2282)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

 GenerateUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The GenerateUsageRecords API command, pulls down the list of usage records in 
 the cloud_usage database and augments records with information pulled from 
 the cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Updated] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard updated CLOUDSTACK-6472:
--

Description: 
The listUsageRecords API command, pulls down the list of usage records in the 
cloud_usage database and augments records with information pulled from the 
cloud database.

When dealing with instance records, only instances which are do not have a 
value for the removed field are considered. Unfortunately, since the output of 
_entityMgr.findById is not checked this means that Null Pointer Exceptions are 
generated when trying to access the output for expunged VMs.

The attached patch fixes the issue and applies a similar fix for other similar 
cases.

  was:
The GenerateUsageRecords API command, pulls down the list of usage records in 
the cloud_usage database and augments records with information pulled from the 
cloud database.

When dealing with instance records, only instances which are do not have a 
value for the removed field are considered. Unfortunately, since the output of 
_entityMgr.findById is not checked this means that Null Pointer Exceptions are 
generated when trying to access the output for expunged VMs.

The attached patch fixes the issue and applies a similar fix for other similar 
cases.


 listUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The listUsageRecords API command, pulls down the list of usage records in the 
 cloud_usage database and augments records with information pulled from the 
 cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Created] (CLOUDSTACK-6479) Strict and Preferred modes should only be allowed in Implict Dedication Planner Service Offerings

2014-04-23 Thread Saksham Srivastava (JIRA)
Saksham Srivastava created CLOUDSTACK-6479:
--

 Summary: Strict and Preferred modes should only be allowed in 
Implict Dedication Planner Service Offerings
 Key: CLOUDSTACK-6479
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6479
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.0
Reporter: Saksham Srivastava


While creating service offering choosing deployment planner other than Implicit 
Dedication Planner the modes(Strict and Preferred) should not be allowed.
However CS allows creation of service offerings with other planners using 
Implicit Dedication Planner modes.

 create serviceoffering name=so1 displaytext=other_planner storagetype=shared 
 deploymentplanner=UserConcentratedPodPlanner 
 serviceofferingdetails[0].key=ImplicitDedicationMode 
 serviceofferingdetails[0].value=Strict 
 serviceofferingdetails[1].key=pciDevice 
 serviceofferingdetails[1].value=Group%20of%20NVIDIA%20Corporation%20GK107GL%20[GRID%20K1]%20GPUs
  serviceofferingdetails[2].key=vgpuType 
 serviceofferingdetails[2].key=vgpuType 
 serviceofferingdetails[2].value=passthrough

serviceoffering:
name = so1
id = d6a6db13-5eb8-4e93-924a-127bf89d8029
created = 2014-04-23T12:15:00+0530
defaultuse = False
deploymentplanner = UserConcentratedPodPlanner
displaytext = other_planner
iscustomized = True
issystem = False
isvolatile = False
limitcpuuse = False
offerha = False
serviceofferingdetails:
ImplicitDedicationMode = Strict
pciDevice = Group%20of%20NVIDIA%20Corporation%20GK107GL%20[GRID%20K1]%20GPUs
vgpuType = passthrough
storagetype = shared



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


[jira] [Created] (CLOUDSTACK-6480) Creating Service Offering with Implict Dedication planner fails with message: Please specify the pciDevice and vgpuType correctly

2014-04-23 Thread Saksham Srivastava (JIRA)
Saksham Srivastava created CLOUDSTACK-6480:
--

 Summary: Creating Service Offering with Implict Dedication planner 
fails with message:  Please specify the pciDevice and vgpuType correctly
 Key: CLOUDSTACK-6480
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6480
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.0
Reporter: Saksham Srivastava


While creating SO with Implicit Dedication planner in Strict/Preferred Mode 
fails with log message Please specify the pciDevice and vgpuType correctly.

Ideally SO should be created without specifying pciDevice abd vgpuType.



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


[jira] [Commented] (CLOUDSTACK-6474) IAM - Not able to list shared networks that is created with scope=all

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

Commit 52f40433b9dbc5d78e7000410da09cb7f55e499f in cloudstack's branch 
refs/heads/4.4 from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=52f4043 ]

CLOUDSTACK-6474: IAM - Not able to list shared networks that is created with 
scope=all

Changes:
- On startup the root domain group should be created
- Also the SYSTEM and Root Admin accounts should be added to that group
- This will make sure that the root domain shared network's policy gets 
attached to the root domain group


 IAM - Not able to list shared networks that is created with scope=all
 ---

 Key: CLOUDSTACK-6474
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6474
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: IAM
Affects Versions: 4.4.0
 Environment: Build from 4.4
Reporter: Sangeetha Hariharan
Assignee: Prachi Damle
Priority: Critical
 Fix For: 4.4.0


 IAM - Not able to list shared networks that is created with scope=all
 Steps to reproduce the problem:
 As admin , create a shared network with scope=all.
 As regular user , tried to list networks. No shared network is returned.
 http://10.223.49.6:8080/client/api?command=listNetworksresponse=jsonsessionkey=wOwS556QDduN5hRqHf1PU3gPBEw%3DlistAll=truepage=1pagesize=20_=1398206302627
 listnetworksresponse : { } }
 As admin user , I am able to list this network:
 http://10.223.49.6:8080/client/api?command=listNetworksresponse=jsonsessionkey=58UVhAXG49kJHSOENDGphnXDEh4%3DlistAll=truepage=1pagesize=20_=1398206454900
 { listnetworksresponse : { count:3 ,network : [  
 {id:65324d0a-5571-4e96-aebe-89d45fbabc72,name:test-domain,displaytext:test-domain,broadcastdomaintype:Vlan,traffictype:Guest,gateway:10.223.1.1,netmask:255.255.255.0,cidr:10.223.1.0/24,zoneid:75d61334-ff70-49c3-99ed-3af702cd51d7,zonename:BLR1,networkofferingid:564de11f-a786-44cf-a729-c4683a12dfe0,networkofferingname:DefaultSharedNetworkOfferingWithSGService,networkofferingdisplaytext:Offering
  for Shared Security group enabled 
 networks,networkofferingconservemode:true,networkofferingavailability:Optional,issystem:false,state:Setup,related:65324d0a-5571-4e96-aebe-89d45fbabc72,broadcasturi:vlan://501,dns1:4.2.2.2,type:Shared,vlan:501,acltype:Domain,subdomainaccess:false,domainid:691ab662-6793-42a0-96e6-3b31a2c4e52d,domain:D1,service:[{name:UserData},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:Dhcp,capability:[{name:DhcpAccrossMultipleSubnets,value:true,canchooseservicecapability:false}]},{name:SecurityGroup}],networkdomain:cs1cloud.internal,physicalnetworkid:3856a5bc-8509-4a7f-a92e-86146cbc6bc1,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[],displaynetwork:true,strechedl2subnet:false},
  
 {id:49146336-bf81-4861-a2bd-5c92efc14cff,name:test,displaytext:test,broadcastdomaintype:Vlan,traffictype:Guest,gateway:10.223.1.1,netmask:255.255.255.0,cidr:10.223.1.0/24,zoneid:75d61334-ff70-49c3-99ed-3af702cd51d7,zonename:BLR1,networkofferingid:564de11f-a786-44cf-a729-c4683a12dfe0,networkofferingname:DefaultSharedNetworkOfferingWithSGService,networkofferingdisplaytext:Offering
  for Shared Security group enabled 
 networks,networkofferingconservemode:true,networkofferingavailability:Optional,issystem:false,state:Setup,related:49146336-bf81-4861-a2bd-5c92efc14cff,broadcasturi:vlan://500,dns1:4.2.2.2,type:Shared,vlan:500,acltype:Domain,subdomainaccess:true,domainid:e5e2ad7a-c019-11e3-907f-4adf980f9414,domain:ROOT,service:[{name:UserData},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:Dhcp,capability:[{name:DhcpAccrossMultipleSubnets,value:true,canchooseservicecapability:false}]},{name:SecurityGroup}],networkdomain:cs1cloud.internal,physicalnetworkid:3856a5bc-8509-4a7f-a92e-86146cbc6bc1,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[],displaynetwork:true,strechedl2subnet:false},
  
 {id:aee03e51-468e-4311-aebc-827d9a43adf0,name:test,displaytext:test,broadcastdomaintype:Vlan,traffictype:Guest,gateway:10.1.1.1,netmask:255.255.255.0,cidr:10.1.1.0/24,zoneid:75d61334-ff70-49c3-99ed-3af702cd51d7,zonename:BLR1,networkofferingid:987d8feb-73b5-4f01-9152-6680a31bc60a,networkofferingname:DefaultIsolatedNetworkOfferingWithSourceNatService,networkofferingdisplaytext:Offering
  for Isolated networks with Source Nat service 
 

[jira] [Created] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.

2014-04-23 Thread manasaveloori (JIRA)
manasaveloori created CLOUDSTACK-6481:
-

 Summary: Vhd-util is not copied to xenserver from MS...As a result 
system VMs fail to start in CS.
 Key: CLOUDSTACK-6481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Install and Setup, XenServer
Affects Versions: 4.4.0
 Environment: Xenserver6.2 added to CS 4.4
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0
 Attachments: management-server.log

PXE booted the Xenserver.
Added it to CS 4.4.
observed that system vms fails to deploy with Exception:

2014-04-23 04:23:46,875 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
(DirectAgent-3:ctx-cf6a380b) Catch Exception 
com.cloud.utils.exception.CloudRuntimeException for template +  due to 
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
5cffabad-fb53-27ad-96eb-a1728623dd7c
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
5cffabad-fb53-27ad-96eb-a1728623dd7c
at 
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846)
at 
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
at 
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received:


Checked in xenserver the vhd-util file is missing under /opt/cloud/bin.


As work around copied the vhd-util to /opt/cloud/bin.


Attaching the log files




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


[jira] [Updated] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.

2014-04-23 Thread manasaveloori (JIRA)

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

manasaveloori updated CLOUDSTACK-6481:
--

Attachment: management-server.log

 Vhd-util is not copied to xenserver from MS...As a result system VMs fail to 
 start in CS.
 -

 Key: CLOUDSTACK-6481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, XenServer
Affects Versions: 4.4.0
 Environment: Xenserver6.2 added to CS 4.4
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log


 PXE booted the Xenserver.
 Added it to CS 4.4.
 observed that system vms fails to deploy with Exception:
 2014-04-23 04:23:46,875 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
 (DirectAgent-3:ctx-cf6a380b) Catch Exception 
 com.cloud.utils.exception.CloudRuntimeException for template +  due to 
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received:
 Checked in xenserver the vhd-util file is missing under /opt/cloud/bin.
 As work around copied the vhd-util to /opt/cloud/bin.
 Attaching the log files



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


[jira] [Updated] (CLOUDSTACK-6338) [Automation] Failed to NetScaler Device with error un.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertathB

2014-04-23 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-6338:
---

Assignee: Rajesh Battala

 [Automation]  Failed to NetScaler Device with error 
 un.security.validator.ValidatorException: PKIX path building failed: 
 sun.security.provider.certpath.SunCertathBuilderException: unable to find 
 valid certification path to requested target} 
 

 Key: CLOUDSTACK-6338
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6338
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: KVM EIP/ELB (RHEL 6.3)
Reporter: Rayees Namathponnan
Assignee: Rajesh Battala
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management.rar


 Failed to add Netscaler during EIP/ELB configuration 
 2014-04-03 21:29:46,460 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-18:ctx-72880204 ctx-2d222b87 ctx-c9a147a3) ===END===  
 10.223.240
 .193 -- GET  
 username=nsrootphysicalnetworkid=94c18f72-8a9c-4d0a-ba43-9a24606f3391url=http%3A%2F%2F10.223.240.177%3Fusername%3
 Dnsroot%26publicinterface%3D1%2F1%26hostname%3D10.223.240.177%26privateinterface%3D1%2F1%26lbdevicecapacity%3D50%26networkdevice
 type%3DNetscalerVPXLoadBalancer%26lbdevicededicated%3Dfalse%26numretries%3D2networkdevicetype=NetscalerVPXLoadBalancerapiKey=K
 BeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScgcommand=addNetscalerLoadBalancersignature
 =PeFY913bQNNkKk5NjxxXzL%2BAEHQ%3Dresponse=json
 2014-04-03 21:29:46,462 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-9:job-13) Add job-13 into job monitoring
 2014-04-03 21:29:46,463 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-9:job-13) Executing AsyncJobVO {id:13, userId:
  2, accountId: 2, instanceType: None, instanceId: null, cmd: 
 com.cloud.api.commands.AddNetscalerLoadBalancerCmd, cmdInfo: {phys
 icalnetworkid:94c18f72-8a9c-4d0a-ba43-9a24606f3391,response:json,username:nsroot,cmdEventType:PHYSICAL.LOADBALANCE
 R.ADD,ctxUserId:2,networkdevicetype:NetscalerVPXLoadBalancer,httpmethod:GET,ctxAccountId:2,ctxStartEventId:5
 2,password:nsroot,apiKey:KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScg,signat
 ure:PeFY913bQNNkKk5NjxxXzL+AEHQ\u003d,url:http://10.223.240.177?username\u003dnsroot\u0026publicinterface\u003d1/1\u0026ho
 stname\u003d10.223.240.177\u0026privateinterface\u003d1/1\u0026lbdevicecapacity\u003d50\u0026networkdevicetype\u003dNetscalerVPX
 LoadBalancer\u0026lbdevicededicated\u003dfalse\u0026password\u003dnsroot\u0026numretries\u003d2},
  cmdVersion: 0, status: IN_PRO
 GRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 
 73187150500751, completeMsid: null, lastUpdated: null, lastPolle
 d: null, created: null}
 2014-04-03 21:29:46,464 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-e2bcddac) ===START===  10.223.240.193 -- GET  
 signature=%
 2FNYT%2FQGLpRKIHiBiILgVLOgSoFU%3DapiKey=KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8RFKCbu6Yik21VURn8uYrgScg
 command=queryAsyncJobResultresponse=jsonjobid=6f3a6915-6ed5-4b52-b467-7e0cfa30e2cf
 2014-04-03 21:29:46,483 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-9:job-13 ctx-39a38b39) Received unknown p
 arameters for command addNetscalerLoadBalancer. Unknown parameters : 
 ctxstarteventid
 2014-04-03 21:29:46,552 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-e2bcddac ctx-96d05190 ctx-6ab9c015) ===END===  
 10.223.240
 .193 -- GET  
 signature=%2FNYT%2FQGLpRKIHiBiILgVLOgSoFU%3DapiKey=KBeoHDz29tjADzbpQ5OEQNgVZ6xYCRE1XDzb4UmfdG_K86pHhU2AYqFZzF8ii8R
 FKCbu6Yik21VURn8uYrgScgcommand=queryAsyncJobResultresponse=jsonjobid=6f3a6915-6ed5-4b52-b467-7e0cfa30e2cf
 2014-04-03 21:29:47,589 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-9:job-13) Complete async job-13, jobStatus: FAILED, 
 resultCode: 530, result: 
 org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Failed
  to log in to Netscaler device at 10.223.240.177 due to 
 sun.security.validator.ValidatorException: PKIX path building failed: 
 sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
 valid certification path to requested target}



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


[jira] [Created] (CLOUDSTACK-6482) [API-LoadBalancing]Passing invalid vm name and vmip to assignToLoadBalancerRule API is not giving proper error message in response.

2014-04-23 Thread manasaveloori (JIRA)
manasaveloori created CLOUDSTACK-6482:
-

 Summary: [API-LoadBalancing]Passing invalid vm name and vmip to 
assignToLoadBalancerRule API is not giving proper error message in response.
 Key: CLOUDSTACK-6482
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6482
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.4.0
Reporter: manasaveloori
 Fix For: 4.4.0


1. Configure the LB rule.
2. Assign a VM to the LB rule by providing invalid VM name or invalid VMid.
API:
http://10.147.59.222:8096/client/api?command=assignToLoadBalancerRuleid=3vmidipmap[0].vmid=e59de8ab-7ed5-4432-8838-ac600323ddvmidipmap[0].vmip=10.1.1.247
 

Response:
assigntoloadbalancerruleresponse cloud-stack-version=4.4.0-SNAPSHOT
jobid683e99a1-8ce2-47be-93f6-a11e18685910/jobid
/assigntoloadbalancerruleresponse

Observation:

API does not proper error message to user.
In MS logs able to proper message:

com.cloud.exception.InvalidParameterValueException: Invalid ip address 
10.1.1..9 passed in vmidipmap for vmid e59de8ab-7ed5-4432-8838-ac64600323dd




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


[jira] [Created] (CLOUDSTACK-6483) [UI-Loading balancing]Multiple UI issues while assigning the VM to LB rule.

2014-04-23 Thread manasaveloori (JIRA)
manasaveloori created CLOUDSTACK-6483:
-

 Summary: [UI-Loading balancing]Multiple UI issues while assigning 
the VM to LB rule.
 Key: CLOUDSTACK-6483
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6483
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.4.0
Reporter: manasaveloori
Priority: Critical
 Fix For: 4.4.0



Observed the following UI issues while configuring  LB rule.

1.  Create LB rule and while assigning the VM ip addresses select both 
primary and secondary ips
Issue:API is passing only primary IP.

2.  Now remove the vm from lb rule and try to add it again .
Issue1:VM is not displayed.Displayed only when navigating from Ipaddress 
page-lbrule-addvm

Issue2:Now if I add the VM by selecting any ip, it throws message as “

“Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, 
please use parameter[index].field=XXX, e.g. userGroupList[0].group=httpGroup”

3.  Create LB rule by assigning primary IP. I want to assign secondary ip 
of same vm to same lb rule.
Issue:UI not displaying the VM once one ip of the vm is assigned to LB rule.


4.  Small improvement in UI page , please reduce the length of the drop 
down white space area. When there is one ip it is showing more length with 
white space area




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


[jira] [Closed] (CLOUDSTACK-6232) isolated network can no longer reserve ip range

2014-04-23 Thread Daan Hoogland (JIRA)

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

Daan Hoogland closed CLOUDSTACK-6232.
-

Resolution: Fixed

 isolated network can no longer reserve ip range
 ---

 Key: CLOUDSTACK-6232
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6232
 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, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Priority: Blocker
 Fix For: 4.3.0, 4.4.0


 We found a functionality that we use once in a while no longer is permitted 
 in 4.2.1. It seems in line with the philosophy of cloudstack but is hurting 
 our operation. In 4.1.1 we could add a bridged network with the following 
 network offering:
 cno.traffictype = GUEST
 cno.guestiptype = Isolated
 cno.specifyipranges = True
 cno.specifyvlan = False
 cno.serviceproviderlist = [ { service: Connectivity, provider: 
 NiciraNvp},
 { service: UserData, provider: 
 VirtualRouter},
 { service: Dhcp, provider: VirtualRouter} 
 ]



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


[jira] [Updated] (CLOUDSTACK-6232) isolated network can no longer reserve ip range

2014-04-23 Thread Daan Hoogland (JIRA)

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

Daan Hoogland updated CLOUDSTACK-6232:
--

Fix Version/s: 4.3.0

 isolated network can no longer reserve ip range
 ---

 Key: CLOUDSTACK-6232
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6232
 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, 4.3.0, 4.4.0
Reporter: Daan Hoogland
Assignee: Daan Hoogland
Priority: Blocker
 Fix For: 4.3.0, 4.4.0


 We found a functionality that we use once in a while no longer is permitted 
 in 4.2.1. It seems in line with the philosophy of cloudstack but is hurting 
 our operation. In 4.1.1 we could add a bridged network with the following 
 network offering:
 cno.traffictype = GUEST
 cno.guestiptype = Isolated
 cno.specifyipranges = True
 cno.specifyvlan = False
 cno.serviceproviderlist = [ { service: Connectivity, provider: 
 NiciraNvp},
 { service: UserData, provider: 
 VirtualRouter},
 { service: Dhcp, provider: VirtualRouter} 
 ]



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


[jira] [Updated] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard updated CLOUDSTACK-6472:
--

Attachment: (was: 0001-handle-removed-entities.patch)

 listUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard

 The listUsageRecords API command, pulls down the list of usage records in the 
 cloud_usage database and augments records with information pulled from the 
 cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Updated] (CLOUDSTACK-6472) listUsageRecords generates NPEs for expunging instances

2014-04-23 Thread Pierre-Yves Ritschard (JIRA)

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

Pierre-Yves Ritschard updated CLOUDSTACK-6472:
--

Attachment: 0001-handle-removed-entities.patch

patch without whitespace glitches

 listUsageRecords generates NPEs for expunging instances
 ---

 Key: CLOUDSTACK-6472
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6472
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Usage
Affects Versions: 4.3.0
 Environment: linux
Reporter: Pierre-Yves Ritschard
 Attachments: 0001-handle-removed-entities.patch


 The listUsageRecords API command, pulls down the list of usage records in the 
 cloud_usage database and augments records with information pulled from the 
 cloud database.
 When dealing with instance records, only instances which are do not have a 
 value for the removed field are considered. Unfortunately, since the output 
 of _entityMgr.findById is not checked this means that Null Pointer Exceptions 
 are generated when trying to access the output for expunged VMs.
 The attached patch fixes the issue and applies a similar fix for other 
 similar cases.



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


[jira] [Created] (CLOUDSTACK-6484) Unable to expunge VM

2014-04-23 Thread Erik Weber (JIRA)
Erik Weber created CLOUDSTACK-6484:
--

 Summary: Unable to expunge VM
 Key: CLOUDSTACK-6484
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6484
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, XenServer
Affects Versions: 4.3.0
 Environment: ACS 4.3, XenServer 6.2 SP1, NFS primary and secondary 
storage
Reporter: Erik Weber
Priority: Minor


VM creation failed, and is now unable to expunge the stale vm.

Log excerpt:

2014-04-23 12:37:38,632 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-17:ctx-63a3ec65) ===START===  172.30.86.24 -- GET  
command=expungeVirtualMachineid=05c7735f-43ab-4e75-b211-3791bceb77f9response=jsonsessionkey=OMJLVfWJLawkctDOi728%2B2sfpzI%3D_=1398256658590
2014-04-23 12:37:38,664 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(catalina-exec-17:ctx-63a3ec65 ctx-fc4c0a3b) submit async job-827, details: 
AsyncJobVO {id:827, userId: 2, accountId: 2, instanceType: VirtualMachine, 
instanceId: 80, cmd: org.apache.cloudstack.api.command.admin.vm.ExpungeVMCmd, 
cmdInfo: 
{id:05c7735f-43ab-4e75-b211-3791bceb77f9,response:json,sessionkey:OMJLVfWJLawkctDOi728+2sfpzI\u003d,cmdEventType:VM.EXPUNGE,ctxUserId:2,httpmethod:GET,_:1398256658590,ctxAccountId:2,ctxStartEventId:3505},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 345049426471, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-04-23 12:37:38,667 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-6:job-827) Add job-827 into job monitoring
2014-04-23 12:37:38,667 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-6:job-827) Executing AsyncJobVO {id:827, userId: 2, 
accountId: 2, instanceType: VirtualMachine, instanceId: 80, cmd: 
org.apache.cloudstack.api.command.admin.vm.ExpungeVMCmd, cmdInfo: 
{id:05c7735f-43ab-4e75-b211-3791bceb77f9,response:json,sessionkey:OMJLVfWJLawkctDOi728+2sfpzI\u003d,cmdEventType:VM.EXPUNGE,ctxUserId:2,httpmethod:GET,_:1398256658590,ctxAccountId:2,ctxStartEventId:3505},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 345049426471, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-04-23 12:37:38,668 DEBUG [c.c.a.ApiServlet] (catalina-exec-17:ctx-63a3ec65 
ctx-fc4c0a3b) ===END===  172.30.86.24 -- GET  
command=expungeVirtualMachineid=05c7735f-43ab-4e75-b211-3791bceb77f9response=jsonsessionkey=OMJLVfWJLawkctDOi728%2B2sfpzI%3D_=1398256658590
2014-04-23 12:37:38,719 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-6:job-827 ctx-602236ef) Sync job-828 execution on object 
VmWorkJobQueue.80
2014-04-23 12:37:38,724 WARN  [c.c.u.d.Merovingian2] 
(API-Job-Executor-6:job-827 ctx-602236ef) Was unable to find lock for the key 
vm_instance80 and thread id 2057517175
2014-04-23 12:37:41,720 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-19:ctx-309c7bb0) ===START===  172.30.86.24 -- GET  
command=queryAsyncJobResultjobId=849b6fb8-c20f-4362-8fc4-6877f36df874response=jsonsessionkey=OMJLVfWJLawkctDOi728%2B2sfpzI%3D_=1398256661662
2014-04-23 12:37:41,753 DEBUG [c.c.a.ApiServlet] (catalina-exec-19:ctx-309c7bb0 
ctx-51354ef7) ===END===  172.30.86.24 -- GET  
command=queryAsyncJobResultjobId=849b6fb8-c20f-4362-8fc4-6877f36df874response=jsonsessionkey=OMJLVfWJLawkctDOi728%2B2sfpzI%3D_=1398256661662
2014-04-23 12:37:41,821 DEBUG [c.c.c.CapacityManagerImpl] 
(API-Job-Executor-6:job-827 ctx-602236ef) VM state transitted from :Expunging 
to Expunging with event: ExpungeOperationvm's original host id: null new host 
id: null host id before state transition: null
2014-04-23 12:37:41,823 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(API-Job-Executor-6:job-827 ctx-602236ef) Destroying vm VM[User|i-9-80-VM]
2014-04-23 12:37:41,824 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(API-Job-Executor-6:job-827 ctx-602236ef) Cleaning up NICS
2014-04-23 12:37:41,832 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-6:job-827) Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.ExpungeVMCmd
java.lang.NullPointerException
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:489)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:455)
at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1739)
at com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:3855)
at com.cloud.vm.UserVmManagerImpl.expungeVm(UserVmManagerImpl.java:2134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 

[jira] [Updated] (CLOUDSTACK-6222) [Automation] config generator script is broken

2014-04-23 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan updated CLOUDSTACK-6222:


Issue Type: Test  (was: Bug)

 [Automation] config generator script is broken
 --

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


 Config generator scripts are broken because of the changes in 
 configGenerator.py 
   tools/marvin/marvin/configGenerator.py
   tools/marvin/marvin/sandbox/advanced/advanced_env.py
tools/marvin/marvin/sandbox/advancedsg/advancedsg_env.py
   tools/marvin/marvin/sandbox/basic/basic_env.py
   tools/marvin/marvin/sandbox/demo/simulator/simulator_setup.py
 1. 
 =
  python basic_env.py 
 Traceback (most recent call last):
   File basic_env.py, line 142, in module
 cfg = describeResources(cfg_parser)
   File basic_env.py, line 55, in describeResources
 pn = physical_network()
 NameError: global name 'physical_network' is not defined
 ==
 2. Fix the  logger path in the config file.



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


[jira] [Updated] (CLOUDSTACK-6443) [Automation] Fix the script test_volumes.py - AttributeError: VirtualMachine instance has no attribute 'hostid'

2014-04-23 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan updated CLOUDSTACK-6443:


Issue Type: Test  (was: Bug)

 [Automation] Fix the script test_volumes.py - AttributeError: 
 VirtualMachine instance has no attribute 'hostid'
 -

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


 Two Test Cases Effected due to the same bug. Need to be corrected at two 
 places:
 est_07_resize_fail
 test_08_resize_volume
 *Error Message1*:
 VirtualMachine instance has no attribute 'hostid'
   begin captured logging  
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 STARTED : TC: test_07_resize_fail :::
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: Fail 
 Resize Volume ID: b5521198-97f1-4f2c-afea-fcadf70d4249
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: resizeVolume {'diskofferingid': 
 u'9015ab2c-1d88-4e39-bcd8-d7fa22a1b2ca', 'id': 'invalid id'}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: bCeC5im5Fgxi23vWk4lBzKbQm7A=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=bCeC5im5Fgxi23vWk4lBzKbQm7A%3Ddiskofferingid=9015ab2c-1d88-4e39-bcd8-d7fa22a1b2caid=invalid+id
  HTTP/1.1 431 330
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=bCeC5im5Fgxi23vWk4lBzKbQm7A%3Ddiskofferingid=9015ab2c-1d88-4e39-bcd8-d7fa22a1b2caid=invalid+id
  Response: { resizevolumeresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command resizevolume due to invalid value. Invalid parameter id 
 value=invalid id due to incorrect long value format, or entity does not exist 
 or due to incorrect parameter annotation for the field in api cmd class.} }
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: resizeVolume {'diskofferingid': 'invalid id', 'id': 
 u'b5521198-97f1-4f2c-afea-fcadf70d4249'}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: DbNaHKDzesuJcTU1thWGQg88UPk=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=DbNaHKDzesuJcTU1thWGQg88UPk%3Ddiskofferingid=invalid+idid=b5521198-97f1-4f2c-afea-fcadf70d4249
  HTTP/1.1 431 342
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qresponse=jsoncommand=resizeVolumesignature=DbNaHKDzesuJcTU1thWGQg88UPk%3Ddiskofferingid=invalid+idid=b5521198-97f1-4f2c-afea-fcadf70d4249
  Response: { resizevolumeresponse : 
 {uuidList:[],errorcode:431,cserrorcode:,errortext:Unable to 
 execute API command resizevolume due to invalid value. Invalid parameter 
 diskofferingid value=invalid id due to incorrect long value format, or entity 
 does not exist or due to incorrect parameter annotation for the field in api 
 cmd class.} }
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 sending GET request: listVolumes {'virtualmachineid': 
 u'bca5f583-139f-46e4-87d5-09fb5adac313', 'type': 'ROOT', 'listall': True}
 test_07_resize_fail (integration.smoke.test_volumes.TestVolumes): DEBUG: 
 Computed Signature by Marvin: f1JO1y9Ye2m1qw3+QCZu9+B8zRo=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 

[jira] [Updated] (CLOUDSTACK-6440) [Automation] Fix the script test_secondary_storage.py - listTemplates response is empty

2014-04-23 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan updated CLOUDSTACK-6440:


Issue Type: Test  (was: Bug)

 [Automation] Fix the script test_secondary_storage.py - listTemplates 
 response is empty
 -

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


 *Add System VM Template ID while querying for the System VM Templates inorder 
 to list the Template.*
 
 listTemplatesResponse:
 
 'NoneType' object is not iterable
   begin captured logging  
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 STARTED : TC: test_02_sys_template_ready :::
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listZones {'name': u'test0'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: t23Z4s6lQrS2hRbKTWxJfI+9a5k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test0command=listZonessignature=t23Z4s6lQrS2hRbKTWxJfI%2B9a5k%3Dresponse=json
  HTTP/1.1 200 394
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test0command=listZonessignature=t23Z4s6lQrS2hRbKTWxJfI%2B9a5k%3Dresponse=json
  Response: { listzonesresponse : { count:1 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 sending GET request: listZones {'name': u'test1'}
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Computed Signature by Marvin: Tt/qzyUZeeDi5QbtHNV6Ve7DHao=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=test1command=listZonessignature=Tt%2FqzyUZeeDi5QbtHNV6Ve7DHao%3Dresponse=json
  HTTP/1.1 200 394
 test_02_sys_template_ready 
 (integration.smoke.test_secondary_storage.TestSecStorageServices): DEBUG: 
 Request: 
 

[jira] [Commented] (CLOUDSTACK-6435) Add new Command line options to setup/bindir/cloud-setup-databases.in and remove OS specific commands

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6435: Add new Command line options to 
setup/bindir/cloud-setup-databases.in and remove OS specific commands


 Add new Command line options to setup/bindir/cloud-setup-databases.in and 
 remove OS specific commands
 -

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


 Currently the python script  setup/bindir/cloud-setup-databases.in for 
 setup databases uses template based parameters which will get replaced during 
 rpm build. 
 Along with this also enable new command line options to over ride those 
 template based parameters if the same get passed as command line options.
 Accept the following options:
 1. db-conf-path
 2. db-files-path
 3. encryption-jar-path
 4. encryption-key-file
 Also replace code that calls OS specific commands with python specific 
 libraries.



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


[jira] [Created] (CLOUDSTACK-6485) [vpc] new private gateway network is registered wrong in network table

2014-04-23 Thread Anton Opgenoort (JIRA)
Anton Opgenoort created CLOUDSTACK-6485:
---

 Summary: [vpc] new private gateway network is registered wrong in 
network table
 Key: CLOUDSTACK-6485
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6485
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.2.1, 4.3.0, 4.4.0, 4.3.1
Reporter: Anton Opgenoort


When creating a private gateway for a VPC router on a network not yet known to 
Cloudstack, Cloudstack ‘documents’ this network in the networks table.
For normal guest networks, which should be associated with a single VPC, 
Cloudstack includes the VPC_ID in the database. The VPC_ID field is used to 
provision all networks and nics on a VPC router when it is created. Since this 
table is all about network provisioning it makes sense to ‘document’ the 
network cidr and gateway present in that nework. For guest tiers this usually 
is the VPC router itself, so the interface IP’s on a VPC router are the gateway 
IP’s found in the networks table.

Unfortunately the VPC_ID is also recorded for the private gateway network when 
it is first created. So the first VPC to be plugged on the private gateway 
network also has that same network associated as a guest network tier, instead 
of just a private gateway network.

This by itself will not quickly become a problem, because private gateways are 
first plugged on a running vpc router which is not likely to be recreated any 
time soon after that.
But as soon as this first ever VPC router on the private gateway network is 
recreated due to a destroy of the VPC Router, all associated networks are 
looked up in the networks table. 
Because the private gateway network is ‘documented’ with the actual upstream 
gateway used by the VPC router defintion, the VPC router provisions a NIC on 
the private gateway network using the IP address of the actual upstream gateway 
creating an IP conflict on the private gateway network, effectively breaking 
down the upstream gateway functionality for all attached private gateways of 
other vpc's.




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


[jira] [Commented] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-6481:
--

which template is being used??

 Vhd-util is not copied to xenserver from MS...As a result system VMs fail to 
 start in CS.
 -

 Key: CLOUDSTACK-6481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, XenServer
Affects Versions: 4.4.0
 Environment: Xenserver6.2 added to CS 4.4
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log


 PXE booted the Xenserver.
 Added it to CS 4.4.
 observed that system vms fails to deploy with Exception:
 2014-04-23 04:23:46,875 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
 (DirectAgent-3:ctx-cf6a380b) Catch Exception 
 com.cloud.utils.exception.CloudRuntimeException for template +  due to 
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received:
 Checked in xenserver the vhd-util file is missing under /opt/cloud/bin.
 As work around copied the vhd-util to /opt/cloud/bin.
 Attaching the log files



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


[jira] [Updated] (CLOUDSTACK-6477) UI: Load Balancing - unable to add Load Balancing rule = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti updated CLOUDSTACK-6477:
-

Priority: Critical  (was: Blocker)

 UI: Load Balancing - unable to add Load Balancing rule = error Unable to 
 decode parameter vmidipmap[0].vmip[]; if specifying an object array, please 
 use parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Commented] (CLOUDSTACK-6475) [Automation] communication between cloudstack agent and MS disconnecting continuously

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-6475:
--

Is there any issue with Network??

 [Automation] communication between cloudstack agent and MS disconnecting 
 continuously  
 ---

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

 Attachments: Agent_log.rar, management-server.rar


 This issue is observed during automation, run.
 communication between cloudstack agent and ms getting disconnected 
 continuously;  observed below error in agent log
  2014-04-22 04:08:47,867 INFO  [cloud.agent.Agent] (AgentShutdownThread:null) 
 Stopping the agent: Reason = sig.kill
 2014-04-22 04:10:41,456 INFO  [cloud.agent.AgentShell] (main:null) Agent 
 started
 2014-04-22 04:10:41,500 INFO  [cloud.agent.AgentShell] (main:null) 
 Implementation Version is 4.4.0-SNAPSHOT
 2014-04-22 04:10:41,502 INFO  [cloud.agent.AgentShell] (main:null) 
 agent.properties found at /etc/cloudstack/agent/agent.properties
 2014-04-22 04:10:41,551 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to using properties file for storage
 2014-04-22 04:10:41,552 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to the constant time backoff algorithm
 2014-04-22 04:10:41,572 INFO  [cloud.utils.LogUtils] (main:null) log4j 
 configuration found at /etc/cloudstack/agent/log4j-cloud.xml
 2014-04-22 04:10:41,722 INFO  [cloud.agent.Agent] (main:null) id is 0
 2014-04-22 04:10:42,501 INFO  [kvm.resource.LibvirtComputingResource] 
 (main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
 2014-04-22 04:10:42,590 INFO  [cloud.agent.Agent] (main:null) Agent [id = 0 : 
 type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 
 10.223.49.195 : port = 8250
 2014-04-22 04:10:42,664 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connecting to 10.223.49.195:8250
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 SSL: Handshake done
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connected to 10.223.49.195:8250
 2014-04-22 04:10:42,941 WARN  [kvm.resource.LibvirtComputingResource] 
 (Agent-Handler-1:null) Could not read cpuinfo_max_freq
 2014-04-22 04:10:43,158 INFO  [cloud.serializer.GsonHelper] 
 (Agent-Handler-1:null) Default Builder inited.
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Proccess agent startup answer, agent id = 0
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) Set 
 agent id 0
 2014-04-22 04:10:43,233 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Startup Response Received: agent id = 0
 2014-04-22 04:11:40,925 INFO  [cloud.agent.Agent] (Agent-Handler-1:null) Lost 
 connection to the server. Dealing with the remaining commands...
 2014-04-22 04:11:42,352 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 0
 2014-04-22 04:11:42,368 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 1
 2014-04-22 04:11:42,383 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 2
 2014-04-22 04:11:42,398 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 3
 2014-04-22 04:11:42,413 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 4
 2014-04-22 04:11:42,414 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error; reboot the host
 2014-04-22 04:11:42,472 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 

[jira] [Closed] (CLOUDSTACK-6456) [Automation] Few vm deployment job never executed during automation run

2014-04-23 Thread Rayees Namathponnan (JIRA)

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

Rayees Namathponnan closed CLOUDSTACK-6456.
---

Resolution: Not a Problem

 [Automation] Few vm deployment job never executed during automation run
 ---

 Key: CLOUDSTACK-6456
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6456
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
 Environment: KVM (RHEL 6,3)
 4.4  build
Reporter: Rayees Namathponnan
Assignee: Harikrishna Patnala
Priority: Blocker
 Fix For: 4.4.0

 Attachments: CLOUDSTACK-6456.rar


 This issue is observed during automation run, few vm deployment job never 
 getting executed
 Please search for job-204 in attached log, there is no result after executing 
 2014-04-17 22:43:33,344 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-98:job-204 = [ befd67d7-61a1-47c0-9d5e-52943fc
 9bd41 ]) Start completed for VM VM[User|e54121f1-561b-48c6-a781-15490cbc17d6]
 2014-04-17 22:43:33,359 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-204 = [ befd67d7-61a1-47c0-9d5e-52943fc9bd
 41 ]) Complete async job-204 = [ befd67d7-61a1-47c0-9d5e-52943fc9bd41 ], 
 jobStatus: 1, resultCode: 0, result: org.apache.clouds
 tack.api.response.UserVmResponse@4f73448
 2014-04-17 22:43:33,364 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-98:job-204 = [ befd67d7-61a1-47c0-9d5e-52943fc9bd
 41 ]) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd 
 for job-204 = [ befd67d7-61a1-47c0-9d5e-52943fc9bd41
  ]
 mysql select * from async_job where 
 uuid=befd67d7-61a1-47c0-9d5e-52943fc9bd41\G;
 *** 1. row ***
 id: 204
user_id: 2
 account_id: 2
session_key: NULL
  instance_type: NULL
instance_id: NULL
job_cmd: org.apache.cloudstack.api.command.user.vm.DeployVMCmd
 job_cmd_originator: NULL
   job_cmd_info: 
 {id:62,response:json,serviceofferingid:5e71a638-3308-48d0-8330-dbc33ce92e71,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:a6564e83-6858-456d-a774-f55e0a31f034,hypervisor:KVM,templateid:ea892f38-c682-11e3-9a99-1a6f7bb0d0a8,account:test-TestVMLifeCycle-test_deploy_vm-CFY6M6,httpmethod:GET,domainid:ea868120-c682-11e3-9a99-1a6f7bb0d0a8,ctxAccountId:2,ctxStartEventId:902,apiKey:YbjvO-Gt8sQu-nabyabTQ82MoQ5r1jRDcjggSBzbRrLM6D7RvCp8tZSIjHVZVkwevhHNkJjPgE2I9FUh9Uyq_w,signature:YEdh9AvtStpDkdCi79lnASoSqKA\u003d,displayname:testserver}
job_cmd_ver: 0
  callback_type: 0
   callback_address: NULL
 job_status: 1
 job_process_status: 0
job_result_code: 0
 job_result: 
 org.apache.cloudstack.api.response.UserVmResponse/virtualmachine/{id:e54121f1-561b-48c6-a781-15490cbc17d6,name:e54121f1-561b-48c6-a781-15490cbc17d6,displayname:testserver,account:test-TestVMLifeCycle-test_deploy_vm-CFY6M6,domainid:ea868120-c682-11e3-9a99-1a6f7bb0d0a8,domain:ROOT,created:2014-04-17T21:24:27-0700,state:Running,haenable:false,zoneid:a6564e83-6858-456d-a774-f55e0a31f034,zonename:Adv-KVM-Zone1,hostid:3860fa83-e583-4795-951a-797076f38501,hostname:Rack2Host11.lab.vmops.com,templateid:ea892f38-c682-11e3-9a99-1a6f7bb0d0a8,templatename:CentOS
  5.5(64-bit) no GUI (KVM),templatedisplaytext:CentOS 5.5(64-bit) no GUI 
 (KVM),passwordenabled:false,serviceofferingid:5e71a638-3308-48d0-8330-dbc33ce92e71,serviceofferingname:Small
  
 Instance,cpunumber:1,cpuspeed:100,memory:256,guestosid:eaa9dc4c-c682-11e3-9a99-1a6f7bb0d0a8,rootdeviceid:0,rootdevicetype:ROOT,securitygroup:[],nic:[{id:59376483-a918-4eb1-aa77-bc2c35dc563a,networkid:ad1bdf70-2ea9-4ff2-8a2f-36f8c4a0d936,networkname:test-TestVMLifeCycle-test_deploy_vm-CFY6M6-network,netmask:255.255.255.0,gateway:10.1.1.1,ipaddress:10.1.1.245,isolationuri:vlan://2342,broadcasturi:vlan://2342,traffictype:Guest,type:Isolated,isdefault:true,macaddress:02:00:53:5c:00:01}],hypervisor:KVM,instancename:i-38-62-QA,tags:[],affinitygroup:[],displayvm:true,isdynamicallyscalable:false,jobid:befd67d7-61a1-47c0-9d5e-52943fc9bd41,jobstatus:0}
  job_init_msid: 29066118877352
  job_complete_msid: 29066118877352
created: 2014-04-18 04:24:27
   last_updated: 2014-04-18 05:43:33
last_polled: 2014-04-18 05:24:35
removed: NULL
   uuid: befd67d7-61a1-47c0-9d5e-52943fc9bd41
 1 row in set (0.00 sec)
 ERROR:
 No query specified



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


[jira] [Commented] (CLOUDSTACK-6444) [Automation] Fix the script test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-6444:
--

Aren't these scripts passing before?? What changed now??

 [Automation] Fix the script test_primary_storage.py - Wrong iscsi path 
 format - it should be /targetIQN/LUN 
 --

 Key: CLOUDSTACK-6444
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Error Message:
 Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
   begin captured logging  
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 STARTED : TC: test_01_primary_storage_iscsi :::
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listZones {}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  HTTP/1.1 200 735
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
  Response: { listzonesresponse : { count:2 ,zone : [  
 {id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
  
 {id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listPods {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  HTTP/1.1 200 314
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
  Response: { listpodsresponse : { count:1 ,pod : [  
 {id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
  ] } }
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 sending GET request: listClusters {'zoneid': 
 u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
 test_01_primary_storage_iscsi 
 (integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG: 
 Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 

[jira] [Commented] (CLOUDSTACK-6439) [Automation] Assertion Error: Fix the script test_disk_offerings.py - provision type is not returned by listDiskOfferings response

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-6439:
--

why this test is failing now??it was passing before

 [Automation] Assertion Error: Fix the script test_disk_offerings.py - 
 provision type is not returned by listDiskOfferings response
 

 Key: CLOUDSTACK-6439
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6439
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer 
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Blocker
 Fix For: 4.4.0


 Two Cases needs to be corrected:
 1. test_02_create_sparse_type_disk_offering
 2. test_04_create_fat_type_disk_offering
 =
 Assertion Errors:
 =
 *Assertion Error 1*
 Check provisionig type in createServiceOffering
   begin captured logging  
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 STARTED : TC: test_02_create_sparse_type_disk_offering :::
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 sending GET request: createDiskOffering {'name': 'Sparse Type Disk offering', 
 'disksize': 1, 'displaytext': 'Sparse Type Disk offering'}
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 Computed Signature by Marvin: m0/TZdrSBwiGRHLEVS5pdjF/y0U=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=Sparse+Type+Disk+offeringcommand=createDiskOfferingdisksize=1signature=m0%2FTZdrSBwiGRHLEVS5pdjF%2Fy0U%3Ddisplaytext=Sparse+Type+Disk+offeringresponse=json
  HTTP/1.1 200 297
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=Sparse+Type+Disk+offeringcommand=createDiskOfferingdisksize=1signature=m0%2FTZdrSBwiGRHLEVS5pdjF%2Fy0U%3Ddisplaytext=Sparse+Type+Disk+offeringresponse=json
  Response: { creatediskofferingresponse :  { diskoffering : 
 {id:ffece54d-6736-4d72-8426-6eeade833db8,name:Sparse Type Disk 
 offering,displaytext:Sparse Type Disk 
 offering,disksize:1,created:2014-04-16T15:52:37-0700,iscustomized:false,storagetype:shared,displayoffering:true}
  }  }
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 Created Disk offering with ID: ffece54d-6736-4d72-8426-6eeade833db8
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 sending GET request: listDiskOfferings {'id': 
 u'ffece54d-6736-4d72-8426-6eeade833db8'}
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 Computed Signature by Marvin: XtzgOFFqAn/1FdLA2F+/yDvHKbQ=
 requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection 
 (1): 10.223.240.161
 requests.packages.urllib3.connectionpool: DEBUG: GET 
 /client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qid=ffece54d-6736-4d72-8426-6eeade833db8command=listDiskOfferingssignature=XtzgOFFqAn%2F1FdLA2F%2B%2FyDvHKbQ%3Dresponse=json
  HTTP/1.1 200 310
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG: 
 Request: 
 http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qid=ffece54d-6736-4d72-8426-6eeade833db8command=listDiskOfferingssignature=XtzgOFFqAn%2F1FdLA2F%2B%2FyDvHKbQ%3Dresponse=json
  Response: { listdiskofferingsresponse : { count:1 ,diskoffering : [  
 {id:ffece54d-6736-4d72-8426-6eeade833db8,name:Sparse Type Disk 
 offering,displaytext:Sparse Type Disk 
 offering,disksize:1,created:2014-04-16T15:52:37-0700,iscustomized:false,storagetype:shared,displayoffering:true}
  ] } }
 test_02_create_sparse_type_disk_offering 
 (integration.smoke.test_disk_offerings.TestCreateDiskOffering): CRITICAL: 
 FAILED: 

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

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti updated CLOUDSTACK-5212:
-

Priority: Critical  (was: Blocker)

 Need Support for the LXC for the Report sockets CS-4908
 ---

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


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



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


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

2014-04-23 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-5212:
--

feature need to be enabled for LXC

 Need Support for the LXC for the Report sockets CS-4908
 ---

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


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



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


[jira] [Created] (CLOUDSTACK-6486) Failed to create more than one isolated network for the same account

2014-04-23 Thread Alena Prokharchyk (JIRA)
Alena Prokharchyk created CLOUDSTACK-6486:
-

 Summary: Failed to create more than one isolated network for the 
same account
 Key: CLOUDSTACK-6486
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6486
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.4.0
Reporter: Alena Prokharchyk
Priority: Blocker






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


[jira] [Updated] (CLOUDSTACK-6486) Failed to create more than one isolated network for the same account

2014-04-23 Thread Alena Prokharchyk (JIRA)

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

Alena Prokharchyk updated CLOUDSTACK-6486:
--

  Description: 
Steps to reproduce:
==
1) login as root admin
2) create first isolated network while deploying a vm, from deployVm dialog
3) Try to create a second isolated network, either from the deploy vm dialog, 
or from Networks tab. following error occurs:

ERROR [c.c.a.ApiServer] (2128435204@qtp-415454110-20:ctx-fe01b290 ctx-c27f313c) 
unhandled exception executing api command: [Ljava.lang.String;@33607ddc
com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
offering with specified id to network profile
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:691)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1940)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1901)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createGuestNetwork(NetworkOrchestrator.java:1901)
at 
com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1362)
at 
com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1310)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at 
com.cloud.network.NetworkServiceImpl.commitNetwork(NetworkServiceImpl.java:1310)
at 
com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy157.createGuestNetwork(Unknown Source)
at 
org.apache.cloudstack.api.command.admin.network.CreateNetworkCmdByAdmin.execute(CreateNetworkCmdByAdmin.java:57)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

[jira] [Resolved] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.

2014-04-23 Thread Anthony Xu (JIRA)

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

Anthony Xu resolved CLOUDSTACK-6481.


Resolution: Invalid


you need to install vhd-util in management server


172 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-1:ctx-644104c2) Unable to 
create destination path: /opt/cloud/bin on 10.147.40.29 but trying anyway
2014-04-23 04:22:49,256 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-1:ctx-644104c2) We cannot locate 
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/../vhd-util
2014-04-23 04:22:49,676 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-1:ctx-644104c2) Management network is on 
pif=7347ced1-eecf-f3ca-0227-70d092ff4a44
2014-04-23 04:22:49,680 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-1:ctx-644104c2) Seq 1-4533998924855246849: Response Received: 


 Vhd-util is not copied to xenserver from MS...As a result system VMs fail to 
 start in CS.
 -

 Key: CLOUDSTACK-6481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, XenServer
Affects Versions: 4.4.0
 Environment: Xenserver6.2 added to CS 4.4
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log


 PXE booted the Xenserver.
 Added it to CS 4.4.
 observed that system vms fails to deploy with Exception:
 2014-04-23 04:23:46,875 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
 (DirectAgent-3:ctx-cf6a380b) Catch Exception 
 com.cloud.utils.exception.CloudRuntimeException for template +  due to 
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received:
 Checked in xenserver the vhd-util file is missing under /opt/cloud/bin.
 As work around copied the vhd-util to /opt/cloud/bin.
 Attaching the log files



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


[jira] [Updated] (CLOUDSTACK-6477) UI: Load Balancing - add VMs fails = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[index].field=XXX, ~

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang updated CLOUDSTACK-6477:
-

Summary: UI: Load Balancing - add VMs fails = error Unable to decode 
parameter vmidipmap[0].vmip[]; if specifying an object array, please use 
parameter[index].field=XXX, ~   (was: UI: Load Balancing - unable to add Load 
Balancing rule = error Unable to decode parameter vmidipmap[0].vmip[]; if 
specifying an object array, please use parameter[index].field=XXX, ~ )

 UI: Load Balancing - add VMs fails = error Unable to decode parameter 
 vmidipmap[0].vmip[]; if specifying an object array, please use 
 parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Commented] (CLOUDSTACK-6477) UI: Load Balancing - add VMs fails = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[index].field=XXX,

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6477: UI - Load Balancing - add VMs = fix error 'Unable to decode 
parameter vmidipmap[0].vmip[]; if specifying an object array, please use 
parameter[index].field=XXX, ~ '


 UI: Load Balancing - add VMs fails = error Unable to decode parameter 
 vmidipmap[0].vmip[]; if specifying an object array, please use 
 parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Resolved] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5

2014-04-23 Thread Anthony Xu (JIRA)

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

Anthony Xu resolved CLOUDSTACK-6382.


Resolution: Fixed

commit 1c10d00ec9268c75c919bf4d873dc0e51eb9e1d2
Author: Anthony Xu anthony...@citrix.com
Date:   Thu Apr 10 17:47:27 2014 -0700

avoid to create same FileSR on host more than once


 System VM's failing to start with XenServer 6.2.5
 -

 Key: CLOUDSTACK-6382
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6382
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0


 Steps:
 Build : 4.4 
 Configure Adv zone with XenServer 6.2.5
  
 Observation:
  
 System VM’s are failing to start with below exception and there are lot of 
 SR’s that got added to XenServer .   
  
 2014-04-10 16:09:42,622 DEBUG [c.c.a.t.Request] 
 (Work-Job-Executor-4:job-4/job-22 ctx-4609aa64) Seq 1-8947526559678332946: 
 Executing:  { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1, 
 Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/1/,origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
  Template 
 (XenServer),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.101/Sailaja/gpuss1,_role:Image}},name:routing-1,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
  Template 
 (XenServer),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:0a336642-b7d7-3262-ae46-8f06ccdf8c30,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpups1/?ROLE=PrimarySTOREUUID=0a336642-b7d7-3262-ae46-8f06ccdf8c30}},name:routing-1,hypervisorType:XenServer}},executeInSequence:false,options:{},wait:10800}}]
  }
 2014-04-10 16:09:42,624 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
 (Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) template 1 is already in 
 store:1, type:Primary
 2014-04-10 16:09:42,627 DEBUG [o.a.c.s.v.VolumeServiceImpl] 
 (Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Found template routing-1 in 
 storage pool 1 with VMTemplateStoragePool id: 2
 2014-04-10 16:09:42,630 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-13:ctx-d982de4d) Seq 1-8947526559678332946: Executing request
 2014-04-10 16:09:42,654 DEBUG [o.a.c.s.v.VolumeServiceImpl] 
 (Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Acquire lock on 
 VMTemplateStoragePool 2 with timeout 3600 seconds
 2014-04-10 16:09:42,657 DEBUG [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-13:ctx-d982de4d) Task is not done uuid: 
 b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Thu Apr 10 21:30:06 IST 2014
 finished: Thu Jan 01 05:30:00 IST 1970
   status: pending
   residentOn: com.xensource.xenapi.Host@514ac968
 progress: 0.0
 type: none/
   result:
errorInfo: []
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []
  
 2014-04-10 16:09:42,660 DEBUG [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-13:ctx-d982de4d) Task is not done uuid: 
 b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Thu Apr 10 21:30:06 IST 2014
 finished: Thu Jan 01 05:30:00 IST 1970
   status: pending
   residentOn: com.xensource.xenapi.Host@514ac968
 progress: 0.0
 type: none/
   result:
errorInfo: []
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []
  
 2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-13:ctx-d982de4d) Task is done success
 2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor] 
 (DirectAgent-13:ctx-d982de4d) Failed to destroy pbd
 2014-04-10 

[jira] [Commented] (CLOUDSTACK-6477) UI: Load Balancing - add VMs fails = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[index].field=XXX,

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6477: UI - Load Balancing - add VMs = fix error 'Unable to decode 
parameter vmidipmap[0].vmip[]; if specifying an object array, please use 
parameter[index].field=XXX, ~ '


 UI: Load Balancing - add VMs fails = error Unable to decode parameter 
 vmidipmap[0].vmip[]; if specifying an object array, please use 
 parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Resolved] (CLOUDSTACK-6477) UI: Load Balancing - add VMs fails = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[index].field=XXX, ~

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang resolved CLOUDSTACK-6477.
--

Resolution: Fixed

 UI: Load Balancing - add VMs fails = error Unable to decode parameter 
 vmidipmap[0].vmip[]; if specifying an object array, please use 
 parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Closed] (CLOUDSTACK-6477) UI: Load Balancing - add VMs fails = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[index].field=XXX, ~

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang closed CLOUDSTACK-6477.



 UI: Load Balancing - add VMs fails = error Unable to decode parameter 
 vmidipmap[0].vmip[]; if specifying an object array, please use 
 parameter[index].field=XXX, ~ 
 --

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

 Attachments: add_LoadBalancingRule_error_1.PNG


 http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
 {
 assigntoloadbalancerruleresponse: {
 uuidList: [],
 errorcode: 430,
 cserrorcode: ,
 errortext: Unable to decode parameter vmidipmap[0].vmip[]; if 
 specifying an object array, please use parameter[index].field=XXX, e.g. 
 userGroupList[0].group=httpGroup
 }
 }



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


[jira] [Commented] (CLOUDSTACK-6442) [Automation] Extraction of Volume failed due to the requested plugin could not be found.

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

Commit 33c0d6c7bbb2e85f87935dee64dccbe2ee7f264c in cloudstack's branch 
refs/heads/4.4 from [~anthonyxu]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33c0d6c ]

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Extraction of Volume failed due to the requested plugin could 
 not be found.
 

 Key: CLOUDSTACK-6442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Use Case:
 Extract Volume from the Setup
 
 The requested plugin could not be found.
 
 2014-04-16 15:59:56,332 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669) ===START===  10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,335 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Processing Seq 4-314:  { Cmd , 
 MgmtId: -1, via: 4, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2014-04-16 15:59:56,343 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Sending Seq 4-314:  { Ans: , 
 MgmtId: 112957957439171, via: 4, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2014-04-16 15:59:56,369 DEBUG [c.c.u.AccountManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) Access to 
 {Vol[31|vm=null|DATADISK]} granted to 
 Acct[ed7cd506-e810-496f-94ee-3e422b3a6449-test-TestVolumes-test_01_create_volume-7K52C0]
  by RoleBasedEntityAccessChecker
 2014-04-16 15:59:56,388 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) submit async 
 job-169, details: AsyncJobVO {id:169, userId: 2, accountId: 2, instanceType: 
 Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,389 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) ===END===  
 10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,394 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-76:job-169) Add job-169 into job monitoring
 2014-04-16 15:59:56,394 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-76:job-169) Executing AsyncJobVO {id:169, userId: 2, 
 accountId: 2, instanceType: Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: 

[jira] [Commented] (CLOUDSTACK-6438) [Automation] Creation of Template from Volume failed due to the requested plugin could not be found.

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

Commit 33c0d6c7bbb2e85f87935dee64dccbe2ee7f264c in cloudstack's branch 
refs/heads/4.4 from [~anthonyxu]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=33c0d6c ]

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Creation of Template from Volume failed due to the requested 
 plugin could not be found.
 

 Key: CLOUDSTACK-6438
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6438
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 
 The requested plugin could not be found.
 
 2014-04-16 15:55:43,850 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-41:job-97) Executing AsyncJobVO {id:97, userId: 2, 
 accountId: 2, instanceType: Template, instanceId: 205, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {cmdEventType:TEMPLATE.CREATE,ctxUserId:2,ispublic:False,isextractable:False,httpmethod:GET,volumeid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,domainid:fe2a30b2-c5a8-11e3-8f55-66bc12ed7ec3,isfeatured:False,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,ostypeid:feba4b70-c5a8-11e3-8f55-66bc12ed7ec3,id:205,response:json,name:Cent
  OS Template-7WLKMH,passwordenabled:False,displaytext:Cent OS 
 Template,account:test-TestCreateTemplate-SCKX71,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,ctxAccountId:2,ctxStartEventId:291,signature:8ILr8Hdfhc35eHAm1D0L7lkgRw4\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:55:43,853 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b) ===START===  10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,877 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-41:job-97 ctx-554395e3) Received unknown parameters for 
 command createTemplate. Unknown parameters : isextractable account
 2014-04-16 15:55:43,921 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b ctx-62916341 ctx-11cd890f) ===END===  
 10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,947 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
 (API-Job-Executor-41:job-97 ctx-554395e3) template 205 is already in store:1, 
 type:Image
 2014-04-16 15:55:43,972 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] 
 (API-Job-Executor-41:job-97 ctx-554395e3) copyAsync inspecting src type 
 VOLUME copyAsync inspecting dest type TEMPLATE
 2014-04-16 15:55:44,005 DEBUG [c.c.a.t.Request] (API-Job-Executor-41:job-97 
 ctx-554395e3) Seq 2-7234469851417280562: Sending  { Cmd , MgmtId: 
 112957957439171, via: 2(marron.lab.vmops.com), Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ac0c4b04-6b72-38b1-a72f-c7fe7163d17a,id:1,poolType:NetworkFilesystem,host:nfs1-ccp.citrix.com,path:/home/common/automation/SC_QA_AUTO7/primary4,port:2049,url:NetworkFilesystem://nfs1-ccp.citrix.com/home/common/automation/SC_QA_AUTO7/primary4/?ROLE=PrimarySTOREUUID=ac0c4b04-6b72-38b1-a72f-c7fe7163d17a}},name:ROOT-17,size:21474836480,path:01269023-5389-407f-8dfc-a3ab22074207,volumeId:19,vmName:i-12-17-QA,accountId:12,format:VHD,id:19,deviceId:0,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/12/205,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,id:205,format:RAW,accountId:12,hvm:true,displayText:Cent
  OS 
 

[jira] [Resolved] (CLOUDSTACK-6438) [Automation] Creation of Template from Volume failed due to the requested plugin could not be found.

2014-04-23 Thread Anthony Xu (JIRA)

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

Anthony Xu resolved CLOUDSTACK-6438.


Resolution: Fixed

commit 33c0d6c7bbb2e85f87935dee64dccbe2ee7f264c
Author: Anthony Xu anthony...@citrix.com
Date:   Wed Apr 23 15:30:36 2014 -0700

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Creation of Template from Volume failed due to the requested 
 plugin could not be found.
 

 Key: CLOUDSTACK-6438
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6438
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 
 The requested plugin could not be found.
 
 2014-04-16 15:55:43,850 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-41:job-97) Executing AsyncJobVO {id:97, userId: 2, 
 accountId: 2, instanceType: Template, instanceId: 205, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {cmdEventType:TEMPLATE.CREATE,ctxUserId:2,ispublic:False,isextractable:False,httpmethod:GET,volumeid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,domainid:fe2a30b2-c5a8-11e3-8f55-66bc12ed7ec3,isfeatured:False,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,ostypeid:feba4b70-c5a8-11e3-8f55-66bc12ed7ec3,id:205,response:json,name:Cent
  OS Template-7WLKMH,passwordenabled:False,displaytext:Cent OS 
 Template,account:test-TestCreateTemplate-SCKX71,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,ctxAccountId:2,ctxStartEventId:291,signature:8ILr8Hdfhc35eHAm1D0L7lkgRw4\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:55:43,853 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b) ===START===  10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,877 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-41:job-97 ctx-554395e3) Received unknown parameters for 
 command createTemplate. Unknown parameters : isextractable account
 2014-04-16 15:55:43,921 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b ctx-62916341 ctx-11cd890f) ===END===  
 10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,947 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
 (API-Job-Executor-41:job-97 ctx-554395e3) template 205 is already in store:1, 
 type:Image
 2014-04-16 15:55:43,972 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] 
 (API-Job-Executor-41:job-97 ctx-554395e3) copyAsync inspecting src type 
 VOLUME copyAsync inspecting dest type TEMPLATE
 2014-04-16 15:55:44,005 DEBUG [c.c.a.t.Request] (API-Job-Executor-41:job-97 
 ctx-554395e3) Seq 2-7234469851417280562: Sending  { Cmd , MgmtId: 
 112957957439171, via: 2(marron.lab.vmops.com), Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ac0c4b04-6b72-38b1-a72f-c7fe7163d17a,id:1,poolType:NetworkFilesystem,host:nfs1-ccp.citrix.com,path:/home/common/automation/SC_QA_AUTO7/primary4,port:2049,url:NetworkFilesystem://nfs1-ccp.citrix.com/home/common/automation/SC_QA_AUTO7/primary4/?ROLE=PrimarySTOREUUID=ac0c4b04-6b72-38b1-a72f-c7fe7163d17a}},name:ROOT-17,size:21474836480,path:01269023-5389-407f-8dfc-a3ab22074207,volumeId:19,vmName:i-12-17-QA,accountId:12,format:VHD,id:19,deviceId:0,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/12/205,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,id:205,format:RAW,accountId:12,hvm:true,displayText:Cent
  OS 
 

[jira] [Commented] (CLOUDSTACK-6442) [Automation] Extraction of Volume failed due to the requested plugin could not be found.

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Extraction of Volume failed due to the requested plugin could 
 not be found.
 

 Key: CLOUDSTACK-6442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Use Case:
 Extract Volume from the Setup
 
 The requested plugin could not be found.
 
 2014-04-16 15:59:56,332 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669) ===START===  10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,335 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Processing Seq 4-314:  { Cmd , 
 MgmtId: -1, via: 4, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2014-04-16 15:59:56,343 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Sending Seq 4-314:  { Ans: , 
 MgmtId: 112957957439171, via: 4, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2014-04-16 15:59:56,369 DEBUG [c.c.u.AccountManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) Access to 
 {Vol[31|vm=null|DATADISK]} granted to 
 Acct[ed7cd506-e810-496f-94ee-3e422b3a6449-test-TestVolumes-test_01_create_volume-7K52C0]
  by RoleBasedEntityAccessChecker
 2014-04-16 15:59:56,388 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) submit async 
 job-169, details: AsyncJobVO {id:169, userId: 2, accountId: 2, instanceType: 
 Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,389 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) ===END===  
 10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,394 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-76:job-169) Add job-169 into job monitoring
 2014-04-16 15:59:56,394 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-76:job-169) Executing AsyncJobVO {id:169, userId: 2, 
 accountId: 2, instanceType: Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, 

[jira] [Commented] (CLOUDSTACK-6438) [Automation] Creation of Template from Volume failed due to the requested plugin could not be found.

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Creation of Template from Volume failed due to the requested 
 plugin could not be found.
 

 Key: CLOUDSTACK-6438
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6438
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 
 The requested plugin could not be found.
 
 2014-04-16 15:55:43,850 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-41:job-97) Executing AsyncJobVO {id:97, userId: 2, 
 accountId: 2, instanceType: Template, instanceId: 205, cmd: 
 org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin, 
 cmdInfo: 
 {cmdEventType:TEMPLATE.CREATE,ctxUserId:2,ispublic:False,isextractable:False,httpmethod:GET,volumeid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,domainid:fe2a30b2-c5a8-11e3-8f55-66bc12ed7ec3,isfeatured:False,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,ostypeid:feba4b70-c5a8-11e3-8f55-66bc12ed7ec3,id:205,response:json,name:Cent
  OS Template-7WLKMH,passwordenabled:False,displaytext:Cent OS 
 Template,account:test-TestCreateTemplate-SCKX71,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,ctxAccountId:2,ctxStartEventId:291,signature:8ILr8Hdfhc35eHAm1D0L7lkgRw4\u003d},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:55:43,853 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b) ===START===  10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,877 WARN  [c.c.a.d.ParamGenericValidationWorker] 
 (API-Job-Executor-41:job-97 ctx-554395e3) Received unknown parameters for 
 command createTemplate. Unknown parameters : isextractable account
 2014-04-16 15:55:43,921 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-a6b8fe9b ctx-62916341 ctx-11cd890f) ===END===  
 10.223.240.161 -- GET  
 signature=vtGRmlHXmBNP%2F1rDkUstx%2BIMl4g%3DapiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=queryAsyncJobResultresponse=jsonjobid=51fab632-3d6f-4898-85e4-9597a8f39707
 2014-04-16 15:55:43,947 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
 (API-Job-Executor-41:job-97 ctx-554395e3) template 205 is already in store:1, 
 type:Image
 2014-04-16 15:55:43,972 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] 
 (API-Job-Executor-41:job-97 ctx-554395e3) copyAsync inspecting src type 
 VOLUME copyAsync inspecting dest type TEMPLATE
 2014-04-16 15:55:44,005 DEBUG [c.c.a.t.Request] (API-Job-Executor-41:job-97 
 ctx-554395e3) Seq 2-7234469851417280562: Sending  { Cmd , MgmtId: 
 112957957439171, via: 2(marron.lab.vmops.com), Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:58a0f1da-e5fe-4cf0-8981-8a8ce848662f,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ac0c4b04-6b72-38b1-a72f-c7fe7163d17a,id:1,poolType:NetworkFilesystem,host:nfs1-ccp.citrix.com,path:/home/common/automation/SC_QA_AUTO7/primary4,port:2049,url:NetworkFilesystem://nfs1-ccp.citrix.com/home/common/automation/SC_QA_AUTO7/primary4/?ROLE=PrimarySTOREUUID=ac0c4b04-6b72-38b1-a72f-c7fe7163d17a}},name:ROOT-17,size:21474836480,path:01269023-5389-407f-8dfc-a3ab22074207,volumeId:19,vmName:i-12-17-QA,accountId:12,format:VHD,id:19,deviceId:0,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/12/205,uuid:2575698c-c82c-4fc3-bd51-0993e40e81cb,id:205,format:RAW,accountId:12,hvm:true,displayText:Cent
  OS 
 

[jira] [Resolved] (CLOUDSTACK-6442) [Automation] Extraction of Volume failed due to the requested plugin could not be found.

2014-04-23 Thread Anthony Xu (JIRA)

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

Anthony Xu resolved CLOUDSTACK-6442.


Resolution: Fixed

commit 33c0d6c7bbb2e85f87935dee64dccbe2ee7f264c
Author: Anthony Xu anthony...@citrix.com
Date:   Wed Apr 23 15:30:36 2014 -0700

CLOUDSTACK-6438
CLOUDSTACK-6442
  XAPI plugins must be copied to XS master first.


 [Automation] Extraction of Volume failed due to the requested plugin could 
 not be found.
 

 Key: CLOUDSTACK-6442
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6442
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Management Server
Affects Versions: 4.4.0
 Environment: Basic Zone
 XenServer
Reporter: Chandan Purushothama
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log.2014-04-16.gz


 Use Case:
 Extract Volume from the Setup
 
 The requested plugin could not be found.
 
 2014-04-16 15:59:56,332 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669) ===START===  10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,335 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Processing Seq 4-314:  { Cmd , 
 MgmtId: -1, via: 4, Ver: v1, Flags: 11, 
 [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:1,_loadInfo:{\n
   \connections\: []\n},wait:0}}] }
 2014-04-16 15:59:56,343 DEBUG [c.c.a.m.AgentManagerImpl] 
 (AgentManager-Handler-20:null) SeqA 4-314: Sending Seq 4-314:  { Ans: , 
 MgmtId: 112957957439171, via: 4, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2014-04-16 15:59:56,369 DEBUG [c.c.u.AccountManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) Access to 
 {Vol[31|vm=null|DATADISK]} granted to 
 Acct[ed7cd506-e810-496f-94ee-3e422b3a6449-test-TestVolumes-test_01_create_volume-7K52C0]
  by RoleBasedEntityAccessChecker
 2014-04-16 15:59:56,388 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) submit async 
 job-169, details: AsyncJobVO {id:169, userId: 2, accountId: 2, instanceType: 
 Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,389 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-1:ctx-2bcdf669 ctx-da1872d1 ctx-20bb4a0a) ===END===  
 10.223.240.161 -- GET  
 apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732command=extractVolumemode=HTTP_DOWNLOADsignature=yuDaizmeEsZcaxZW0QEVOGL7YK0%3Did=b5521198-97f1-4f2c-afea-fcadf70d4249response=json
 2014-04-16 15:59:56,394 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
 (API-Job-Executor-76:job-169) Add job-169 into job monitoring
 2014-04-16 15:59:56,394 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
 (API-Job-Executor-76:job-169) Executing AsyncJobVO {id:169, userId: 2, 
 accountId: 2, instanceType: Volume, instanceId: 31, cmd: 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, cmdInfo: 
 {response:json,id:b5521198-97f1-4f2c-afea-fcadf70d4249,cmdEventType:VOLUME.EXTRACT,ctxUserId:2,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,httpmethod:GET,uuid:b5521198-97f1-4f2c-afea-fcadf70d4249,ctxAccountId:2,ctxStartEventId:441,apiKey:MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Q,signature:yuDaizmeEsZcaxZW0QEVOGL7YK0\u003d,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
 null, initMsid: 112957957439171, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2014-04-16 15:59:56,395 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-20:ctx-fecf5e4b) ===START===  

[jira] [Updated] (CLOUDSTACK-6486) Isolation network creation fails when isolationMethod is set in lower case for the corresponding physical network

2014-04-23 Thread Alena Prokharchyk (JIRA)

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

Alena Prokharchyk updated CLOUDSTACK-6486:
--

Priority: Major  (was: Blocker)
 Summary: Isolation network creation fails when isolationMethod is set in 
lower case for the corresponding physical network  (was: Failed to create more 
than one isolated network for the same account)

 Isolation network creation fails when isolationMethod is set in lower case 
 for the corresponding physical network
 -

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


 Steps to reproduce:
 ==
 1) login as root admin
 2) create first isolated network while deploying a vm, from deployVm dialog
 3) Try to create a second isolated network, either from the deploy vm dialog, 
 or from Networks tab. following error occurs:
 ERROR [c.c.a.ApiServer] (2128435204@qtp-415454110-20:ctx-fe01b290 
 ctx-c27f313c) unhandled exception executing api command: 
 [Ljava.lang.String;@33607ddc
 com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
 offering with specified id to network profile
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:691)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1940)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1901)
   at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createGuestNetwork(NetworkOrchestrator.java:1901)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1362)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1310)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at 
 com.cloud.network.NetworkServiceImpl.commitNetwork(NetworkServiceImpl.java:1310)
   at 
 com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1273)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at com.sun.proxy.$Proxy157.createGuestNetwork(Unknown Source)
   at 
 org.apache.cloudstack.api.command.admin.network.CreateNetworkCmdByAdmin.execute(CreateNetworkCmdByAdmin.java:57)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
   at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
   at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
   at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 

[jira] [Commented] (CLOUDSTACK-6486) Failed to create more than one isolated network for the same account

2014-04-23 Thread Alena Prokharchyk (JIRA)

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

Alena Prokharchyk commented on CLOUDSTACK-6486:
---

Found the reason for the failure. In GuestNetworkGuru when check if the guru 
supports isolation method of the physical network, the check is done in case 
sensitive manner. And if you create physical network with isolationMethod=vlan 
passed to the API in lower case, the comparison in Guru will fail as it tries 
to compare it with the uppercase VLAN value.

 Failed to create more than one isolated network for the same account
 

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


 Steps to reproduce:
 ==
 1) login as root admin
 2) create first isolated network while deploying a vm, from deployVm dialog
 3) Try to create a second isolated network, either from the deploy vm dialog, 
 or from Networks tab. following error occurs:
 ERROR [c.c.a.ApiServer] (2128435204@qtp-415454110-20:ctx-fe01b290 
 ctx-c27f313c) unhandled exception executing api command: 
 [Ljava.lang.String;@33607ddc
 com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
 offering with specified id to network profile
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:691)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1940)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1901)
   at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createGuestNetwork(NetworkOrchestrator.java:1901)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1362)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1310)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at 
 com.cloud.network.NetworkServiceImpl.commitNetwork(NetworkServiceImpl.java:1310)
   at 
 com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1273)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at com.sun.proxy.$Proxy157.createGuestNetwork(Unknown Source)
   at 
 org.apache.cloudstack.api.command.admin.network.CreateNetworkCmdByAdmin.execute(CreateNetworkCmdByAdmin.java:57)
   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
   at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
   at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
   at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
   at 
 

[jira] [Commented] (CLOUDSTACK-6486) Isolation network creation fails when isolationMethod is set in lower case for the corresponding physical network

2014-04-23 Thread Alena Prokharchyk (JIRA)

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

Alena Prokharchyk commented on CLOUDSTACK-6486:
---

Steps to reproduce:

1) Create the zone
2) Add physical network to the zone with the API:

http://localhost:8096/?command=createPhysicalNetworkzoneId=1name=alenaisolationmethods=vlan

make sure vlan is passed in lower case

3) Try to create an isolated network. It will fail as this part of the code in 
GuestNetworkGuru does isolation methods comparison in case sensitive manner:

 ListString methods = physicalNetwork.getIsolationMethods();
if (methods.isEmpty()) {
// The empty isolation method is assumed to be VLAN
s_logger.debug(Empty physical isolation type for physical network 
 + physicalNetwork.getUuid());
methods = new ArrayListString(1);
methods.add(VLAN);
}

for (IsolationMethod m : _isolationMethods) {
if (methods.contains(m.toString())) {
return true;
}
}


 Isolation network creation fails when isolationMethod is set in lower case 
 for the corresponding physical network
 -

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


 Steps to reproduce:
 ==
 1) login as root admin
 2) Try to create an isolated network, either from the deploy vm dialog, or 
 from Networks tab. following error occurs:
 ERROR [c.c.a.ApiServer] (2128435204@qtp-415454110-20:ctx-fe01b290 
 ctx-c27f313c) unhandled exception executing api command: 
 [Ljava.lang.String;@33607ddc
 com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
 offering with specified id to network profile
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:691)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1940)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1901)
   at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
   at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createGuestNetwork(NetworkOrchestrator.java:1901)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1362)
   at 
 com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1310)
   at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
   at 
 com.cloud.network.NetworkServiceImpl.commitNetwork(NetworkServiceImpl.java:1310)
   at 
 com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1273)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
   at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
   at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
   at com.sun.proxy.$Proxy157.createGuestNetwork(Unknown Source)
   at 
 

[jira] [Updated] (CLOUDSTACK-6486) Isolation network creation fails when isolationMethod is set in lower case for the corresponding physical network

2014-04-23 Thread Alena Prokharchyk (JIRA)

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

Alena Prokharchyk updated CLOUDSTACK-6486:
--

Description: 
Steps to reproduce:
==
1) login as root admin
2) Try to create an isolated network, either from the deploy vm dialog, or from 
Networks tab. following error occurs:

ERROR [c.c.a.ApiServer] (2128435204@qtp-415454110-20:ctx-fe01b290 ctx-c27f313c) 
unhandled exception executing api command: [Ljava.lang.String;@33607ddc
com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
offering with specified id to network profile
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:691)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1940)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$8.doInTransaction(NetworkOrchestrator.java:1901)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createGuestNetwork(NetworkOrchestrator.java:1901)
at 
com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1362)
at 
com.cloud.network.NetworkServiceImpl$4.doInTransaction(NetworkServiceImpl.java:1310)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at 
com.cloud.network.NetworkServiceImpl.commitNetwork(NetworkServiceImpl.java:1310)
at 
com.cloud.network.NetworkServiceImpl.createGuestNetwork(NetworkServiceImpl.java:1273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy157.createGuestNetwork(Unknown Source)
at 
org.apache.cloudstack.api.command.admin.network.CreateNetworkCmdByAdmin.execute(CreateNetworkCmdByAdmin.java:57)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:134)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:593)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416)
at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330)
at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54)
at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at 

[jira] [Commented] (CLOUDSTACK-6202) Support signature version 3 in Cloudmonkey

2014-04-23 Thread Chiradeep Vittal (JIRA)

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

Chiradeep Vittal commented on CLOUDSTACK-6202:
--

SignatureVersion=3 has been supported since 2011-08-10

 Support signature version 3 in Cloudmonkey
 --

 Key: CLOUDSTACK-6202
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6202
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Cloudmonkey
Reporter: Chiradeep Vittal
Assignee: Yichi Lu

 Cloudstack has signatureVersion=3 which supports an 'expires' timestamp. This 
 enhances security by making replay attacks less likely.



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


[jira] [Created] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread Jessica Wang (JIRA)
Jessica Wang created CLOUDSTACK-6487:


 Summary: UI  Add LDAP Account dialog  LDAP users listing - fails 
to show all LDAP users when one of them does not have email.
 Key: CLOUDSTACK-6487
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6487
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang






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


[jira] [Commented] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang commented on CLOUDSTACK-6487:
--

http://bugs-ccp.citrix.com/browse/CS-19795

 UI  Add LDAP Account dialog  LDAP users listing - fails to show all LDAP 
 users when one of them does not have email.
 --

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





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


[jira] [Commented] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6487: UI  Add LDAP Account - fix a bug that a LDAP account that 
does not have email and all LDAP accounts below it are missing from the listing.


 UI  Add LDAP Account dialog  LDAP users listing - fails to show all LDAP 
 users when one of them does not have email.
 --

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





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


[jira] [Commented] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang commented on CLOUDSTACK-6487:
--

commit 953167808c3e9a9c40a6f7be6e16ebf32c608a4c
Author: Jessica Wang jessicaw...@apache.org
Date:   Wed Apr 23 16:27:44 2014 -0700

BUG-ID: CS-19795: UI  Add LDAP Account - fix a bug that a LDAP account that
Reviewed-by: Brian

branch: 4.4-forward

 UI  Add LDAP Account dialog  LDAP users listing - fails to show all LDAP 
 users when one of them does not have email.
 --

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





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


[jira] [Closed] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang closed CLOUDSTACK-6487.



 UI  Add LDAP Account dialog  LDAP users listing - fails to show all LDAP 
 users when one of them does not have email.
 --

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





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


[jira] [Resolved] (CLOUDSTACK-6487) UI Add LDAP Account dialog LDAP users listing - fails to show all LDAP users when one of them does not have email.

2014-04-23 Thread Jessica Wang (JIRA)

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

Jessica Wang resolved CLOUDSTACK-6487.
--

Resolution: Fixed

 UI  Add LDAP Account dialog  LDAP users listing - fails to show all LDAP 
 users when one of them does not have email.
 --

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





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


[jira] [Created] (CLOUDSTACK-6488) VMware path field not set properly in DB in snapshot state

2014-04-23 Thread Mike Tutkowski (JIRA)
Mike Tutkowski created CLOUDSTACK-6488:
--

 Summary: VMware path field not set properly in DB in snapshot 
state
 Key: CLOUDSTACK-6488
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: VMware
Affects Versions: 4.4.0
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


From an e-mail I sent to the CS e-mail list:

I was testing VMware snapshots with managed storage and believe I see a problem 
with these snapshots with non-managed storage (I was comparing results from 
managed storage to non-managed storage).

If I take a VMware snapshot, I notice the path field in the volumes table 
references, say, the ROOT-9 VMDK instead of the ROOT-9-01 VMDK.

This seems like a bug.

If I look in vSphere Client, I see that the VM is using ROOT-9-01.vmdk.



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


[jira] [Commented] (CLOUDSTACK-6488) VMware path field not set properly in DB in snapshot state

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

Commit 54c0df56dc03d20ef1d9804d8695c3f6584470f8 in cloudstack's branch 
refs/heads/4.4-forward from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=54c0df5 ]

CLOUDSTACK-6488 Fixed an issue where the path field was not being set 
properly in the DB when the volume had a snapshot taken of it


 VMware path field not set properly in DB in snapshot state
 

 Key: CLOUDSTACK-6488
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 From an e-mail I sent to the CS e-mail list:
 I was testing VMware snapshots with managed storage and believe I see a 
 problem with these snapshots with non-managed storage (I was comparing 
 results from managed storage to non-managed storage).
 If I take a VMware snapshot, I notice the path field in the volumes table 
 references, say, the ROOT-9 VMDK instead of the ROOT-9-01 VMDK.
 This seems like a bug.
 If I look in vSphere Client, I see that the VM is using ROOT-9-01.vmdk.



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


[jira] [Commented] (CLOUDSTACK-6488) VMware path field not set properly in DB in snapshot state

2014-04-23 Thread ASF subversion and git services (JIRA)

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

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

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

CLOUDSTACK-6488 Fixed an issue where the path field was not being set 
properly in the DB when the volume had a snapshot taken of it


 VMware path field not set properly in DB in snapshot state
 

 Key: CLOUDSTACK-6488
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 From an e-mail I sent to the CS e-mail list:
 I was testing VMware snapshots with managed storage and believe I see a 
 problem with these snapshots with non-managed storage (I was comparing 
 results from managed storage to non-managed storage).
 If I take a VMware snapshot, I notice the path field in the volumes table 
 references, say, the ROOT-9 VMDK instead of the ROOT-9-01 VMDK.
 This seems like a bug.
 If I look in vSphere Client, I see that the VM is using ROOT-9-01.vmdk.



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


[jira] [Resolved] (CLOUDSTACK-6488) VMware path field not set properly in DB in snapshot state

2014-04-23 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski resolved CLOUDSTACK-6488.


Resolution: Fixed

 VMware path field not set properly in DB in snapshot state
 

 Key: CLOUDSTACK-6488
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 From an e-mail I sent to the CS e-mail list:
 I was testing VMware snapshots with managed storage and believe I see a 
 problem with these snapshots with non-managed storage (I was comparing 
 results from managed storage to non-managed storage).
 If I take a VMware snapshot, I notice the path field in the volumes table 
 references, say, the ROOT-9 VMDK instead of the ROOT-9-01 VMDK.
 This seems like a bug.
 If I look in vSphere Client, I see that the VM is using ROOT-9-01.vmdk.



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


[jira] [Closed] (CLOUDSTACK-6488) VMware path field not set properly in DB in snapshot state

2014-04-23 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski closed CLOUDSTACK-6488.
--


 VMware path field not set properly in DB in snapshot state
 

 Key: CLOUDSTACK-6488
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6488
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.4.0
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Assignee: Mike Tutkowski
 Fix For: 4.4.0


 From an e-mail I sent to the CS e-mail list:
 I was testing VMware snapshots with managed storage and believe I see a 
 problem with these snapshots with non-managed storage (I was comparing 
 results from managed storage to non-managed storage).
 If I take a VMware snapshot, I notice the path field in the volumes table 
 references, say, the ROOT-9 VMDK instead of the ROOT-9-01 VMDK.
 This seems like a bug.
 If I look in vSphere Client, I see that the VM is using ROOT-9-01.vmdk.



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


[jira] [Updated] (CLOUDSTACK-6475) [Automation] communication between cloudstack agent and MS disconnecting continuously

2014-04-23 Thread Ram Ganesh (JIRA)

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

Ram Ganesh updated CLOUDSTACK-6475:
---

Assignee: Kishan Kavala

 [Automation] communication between cloudstack agent and MS disconnecting 
 continuously  
 ---

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

 Attachments: Agent_log.rar, management-server.rar


 This issue is observed during automation, run.
 communication between cloudstack agent and ms getting disconnected 
 continuously;  observed below error in agent log
  2014-04-22 04:08:47,867 INFO  [cloud.agent.Agent] (AgentShutdownThread:null) 
 Stopping the agent: Reason = sig.kill
 2014-04-22 04:10:41,456 INFO  [cloud.agent.AgentShell] (main:null) Agent 
 started
 2014-04-22 04:10:41,500 INFO  [cloud.agent.AgentShell] (main:null) 
 Implementation Version is 4.4.0-SNAPSHOT
 2014-04-22 04:10:41,502 INFO  [cloud.agent.AgentShell] (main:null) 
 agent.properties found at /etc/cloudstack/agent/agent.properties
 2014-04-22 04:10:41,551 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to using properties file for storage
 2014-04-22 04:10:41,552 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
 to the constant time backoff algorithm
 2014-04-22 04:10:41,572 INFO  [cloud.utils.LogUtils] (main:null) log4j 
 configuration found at /etc/cloudstack/agent/log4j-cloud.xml
 2014-04-22 04:10:41,722 INFO  [cloud.agent.Agent] (main:null) id is 0
 2014-04-22 04:10:42,501 INFO  [kvm.resource.LibvirtComputingResource] 
 (main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
 2014-04-22 04:10:42,590 INFO  [cloud.agent.Agent] (main:null) Agent [id = 0 : 
 type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 
 10.223.49.195 : port = 8250
 2014-04-22 04:10:42,664 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connecting to 10.223.49.195:8250
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 SSL: Handshake done
 2014-04-22 04:10:42,920 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
 Connected to 10.223.49.195:8250
 2014-04-22 04:10:42,941 WARN  [kvm.resource.LibvirtComputingResource] 
 (Agent-Handler-1:null) Could not read cpuinfo_max_freq
 2014-04-22 04:10:43,158 INFO  [cloud.serializer.GsonHelper] 
 (Agent-Handler-1:null) Default Builder inited.
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Proccess agent startup answer, agent id = 0
 2014-04-22 04:10:43,227 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) Set 
 agent id 0
 2014-04-22 04:10:43,233 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
 Startup Response Received: agent id = 0
 2014-04-22 04:11:40,925 INFO  [cloud.agent.Agent] (Agent-Handler-1:null) Lost 
 connection to the server. Dealing with the remaining commands...
 2014-04-22 04:11:42,352 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 0
 2014-04-22 04:11:42,368 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 1
 2014-04-22 04:11:42,383 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 2
 2014-04-22 04:11:42,398 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 3
 2014-04-22 04:11:42,413 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error, retry: 4
 2014-04-22 04:11:42,414 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: Input/output error; reboot the host
 2014-04-22 04:11:42,472 WARN  [kvm.resource.KVMHAMonitor] (Thread-4:null) 
 write heartbeat failed: 
 /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 
 131: echo: write error: 

[jira] [Commented] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.

2014-04-23 Thread manasaveloori (JIRA)

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

manasaveloori commented on CLOUDSTACK-6481:
---

http://nfs1.lab.vmops.com/templates/Goleta_qa/open_ssl_64bit/systemvm64template-master-xen.vhd.bz2
 is used
vhd-util is already installed under 
/usr/share/cloudstack-common/scripts/util/vhd-util as a part of management 
server package installation

 Vhd-util is not copied to xenserver from MS...As a result system VMs fail to 
 start in CS.
 -

 Key: CLOUDSTACK-6481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, XenServer
Affects Versions: 4.4.0
 Environment: Xenserver6.2 added to CS 4.4
Reporter: manasaveloori
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.log


 PXE booted the Xenserver.
 Added it to CS 4.4.
 observed that system vms fails to deploy with Exception:
 2014-04-23 04:23:46,875 WARN  [c.c.h.x.r.XenServerStorageProcessor] 
 (DirectAgent-3:ctx-cf6a380b) Catch Exception 
 com.cloud.utils.exception.CloudRuntimeException for template +  due to 
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 
 5cffabad-fb53-27ad-96eb-a1728623dd7c
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846)
 at 
 com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77)
 at 
 com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received:
 Checked in xenserver the vhd-util file is missing under /opt/cloud/bin.
 As work around copied the vhd-util to /opt/cloud/bin.
 Attaching the log files



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


[jira] [Created] (CLOUDSTACK-6489) The latest changes in the marvin break the bug logger integration.

2014-04-23 Thread Bharat kumar (JIRA)
Bharat kumar created CLOUDSTACK-6489:


 Summary: The latest changes in the marvin break the bug logger 
integration.
 Key: CLOUDSTACK-6489
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6489
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.5.0
Reporter: Bharat kumar


The present bug logger integration breaks because of the following.

1.) if a test fails logs are not generated with the name of the test suite. it  
places the logs in the test_suite_*  folder. as result of this we do not know 
to which test suite these logs belong to. 

2.)The new changes in the marvin framework change the directory structure of 
the  logs, this breaks the current implementation of collecting the results.






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


[jira] [Created] (CLOUDSTACK-6490) Integrate the code coverage with the new automation infra.

2014-04-23 Thread Bharat kumar (JIRA)
Bharat kumar created CLOUDSTACK-6490:


 Summary: Integrate the code coverage with the new automation infra.
 Key: CLOUDSTACK-6490
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6490
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Reporter: Bharat kumar






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


[jira] [Created] (CLOUDSTACK-6491) add support for vmware in the new automation infra.

2014-04-23 Thread Bharat kumar (JIRA)
Bharat kumar created CLOUDSTACK-6491:


 Summary: add support for vmware in the new automation infra.
 Key: CLOUDSTACK-6491
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6491
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Reporter: Bharat kumar






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


[jira] [Commented] (CLOUDSTACK-6482) [API-LoadBalancing]Passing invalid vm name and vmip to assignToLoadBalancerRule API is not giving proper error message in response.

2014-04-23 Thread manasaveloori (JIRA)

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

manasaveloori commented on CLOUDSTACK-6482:
---

proper error message is not displayed if already assigned ip is passed in 
vmidipmap using API.

 [API-LoadBalancing]Passing invalid vm name and vmip to 
 assignToLoadBalancerRule API is not giving proper error message in response.
 ---

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


 1. Configure the LB rule.
 2. Assign a VM to the LB rule by providing invalid VM name or invalid VMid.
 API:
 http://10.147.59.222:8096/client/api?command=assignToLoadBalancerRuleid=3vmidipmap[0].vmid=e59de8ab-7ed5-4432-8838-ac600323ddvmidipmap[0].vmip=10.1.1.247
  
 Response:
 assigntoloadbalancerruleresponse cloud-stack-version=4.4.0-SNAPSHOT
 jobid683e99a1-8ce2-47be-93f6-a11e18685910/jobid
 /assigntoloadbalancerruleresponse
 Observation:
 API does not proper error message to user.
 In MS logs able to proper message:
 com.cloud.exception.InvalidParameterValueException: Invalid ip address 
 10.1.1..9 passed in vmidipmap for vmid e59de8ab-7ed5-4432-8838-ac64600323dd



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


[jira] [Updated] (CLOUDSTACK-5910) mark the LDAP user as imported from LDAP

2014-04-23 Thread Rajani Karuturi (JIRA)

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

Rajani Karuturi updated CLOUDSTACK-5910:


Status: Reviewable  (was: In Progress)

 mark the LDAP user as imported from LDAP
 

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


 currently once the ldap users are imported, there is no way to differentiate 
 between LDAP users and native cloudstack users. 
 There should be a way to differentiate these users so that the authentication 
 can differentiate between native and ldap users and only use the 
 corresponding authentication mechanism. 



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