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 0F626E7C4 for ; Thu, 30 May 2013 12:53:25 +0000 (UTC) Received: (qmail 85916 invoked by uid 500); 30 May 2013 12:53:24 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 85253 invoked by uid 500); 30 May 2013 12:53:24 -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 84824 invoked by uid 500); 30 May 2013 12:53:22 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 84810 invoked by uid 99); 30 May 2013 12:53:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 May 2013 12:53:22 +0000 Date: Thu, 30 May 2013 12:53:22 +0000 (UTC) From: "Srikanteswararao Talluri (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-2768) [SXM] snapshot on a migrated volume is getting NULL path MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-2768: ------------------------------------------------- Attachment: management-server.log.zip > [SXM] snapshot on a migrated volume is getting NULL path > --------------------------------------------------------- > > Key: CLOUDSTACK-2768 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2768 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Snapshot > Affects Versions: 4.2.0 > Reporter: Srikanteswararao Talluri > Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.zip > > > Steps to reproduce: > 1. create two clusters [C1,C2]with two primary storages[P1,P2] respectively. > 2. deploy a VM VM1 and attach 2 data volumes V1,V2. > 3. migrate volume V1. > 4. While volume V1 is being migrated, Migrate VM1 with volumes to Cluster C2. > Step 4 will result in failure and all the volumes and VM should be as it was before migrate operation. > 5. Now, take a snapshot of volume V1 OR V2. This is updating the path in the snapshot table as NULL, which in turn results in Null pointer exception on snapshot operations(template/volume creation from snapshot) > id: 3 > data_center_id: 1 > account_id: 2 > domain_id: 1 > volume_id: 25 > disk_offering_id: 5 > status: BackedUp > path: NULL > name: sharedshared_tt_20130530164422 > uuid: 3ba59708-cb37-4019-a54c-5f6db4eaa36d > snapshot_type: 0 > type_description: MANUAL > size: 107374182400 > created: 2013-05-30 16:44:22 > removed: NULL > backup_snap_id: NULL > swift_id: NULL > sechost_id: NULL > prev_snap_id: 0 > hypervisor_type: XenServer > version: 2.2 > s3_id: NULL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira