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 616F4200C23 for ; Wed, 22 Feb 2017 11:12:34 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5FFDF160B7D; Wed, 22 Feb 2017 10:12:34 +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 9E60A160B49 for ; Wed, 22 Feb 2017 11:12:33 +0100 (CET) Received: (qmail 1399 invoked by uid 500); 22 Feb 2017 10:12:27 -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 1380 invoked by uid 99); 22 Feb 2017 10:12:27 -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 Feb 2017 10:12:27 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 6BF57DFF09; Wed, 22 Feb 2017 10:12:27 +0000 (UTC) From: blueorangutan To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #843: Security group ingress/egress issues with xenserver 6... Content-Type: text/plain Message-Id: <20170222101227.6BF57DFF09@git1-us-west.apache.org> Date: Wed, 22 Feb 2017 10:12:27 +0000 (UTC) archived-at: Wed, 22 Feb 2017 10:12:34 -0000 Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/843 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + xenserver-65sp1) has been kicked to run smoke tests --- 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. ---