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 5C0472009A8 for ; Tue, 17 May 2016 21:03:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5AAA51609F5; Tue, 17 May 2016 19:03:26 +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 9925F1607A8 for ; Tue, 17 May 2016 21:03:25 +0200 (CEST) Received: (qmail 36333 invoked by uid 500); 17 May 2016 19:03:24 -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 36322 invoked by uid 99); 17 May 2016 19:03:24 -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; Tue, 17 May 2016 19:03:24 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 444B4DFB93; Tue, 17 May 2016 19:03:24 +0000 (UTC) From: swill To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9362: Skip VXLANs when rewriti... Content-Type: text/plain Message-Id: <20160517190324.444B4DFB93@git1-us-west.apache.org> Date: Tue, 17 May 2016 19:03:24 +0000 (UTC) archived-at: Tue, 17 May 2016 19:03:26 -0000 Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1513#issuecomment-219820368 Not sure what to think of that. I have never seen those errors before in my environment... --- 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. ---