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 76213200C3F for ; Wed, 22 Mar 2017 10:56:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6A077160B86; Wed, 22 Mar 2017 09:56:46 +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 A7EFE160B83 for ; Wed, 22 Mar 2017 10:56:45 +0100 (CET) Received: (qmail 24367 invoked by uid 500); 22 Mar 2017 09:56:44 -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 24346 invoked by uid 99); 22 Mar 2017 09:56:44 -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, 22 Mar 2017 09:56:44 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B143DDFE7B; Wed, 22 Mar 2017 09:56:43 +0000 (UTC) From: borisstoyanov To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #2003: CLOUDSTACK-9811: fixed an issue if the dev is not in... Content-Type: text/plain Message-Id: <20170322095643.B143DDFE7B@git1-us-west.apache.org> Date: Wed, 22 Mar 2017 09:56:43 +0000 (UTC) archived-at: Wed, 22 Mar 2017 09:56:46 -0000 Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2003 @rhtyd I think this was introduced with the StrongSwan implementation which was 4.10 I think. --- 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. ---