You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by gauravaradhye <gi...@git.apache.org> on 2015/03/25 07:19:25 UTC
[GitHub] cloudstack pull request: CLOUDSTACK-8344: Fixed SSH failures in te...
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 <ga...@clogeny.com>
Date: 2015-03-25T05:31:58Z
CLOUDSTACK-8344: Fixed SSH failures in test_haproxy.py test suite
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: CLOUDSTACK-8344: Fixed SSH failures in te...
Posted by srikanteswartalluri <gi...@git.apache.org>.
Github user srikanteswartalluri commented on the pull request:
https://github.com/apache/cloudstack/pull/130#issuecomment-87555204
Good catch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: CLOUDSTACK-8344: Fixed SSH failures in te...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/130
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---