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 AAB8C200BD5 for ; Thu, 8 Dec 2016 11:11:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A96B4160B30; Thu, 8 Dec 2016 10:11:59 +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 E0207160B1E for ; Thu, 8 Dec 2016 11:11:58 +0100 (CET) Received: (qmail 67093 invoked by uid 500); 8 Dec 2016 10:11:53 -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 67069 invoked by uid 99); 8 Dec 2016 10:11:52 -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; Thu, 08 Dec 2016 10:11:52 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1CC4BED225; Thu, 8 Dec 2016 10:11:52 +0000 (UTC) From: borisstoyanov To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1796: CLOUDSTACK-9626: Instance fails to start after unsuc... Content-Type: text/plain Message-Id: <20161208101152.1CC4BED225@git1-us-west.apache.org> Date: Thu, 8 Dec 2016 10:11:52 +0000 (UTC) archived-at: Thu, 08 Dec 2016 10:11:59 -0000 Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1796 @rhtyd I don't see any smoke testing job in Trillian about this PR, should we kick another one? --- 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. ---