You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/07/08 08:45:49 UTC

[jira] [Commented] (CLOUDSTACK-3259) integration.component.test_routers test cases failed with ssh connection error

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

Rayees Namathponnan commented on CLOUDSTACK-3259:
-------------------------------------------------

3) test_routers.TestRouterStopCreatePF.test_01_RouterStopCreatePF; failed with below error 

SSH Access failed for 10.1.1.76: [Errno 113] No route to host
-------------------- >> begin captured logging << --------------------
testclient.testcase.TestRouterStopCreatePF: DEBUG: Stopping router ID: 57e6c9be-7deb-4020-be3e-6d2ec8e04ba6
testclient.testcase.TestRouterStopCreatePF: DEBUG: Creating NAT rule for VM ID: c509eb0f-ec83-44ec-b167-ba680eea33cd
testclient.testcase.TestRouterStopCreatePF: DEBUG: Starting router ID: 57e6c9be-7deb-4020-be3e-6d2ec8e04ba6
testclient.testcase.TestRouterStopCreatePF: DEBUG: SSH into VM with ID: 10.223.243.23
                
> integration.component.test_routers test cases failed with ssh connection error 
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3259
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3259
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.2.0
>         Environment: Automation : Vmware
>            Reporter: Rayees Namathponnan
>             Fix For: 4.2.0
>
>
> Test cases failed with ssh connection error in vmware 
> integration.component.test_routers

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira