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 EE97D200BBA for ; Sat, 5 Nov 2016 14:07:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id ED20A160AEF; Sat, 5 Nov 2016 13:07:28 +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 660D5160AE0 for ; Sat, 5 Nov 2016 14:07:28 +0100 (CET) Received: (qmail 39218 invoked by uid 500); 5 Nov 2016 13:07: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 39207 invoked by uid 99); 5 Nov 2016 13:07: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; Sat, 05 Nov 2016 13:07:27 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 16EB5E03D1; Sat, 5 Nov 2016 13:07:27 +0000 (UTC) From: prashanthvarma To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1578: CLOUDSTACK-9401 : Support for Internal DNS in Nuage ... Content-Type: text/plain Message-Id: <20161105130727.16EB5E03D1@git1-us-west.apache.org> Date: Sat, 5 Nov 2016 13:07:27 +0000 (UTC) archived-at: Sat, 05 Nov 2016 13:07:29 -0000 Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1578 @jburwell @rhtyd We have briefly investigated the above test failures, and here are our findings: 1) No single test is failing across all the environments, and this PR doesn't contain any "hypervisor" specific changes. 2) The failed test on KVM "test_01_create_template" looks more like a timing issue, and we might not always hit it (refer above comment). Is there a way, we can re-trigger the above failing tests on your CI environment, and also get the management server logs for them to further debug these failures ? It will also be handy for us to get the results and logs of these tests when ran against latest master. Hope, we are not asking to much :) Meanwhile, we will try to reproduce these failures on our setups. --- 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. ---