backup delete fail
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Triaged
|
Low
|
FengJiankui | ||
Bug Description
an backup attribute has_dependent_
Failed to delete backup with name or ID '40b9d629-
1 of 1 backups failed to delete.
the backup detail as follows:
+------
| Property | Value |
+------
| availability_zone | nova1 |
| container | 40/b9/40b9d629-
| created_at | 2020-12-
| data_timestamp | 2020-12-
| description | None |
| fail_reason | None |
| has_dependent_
| id | 40b9d629-
| is_incremental | False |
| name | test1 |
| object_count | 22 |
| size | 1 |
| snapshot_id | None |
| status | available |
| updated_at | 2020-12-
| volume_id | 50ae12d3-
+------
Found there is a backup with an error status, its parent backup is above backup.
+------
| Property | Value |
+------
| availability_zone | nova1 |
| container | None |
| created_at | 2020-12-
| data_timestamp | 2020-12-
| description | None |
| fail_reason | global name 'dd' is not defined |
| has_dependent_
| id | 4de46669-
| is_incremental | True |
| name | test2 |
| object_count | 0 |
| size | 1 |
| snapshot_id | None |
| status | error |
| updated_at | 2020-12-
| volume_id | 50ae12d3-
after delete the child backup, parent backup can be deleted
| Changed in python-cinderclient: | |
| assignee: | nobody → FengJiankui (fengjiankui) |
| Changed in python-cinderclient: | |
| status: | New → Triaged |
| tags: | added: backup dependents failure |
| Changed in python-cinderclient: | |
| importance: | Undecided → Low |
| affects: | python-cinderclient → cinder |
| Brian Rosmaita (brian-rosmaita) wrote | #1 |
| FengJiankui (fengjiankui) wrote | #2 |
This needs to be fixed in Cinder, the python-cinderclient is just acting as an interface here.
Please read through the discussion at this week's cinder meeting:
http://
A few key points:
1) has_dependent_
2) we could implement a 'cascade' option for deletion that would delete a backup AND its dependent backups. This is probably a good idea independently of this particular bug. Its impact on this bug is that it would be useful in this situation, though a user wouldn't know to use it immediately because has_dependent_
3) we could implement it so that if a backup is requested to be deleted, and it has a dependent backup in ERROR status, then it acts like 'cascade' even without the 'cascade' option.
Think it over, and we can discuss it in #openstack-cinder or at the weekly meeting or on the mailing list.