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 E9E8B200C53 for ; Tue, 28 Mar 2017 08:24:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E8752160B99; Tue, 28 Mar 2017 06:24:26 +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 32FFC160B85 for ; Tue, 28 Mar 2017 08:24:26 +0200 (CEST) Received: (qmail 481 invoked by uid 500); 28 Mar 2017 06:24:25 -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 469 invoked by uid 99); 28 Mar 2017 06:24:24 -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; Tue, 28 Mar 2017 06:24:24 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B5EDDDFBCA; Tue, 28 Mar 2017 06:24:24 +0000 (UTC) From: koushik-das To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1953: CLOUDSTACK-9794: Unable to attach more than 14 devic... Content-Type: text/plain Message-Id: <20170328062424.B5EDDDFBCA@git1-us-west.apache.org> Date: Tue, 28 Mar 2017 06:24:24 +0000 (UTC) archived-at: Tue, 28 Mar 2017 06:24:27 -0000 Github user koushik-das commented on the issue: https://github.com/apache/cloudstack/pull/1953 @karuturi This PR is not correct and is resulting in travis CI failures. It needs to be properly fixed. --- 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. ---