Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 8 Jul 2015 14:44:04 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12711449.1398861178000.130718.1436366644768@Atlassian.JIRA>
In-Reply-To: <JIRA.12711449.1398861178000@Atlassian.JIRA>
References: <JIRA.12711449.1398861178000@Atlassian.JIRA>
 <JIRA.12711449.1398861178415@arcas>
Subject: [jira] [Updated] (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


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6538?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daan Hoogland updated CLOUDSTACK-6538:
--------------------------------------
    Fix Version/s:     (was: 4.5.2)
                   Future

> Migrating a volume causes snapshot schedule to disappear
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-6538
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-653=
8
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.3.0
>            Reporter: Remi Bergsma
>            Assignee: Abhinandan Prateek
>             Fix For: Future
>
>
> When a volume is migrated to another primary storage, the snapshot schedu=
le 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 sn=
apshot schedule is linked to a volume based on id, this is lost after migra=
tion.
> Please:
> - do not delete entries in cloud.snapshot_policy but mark as =E2=80=98del=
eted=E2=80=99 instead (like done on other tables)
> - recreate the snapshot schedule for a volume that was migrated, using it=
s new id. Or update the table with the new id.
> This is a serious bug, because the user does not expect the snapshot sche=
dule to disappear. Hence, when a snapshot is needed after migration you hav=
e a problem that cannot be fixed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)