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

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

Github user borisroman commented on the pull request:

    https://github.com/apache/cloudstack/pull/923#issuecomment-147841813
  
    @remibergsma @karuturi @wilderrodrigues @DaanHoogland I tested this PR 
today. Tests ran fine except for the cleanups (which are known by 
CLOUDSTACK-8935). I'll spare the space of this comment as all test results 
already have been posted twice by Wilder and Remi. I also ran the 
test_loadbalance.py which turned out positive.
    
    Test to create Load balancing rule with source NAT ... === TestName: 
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
    ok
    Test to create Load balancing rule with non source NAT ... === TestName: 
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
    ok
    Test for assign & removing load balancing rule ... === TestName: 
test_assign_and_removal_lb | Status : SUCCESS ===
    ok
    
    ----------------------------------------------------------------------
    Ran 3 tests in 633.239s
    
    OK
    /tmp//MarvinLogs/test_loadbalance_HD34OP/results.txt 
    
    Code (style) changes look good to me.
    
    To conclude: LGTM :+1: 


> Default routes not configured for rVPC and RVR
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-8934
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8934
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.6.0
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>            Priority: Blocker
>             Fix For: 4.6.0
>
>
> User VMs cannot reach the outside world due to missing default routes in 
> Redundant VPCs and Redundant Isolated Networks.
> In order to work it around I had to:
> route add default gw 192.168.23.1



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

Reply via email to