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 61FF810F70 for ; Wed, 30 Apr 2014 12:33:16 +0000 (UTC) Received: (qmail 77339 invoked by uid 500); 30 Apr 2014 12:33:16 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 77260 invoked by uid 500); 30 Apr 2014 12:33:15 -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 77253 invoked by uid 500); 30 Apr 2014 12:33:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 77249 invoked by uid 99); 30 Apr 2014 12:33:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Apr 2014 12:33:14 +0000 Date: Wed, 30 Apr 2014 12:33:14 +0000 (UTC) From: "Remi Bergsma (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-6538) Migrating a volume causes snapshot schedule to disappear MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Remi Bergsma created CLOUDSTACK-6538: ---------------------------------------- Summary: Migrating a volume causes snapshot schedule to disapp= ear Key: CLOUDSTACK-6538 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6538 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the defa= ult.) Affects Versions: 4.3.0 Reporter: Remi Bergsma When a volume is migrated to another primary storage, the snapshot schedule= that exists before migration, is no longer active after migration. Steps to reproduce: - create a volume - create a snapshot policy - note it creates an entry in cloud.snapshot_policy table - migrate volume to another primary storage - note the entry in cloud.snapshot_policy has been deleted Cause: Migrating a volume leads to a volume with a new id and uuid. Since the snap= shot schedule is linked to a volume based on id, this is lost after migrati= on. Please: - do not delete entries in cloud.snapshot_policy but mark as =E2=80=98delet= ed=E2=80=99 instead (like done on other tables) - recreate the snapshot schedule for a volume that was migrated, using its = new id. Or update the table with the new id. This is a serious bug, because the user does not expect the snapshot schedu= le to disappear. Hence, when a snapshot is needed after migration you have = a problem that cannot be fixed. -- This message was sent by Atlassian JIRA (v6.2#6252)