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

Gaurav Aradhye commented on CLOUDSTACK-6550:
--------------------------------------------

I looked at the logs of first 3 failures

integration.component.test_accounts.TestTemplateHierarchy.test_01_template_hierarch
integration.component.test_cpu_project_limits.TestProjectsCPULimits.test_01_project_counts_start_stop_instance
integration.component.test_mm_project_limits.TestProjectsMemoryLimits.test_01_project_vmlifecycle_start_stop_instance

 and the issue does not seem about the listall parameter. The listall parameter 
is sent as True in each case as seen in the logs. Also I ran the test case 
test_01_template_hierarchy locally and it ran without failure.

I will debug more tomorrow to find out the root cause.

> [Automation] list**** API return empty list if you are not passing 
> listall=true, many testcases failed due to this
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6550
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6550
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API, Virtual Router
>    Affects Versions: 4.4.0
>         Environment: Xen 6.2
> build : 4.4-forward 
>            Reporter: Rayees Namathponnan
>            Assignee: Santhosh Kumar Edukulla
>            Priority: Blocker
>             Fix For: 4.4.0
>
>
> Currently test cases are using below command to listrouter (without 
> listall=true),  
> passing accountID and domain ID
>  
> http://10.147.38.149:8096/?account=test-TestReleaseIP-test_releaseIP-8W58N0&domainid=22feae40-d076-11e3-8dca-06080800001f&command=listRouters
>  
> this API call return empty list in 4.4,  



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

Reply via email to