ceph backup needs to ignore stale snapshots

Bug #1221836 reported by Edward Hope-Morley on 2013-09-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Undecided
Edward Hope-Morley

Bug Description

I just hit an issue with the following steps:

1. create vol
2. create backup (works fine uses incremental diff)
3. delete backup
4. create new backup (full copy forced because volume backup-snap exists and is not ignored)

The ceph backup driver needs to either (a) ignore the backup snap if the base it was applied to was deleted or (b) delete the backup snap when the backup is deleted if the base is being deleted.

Changed in cinder:
assignee: nobody → Edward Hope-Morley (hopem)
status: New → In Progress

Reviewed: https://review.openstack.org/45480
Committed: http://github.com/openstack/cinder/commit/c5060dd0e796ac92ecb2b5d75f9e700509827806
Submitter: Jenkins
Branch: master

commit c5060dd0e796ac92ecb2b5d75f9e700509827806
Author: Edward Hope-Morley <email address hidden>
Date: Fri Sep 6 20:40:38 2013 +0100

    Fixed erroneous force full copy in ceph backup driver

    The following steps should not result in a forced full copy:

    1. create vol
    2. create backup (works fine i.e. uses incremental diff)
    3. delete backup
    4. create new backup (full copy forced because volume backup-snap exists and is not ignored)

    This patch resolves the above problem.

    Change-Id: I61c245219f54f7ee942e06e343c5d79d4cab947b
    Fixes: bug #1221836

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-10-04
Changed in cinder:
milestone: none → havana-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-rc1 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers