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

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

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

CLOUDSTACK-7393: Expunging VM immediately and removing unncessary wait in 
test_vpc_vm_life_cycle.py

Signed-off-by: SrikanteswaraRao Talluri <[email protected]>


> [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)

Reply via email to