[ https://issues.apache.org/jira/browse/CLOUDSTACK-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723505#comment-13723505 ]
Girish Shilamkar edited comment on CLOUDSTACK-3168 at 7/30/13 7:27 AM: ----------------------------------------------------------------------- Patch: https://reviews.apache.org/r/13056/ After fixing the testcase I uncovered a defect. The vm cannot be ssh after router is reboot, so the pf rules no longer apply once router is rebooted. Without router being rebooted (commented out reboot router API call): Test for Associate/Disassociate public IP address for user account ... skipped 'Skip' test_reboot_router (test_net.TestRebootRouter) Test for reboot router ... ok test_releaseIP (test_net.TestReleaseIP) Test for release public IP address ... skipped 'Skip' ---------------------------------------------------------------------- Ran 7 tests in 259.316s OK (skipped=6) Router rebooted: test_reboot_router (test_net.TestRebootRouter) Test for reboot router ... FAIL test_releaseIP (test_net.TestReleaseIP) Test for release public IP address ... skipped 'Skip' ====================================================================== FAIL: test_reboot_router (test_net.TestRebootRouter) Test for reboot router ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/girish/test_net.py", line 752, in test_reboot_router (self.public_ip.ipaddress.ipaddress, e)) AssertionError: SSH Access failed for 10.223.243.23: [Errno 113] No route to host ---------------------------------------------------------------------- Ran 7 tests in 356.064s Note: This is seen for vmware as of now. was (Author: gpshilamkar): Patch: https://reviews.apache.org/r/13056/ After fixing the testcase I uncovered a defect. The vm cannot be ssh after router is reboot, so the pf rules no longer apply once router is rebooted. Without router being rebooted (commented out reboot router API call): Test for Associate/Disassociate public IP address for user account ... skipped 'Skip' test_reboot_router (test_net.TestRebootRouter) Test for reboot router ... ok test_releaseIP (test_net.TestReleaseIP) Test for release public IP address ... skipped 'Skip' ---------------------------------------------------------------------- Ran 7 tests in 259.316s OK (skipped=6) Router rebooted: test_reboot_router (test_net.TestRebootRouter) Test for reboot router ... FAIL test_releaseIP (test_net.TestReleaseIP) Test for release public IP address ... skipped 'Skip' ====================================================================== FAIL: test_reboot_router (test_net.TestRebootRouter) Test for reboot router ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/girish/test_net.py", line 752, in test_reboot_router (self.public_ip.ipaddress.ipaddress, e)) AssertionError: SSH Access failed for 10.223.243.23: [Errno 113] No route to host ---------------------------------------------------------------------- Ran 7 tests in 356.064s > [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