[
https://issues.apache.org/jira/browse/CLOUDSTACK-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715547#comment-13715547
]
Rayees Namathponnan commented on CLOUDSTACK-3168:
-------------------------------------------------
Test integration.smoke.test_network.TestRebootRouter.test_reboot_router still
fails in VMware
SSH Access failed for 10.1.1.36: [Errno 113] No route to host
-------------------- >> begin captured logging << --------------------
testclient.testcase.TestRebootRouter: DEBUG: Rebooting the router (ID:
b3082088-d3de-44e5-92fe-f3a9b0ffee3d)
testclient.testcase.TestRebootRouter: DEBUG: VM state: Running
testclient.testcase.TestRebootRouter: DEBUG: SSH into VM (ID :
59ecbab0-2c2f-49d4-acc4-f3bdb90d09e5 ) after reboot
--------------------- >> end captured logging << ---------------------
Stacktrace
File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
testMethod()
File "/data/Repo2/qa/cloudstack/test/integration/smoke/test_network.py", line
743, in test_reboot_router
(self.vm_1.ipaddress, e))
File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
raise self.failureException(msg)
SSH Access failed for 10.1.1.36: [Errno 113] No route to host
> [Automation] BVT - Network test cases failed with ssh connection error
> -----------------------------------------------------------------------
>
> Key: CLOUDSTACK-3168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3168
> 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 env
> Reporter: Rayees Namathponnan
> Assignee: Girish Shilamkar
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Below two tets cases failing with ssh connection error
> smoke.test_network.TestLoadBalancingRule.test_02_create_lb_rule_non_nat
> test_network.TestPortForwarding.test_02_port_fwd_on_non_src_nat
--
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
