[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread murali-reddy
Github user murali-reddy commented on the issue: https://github.com/apache/cloudstack/pull/1929 LGTM. thanks @ustcweizhou --- 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

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread blueorangutan
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1929 Trillian test result (tid-802) Environment: vmware-60u2 (x2), Advanced Networking with Mgmt server 7 Total time taken: 43855 seconds Marvin logs:

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread blueorangutan
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1929 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-60u2) has been kicked to run smoke tests --- If your project is set up for it, you can reply to this email and have your

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread borisstoyanov
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1929 @blueorangutan test centos7 vmware-60u2 --- 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

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread blueorangutan
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1929 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-471 --- 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

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread blueorangutan
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1929 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-05 Thread borisstoyanov
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1929 @blueorangutan package --- 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

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace
Github user milamberspace commented on the issue: https://github.com/apache/cloudstack/pull/1929 LGTM tested in real conditions with success --- 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

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace
Github user milamberspace commented on the issue: https://github.com/apache/cloudstack/pull/1929 @DaanHoogland Yes I've already tested with success the patch. Please see Jira https://issues.apache.org/jira/browse/CLOUDSTACK-9770 The PR by @ustcweizhou is

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread milamberspace
Github user milamberspace commented on the issue: https://github.com/apache/cloudstack/pull/1929 @DaanHoogland Yes I've already tested with success the patch. Please see Jira --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] cloudstack issue #1929: CLOUDSTACK-9770: fix missing ip routes in VR

2017-02-03 Thread DaanHoogland
Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/1929 @milamberspace could you try with this patch? I think @ustcweizhou solved your problem with the default route --- If your project is set up for it, you can reply to this email and have