You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Gaurav Aradhye (JIRA)" <ji...@apache.org> on 2014/09/05 07:57:34 UTC

[jira] [Commented] (CLOUDSTACK-7393) [Automation] Fix the script "test_vpc_vm_life_cycle.py" - Code is hardcoded to use certain host tags

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

Gaurav Aradhye commented on CLOUDSTACK-7393:
--------------------------------------------

Identified the issue, fixed it, testing in progress.

> [Automation] Fix the script "test_vpc_vm_life_cycle.py" - Code is hardcoded to use certain host tags
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7393
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7393
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Test
>    Affects Versions: 4.5.0
>            Reporter: Chandan Purushothama
>            Assignee: Gaurav Aradhye
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> *Script is present at:*
> component/test_vpc_vm_life_cycle.py
> Currently script assumes that the deployment has hosts with host_tags "host1" and "host2" and uses two service offerings with these host_tags. The script is hardcoded with the above information. The proper design and correction should be as follows.
>     Find the cluster with two hosts
>         If no two host cluster is found error out with proper message
>     Edit the host tags on the two hosts to two different unique names
>     Create corresponding service offerings with the two different unique names
>     Conduct the tests
>     In teardown script section of the script, edit the host tags on the hosts to empty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)