Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 83588187C2 for ; Thu, 22 Oct 2015 10:26:49 +0000 (UTC) Received: (qmail 3370 invoked by uid 500); 22 Oct 2015 10:26:49 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 3310 invoked by uid 500); 22 Oct 2015 10:26:49 -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 3299 invoked by uid 99); 22 Oct 2015 10:26:48 -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, 22 Oct 2015 10:26:48 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id BB279E3916; Thu, 22 Oct 2015 10:26:48 +0000 (UTC) From: michaelandersen To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Improve marvin test site2site VPN Content-Type: text/plain Message-Id: <20151022102648.BB279E3916@git1-us-west.apache.org> Date: Thu, 22 Oct 2015 10:26:48 +0000 (UTC) Github user michaelandersen commented on the pull request: https://github.com/apache/cloudstack/pull/952#issuecomment-150173017 The exceptions: error: [Errno 113] No route to host error: [Errno 111] Connection refused until ===SSH to Host 192.168.23.12 port : 22 SUCCESSFUL=== basically show the state change of the VM to which the test is trying to connect to. the exceptions can be ignored as the test is able to login and perform the assertion --- 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. ---