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 424BD200BC7 for ; Fri, 25 Nov 2016 16:12:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 40E1D160B1C; Fri, 25 Nov 2016 15:12:31 +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 831CF160B01 for ; Fri, 25 Nov 2016 16:12:30 +0100 (CET) Received: (qmail 91513 invoked by uid 500); 25 Nov 2016 15:12:28 -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 91209 invoked by uid 99); 25 Nov 2016 15:12:28 -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; Fri, 25 Nov 2016 15:12:28 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3E078E04BB; Fri, 25 Nov 2016 15:12:28 +0000 (UTC) From: syed To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1780: Fix the KVM hypervisor's handling of not-really-SCSI... Content-Type: text/plain Message-Id: <20161125151228.3E078E04BB@git1-us-west.apache.org> Date: Fri, 25 Nov 2016 15:12:28 +0000 (UTC) archived-at: Fri, 25 Nov 2016 15:12:31 -0000 Github user syed commented on the issue: https://github.com/apache/cloudstack/pull/1780 @ppenchev-storpool I haven't worked with a non-iscsi adaptor for KVM but wouldn't it change the default behaviour now for non-iscsi disks? What if the other adaptors also ignore this? Can we add a default? Also is there a way of adding another adopter to test this from an integration test? --- 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. ---