has_dependent_backup of backup is false, but the backup has a child backup that its status is available

Bug #1911604 reported by FengJiankui
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Incomplete
Low
Tushar Trambak Gite

Bug Description

After backup A created a snapshot, backup A created a error incremental backup C, has_dependent_backup of backup A is false at this time. Backup A created a available incremental backup B with snapshot, two incremental backups were created based on backup A and has_dependent_backup of backup A is true at this time. After error incremental backup C deleted, has_dependent_backup of backup A become false, but backup has a dependency backup B that its status is available.

After error incremental backup C deleted, backup A and available incremental backup B as follows:

+-----------------------+--------------------------------------------+
| Property | Value |
+-----------------------+--------------------------------------------+
| availability_zone | nova1 |
| container | 77/b0/77b05a77-5f1a-49b1-8764-e13ed10822d7 |
| created_at | 2021-01-14T01:41:29.000000 |
| data_timestamp | 2021-01-14T01:41:29.000000 |
| description | None |
| fail_reason | None |
| has_dependent_backups | False |
| id | 77b05a77-5f1a-49b1-8764-e13ed10822d7 |
| is_incremental | False |
| name | fjkA |
| object_count | 214 |
| size | 10 |
| snapshot_id | None |
| status | available |
| updated_at | 2021-01-14T01:50:17.000000 |
| volume_id | b6e4b83e-3025-4f28-9370-417d784379a8 |
+-----------------------+--------------------------------------------+

+-----------------------+--------------------------------------------+
| Property | Value |
+-----------------------+--------------------------------------------+
| availability_zone | nova1 |
| container | a2/31/a23155f3-7ec3-4fcc-80b3-bc8be47926ef |
| created_at | 2021-01-14T01:47:28.000000 |
| data_timestamp | 2021-01-14T01:44:18.000000 |
| description | None |
| fail_reason | None |
| has_dependent_backups | False |
| id | a23155f3-7ec3-4fcc-80b3-bc8be47926ef |
| is_incremental | True |
| name | fjkB |
| object_count | 0 |
| size | 10 |
| snapshot_id | 87b032ec-8171-450b-ba9f-a7f85312b2d6 |
| status | available |
| updated_at | 2021-01-14T01:48:24.000000 |
| volume_id | b6e4b83e-3025-4f28-9370-417d784379a8 |
+-----------------------+--------------------------------------------+

Try to delete backup A, as follows:

openstack volume backup delete 77b05a77-5f1a-49b1-8764-e13ed10822d7
Failed to delete backup with name or ID '77b05a77-5f1a-49b1-8764-e13ed10822d7': Invalid backup: Incremental backups exist for this backup. (HTTP 400) (Request-ID: req-c900063c-3e12-4951-86d6-4b451deac808)
1 of 1 backups failed to delete.

Revision history for this message
michael-mcaleer (mmcaleer) wrote :

Hi,

Can you please provide clear steps to reproduce this issue, the provided summary is not clear enough.

Ideally please provide steps in 1, 2, 3 order with any associated CLI commands used.

Thanks

Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
tags: added: backup delete snapshot
Changed in cinder:
status: Triaged → Incomplete
importance: Medium → Low
Revision history for this message
FengJiankui (fengjiankui) wrote :

The detailed steps as follows:

step 1: crate a volume volume_test.
step 2: create a non-incremental backup A of volume volume_test successfully.
step 3: create a snapshot of volume volume_test.
step 4: create a incremental backup B of volume volume_test, but fail to create, status of backup B is error.
step 5: create a incremental backup C of volume volume_test with snapshot, backup C is created successfully, its status is available. At this time, volume volume_test has two incremental backups, and their parent backups are all non-incremental backup A.
step 6: delete incremental backup B, has_dependent_backup of backup A became false after successfully deleting B. But, backup A has a incremental backup C, and its status is available.

Changed in cinder:
assignee: nobody → Tushar Trambak Gite (tushargite96)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.