cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Bergsma (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-6538) Migrating a volume causes snapshot schedule to disappear
Date Wed, 30 Apr 2014 12:33:14 GMT
Remi Bergsma created CLOUDSTACK-6538:
----------------------------------------

             Summary: Migrating a volume causes snapshot schedule to disappear
                 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 default.)
    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 snapshot schedule is
linked to a volume based on id, this is lost after migration.

Please:
- do not delete entries in cloud.snapshot_policy but mark as ‘deleted’ 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 schedule 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)

Mime
View raw message