Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E97EF17C66 for ; Wed, 9 Sep 2015 05:34:45 +0000 (UTC) Received: (qmail 76824 invoked by uid 500); 9 Sep 2015 05:34:45 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 76786 invoked by uid 500); 9 Sep 2015 05:34:45 -0000 Mailing-List: contact issues-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 issues@cloudstack.apache.org Received: (qmail 76776 invoked by uid 500); 9 Sep 2015 05:34:45 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 76773 invoked by uid 99); 9 Sep 2015 05:34:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 05:34:45 +0000 Date: Wed, 9 Sep 2015 05:34:45 +0000 (UTC) From: "Koushik Das (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-8826) XenServer - Use device id passed as part of attach volume API properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Koushik Das created CLOUDSTACK-8826: --------------------------------------- Summary: XenServer - Use device id passed as part of attach volume API properly Key: CLOUDSTACK-8826 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8826 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.6.0 Reporter: Koushik Das Assignee: Koushik Das Fix For: 4.6.0 Random failures were seen in XS attach/detach volume test scenarios (many attach/detach were performed on the same VM over a span of 24 hrs). The failures happened as the device id for attaching volume wasn't available in HV. Some detached volume didn't got cleaned up properly and so the device id wasn't released. The fix would be clean up stale volumes before attaching new ones so the device slots are released. Also using the device id should be best effort and if that particular id is not available in XS, it should fallback on using an id that is available and automatically assigned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)