cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8344) Fix SSH failures in test_haproxy.py test cases
Date Wed, 25 Mar 2015 06:19:54 GMT

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

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

GitHub user gauravaradhye opened a pull request:

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

    CLOUDSTACK-8344: Fixed SSH failures in test_haproxy.py test suite

    The test case in test suite test_haproxy.py are failing while attempting SSH due to Authentication
error.
    The test cases are using host credentials while trying to connect to user VM. Instead
they should use VM username and password.
    
    Tested on KVM setup.
    
    Logs:
    Test Configure stickiness policies with default values ... === TestName: test_01_create_sticky_policy_default_values
|
    Status : SUCCESS ===
    ok
    Test Configure stickiness policies with custom values ... === TestName: test_02_create_sticky_policy_custom_values
|
    Status : SUCCESS ===
    ok
    Test listnetworks response to check supported stickiness policies ... === TestName: test_03_supported_policies_by_network
    | Status : SUCCESS ===
    ok
    Test LB rule before/after stickiness policy creation ... === TestName: test_04_delete_lb_rule
| Status : SUCCESS ===
    ok
    Test error/alerts after creating stickiness policy ... === TestName: test_05_error_alerts_after_create
| Status : SUCCESS
    ===
    ok
    Test release public IP with stickiness policy ... === TestName: test_06_release_ip | Status
: SUCCESS ===
    ok
    Test Delete account  and check the router and its rules ... === TestName: test_07_delete_account
| Status : SUCCESS ===
    ok
    Test verify create stickiness policy when router is stopped state ... === TestName: test_08_create_policy_router_stopped
|
    Status : SUCCESS ===
    ok
    Test check the stickiness policy rules after destroying router ... === TestName: test_09_create_policy_router_destroy
|
    Status : SUCCESS ===
    ok
    Test enable/disable the VPN after applying sticky policy rules ... === TestName: test_10_create_policy_enable_disable_vpn
    | Status : SUCCESS ===
    ok
    Test verfify functionality syncronous and asyncronous validations ... === TestName: test_11_invalid_params
| Status :
    SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 11 tests in 3936.193s
    
    OK

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

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

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

    https://github.com/apache/cloudstack/pull/130.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 #130
    
----
commit 074ecbd9ce802af337e2c093e528c44dd14b6d67
Author: Gaurav Aradhye <gaurav.aradhye@clogeny.com>
Date:   2015-03-25T05:31:58Z

    CLOUDSTACK-8344: Fixed SSH failures in test_haproxy.py test suite

----


> Fix SSH failures in test_haproxy.py test cases
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-8344
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8344
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: Future
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: Future
>
>
> The test case in test suite test_haproxy.py are failing while attempting SSH due to Authentication
error.
> The test cases are using host credentials while trying to connect to user VM. Instead
they should use VM username and password.



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

Mime
View raw message