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 9C83E200C54 for ; Wed, 12 Apr 2017 14:47:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9B27C160B95; Wed, 12 Apr 2017 12:47:07 +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 D82FE160B8A for ; Wed, 12 Apr 2017 14:47:06 +0200 (CEST) Received: (qmail 59087 invoked by uid 500); 12 Apr 2017 12:47:06 -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 59076 invoked by uid 99); 12 Apr 2017 12:47:05 -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; Wed, 12 Apr 2017 12:47:05 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 94CA8DFC31; Wed, 12 Apr 2017 12:47:05 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and... Content-Type: text/plain Message-Id: <20170412124705.94CA8DFC31@git1-us-west.apache.org> Date: Wed, 12 Apr 2017 12:47:05 +0000 (UTC) archived-at: Wed, 12 Apr 2017 12:47:07 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1879 @karuturi thanks I'll see how I can help. This PR though looks like a bug to me, though not a blocker. --- 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. ---