Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CB1B8200BBE for ; Fri, 11 Nov 2016 11:17:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C9DDA160AF5; Fri, 11 Nov 2016 10:17:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15FC1160AE4 for ; Fri, 11 Nov 2016 11:17:51 +0100 (CET) Received: (qmail 96602 invoked by uid 500); 11 Nov 2016 10:17:46 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 96577 invoked by uid 99); 11 Nov 2016 10:17:45 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2016 10:17:45 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 5D544E09B6; Fri, 11 Nov 2016 10:17:45 +0000 (UTC) From: SudharmaJain To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1736: CLOUDSTACK-9562 Linux Guest VM get wrong default rou... Content-Type: text/plain Message-Id: <20161111101745.5D544E09B6@git1-us-west.apache.org> Date: Fri, 11 Nov 2016 10:17:45 +0000 (UTC) archived-at: Fri, 11 Nov 2016 10:17:53 -0000 Github user SudharmaJain commented on the issue: https://github.com/apache/cloudstack/pull/1736 @ustcweizhou You are right. This is not fixing the issue. --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---