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

ASF GitHub Bot commented on CLOUDSTACK-8518:
--------------------------------------------

GitHub user gauravaradhye opened a pull request:

    https://github.com/apache/cloudstack/pull/319

    CLOUDSTACK-8518: Fix issues in testpath_disable_enable_zone.py

    Changes:
    1. Skip snapshot test cases for hyperv and LXC hypervisors
    2. Include enable host script in tearDownClass so that in case test fails, 
hosts are not left in disabled state

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gauravaradhye/cloudstack 8518

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/319.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #319
    
----
commit ee39765a17bb658eca499d238775a721db163c64
Author: Gaurav Aradhye <[email protected]>
Date:   2015-05-27T12:55:18Z

    CLOUDSTACK-8518: Fix issues in testpath_disable_enable_zone.py

----


> Fix testpath_disable_enable_zone.py test suite
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-8518
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8518
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation
>    Affects Versions: 4.6.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.6.0
>
>
> Changes:
> 1. Skip snapshot test cases for hyperv and LXC hypervisors
> 2. Include enable host script in tearDownClass so that in case test fails, 
> hosts are not left in disabled state



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

Reply via email to