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

Prasanna Santhanam resolved CLOUDSTACK-567.
-------------------------------------------

    Resolution: Fixed

commit 4b539ddcb3e37810757e74b2a6060ec6f4776e07
Author: Talluri <srikanteswararao.tall...@citrix.com>
Date:   Thu Nov 29 14:27:42 2012 +0530

    Summary: Fixes marvin integration test for copy template/iso between zones
    
    Detail:
    This is a fix
    1. to populate 'destzoneid' as part of the test data by issuing
    listZones API. Earlier, this is provided manually in the test data.
    2. to  wait till the ISO/template is downloaded & installed successfully
    before being deleted as part of the cleanup.
    
    BUG-ID: CLOUDSTACK-567
    Reviewed-by: Prasanna Santhanam
    Reported-by: Prasanna Santhanam
    Signed-off-by: Prasanna Santhanam <t...@apache.org> 1354234426 -0800

                
> Integration Test: Test for Copy Zone has hardcoded destination id
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-567
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-567
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Test
>    Affects Versions: 4.0.0
>            Reporter: Prasanna Santhanam
>            Assignee: Prasanna Santhanam
>
> The smoke and integration tests for copying image (template/iso) between 
> zones assumes the destination id is always 2 which is incorrect since all 
> entities are now based on uuid. Furthermore the listTemplates response needs 
> to resolve the template to be in READY state to ensure that the image was 
> copied over successfully.
> Here's the review request that corrects this:
> https://reviews.apache.org/r/8082/

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

Reply via email to