Comment 1 for bug 1764269

Hi,
I have tried to reproduce this issue on latest release but not able to validate.
May be it's already fixed on latest but I am not sure about it. Also delete() function has changed to delete_backup() in latest release(Rocky).
Please suggest the conclusion pointer to verify the bug because "cinder backup-list" showing blank data and I am considering it has deleting/erasing completely.

Followed steps by me:
========================================
stack@ubuntu-xenial:~/cinder$ cinder backup-create --name newvol_bak 5d85b172-26f9-4f84-92e8-50941f3e7f1a +-----------+--------------------------------------+
| Property | Value |
+-----------+--------------------------------------+
| id | 918a9142-7ff3-448c-a90e-78c9b5832e96 |
| name | newvol_bak |
| volume_id | 5d85b172-26f9-4f84-92e8-50941f3e7f1a |
+-----------+--------------------------------------+

stack@ubuntu-xenial:~/cinder$ cinder backup-list
+--------------------------------------+--------------------------------------+-----------+------------+------+--------------+---------------+
| ID | Volume ID | Status | Name | Size | Object Count | Container |
+--------------------------------------+--------------------------------------+-----------+------------+------+--------------+---------------+
| 918a9142-7ff3-448c-a90e-78c9b5832e96 | 5d85b172-26f9-4f84-92e8-50941f3e7f1a | available | newvol_bak | 1 | 22 | volumebackups |
+--------------------------------------+--------------------------------------+-----------+------------+------+--------------+---------------+

stack@ubuntu-xenial:~/cinder$ cinder backup-delete 918a9142-7ff3-448c-a90e-78c9b5832e96 & sleep 3; sudo systemctl stop <email address hidden>
[1] 20381Request to delete backup 918a9142-7ff3-448c-a90e-78c9b5832e96 has been accepted.[1]+ Done cinder backup-delete 918a9142-7ff3-448c-a90e-78c9b5832e96

stack@ubuntu-xenial:~/cinder$ cinder backup-list
+----+-----------+--------+------+------+--------------+-----------+
| ID | Volume ID | Status | Name | Size | Object Count | Container |
+----+-----------+--------+------+------+--------------+-----------+
+----+-----------+--------+------+------+--------------+-----------+

I have tried to stop swift-proxy service multiple times(parallely with delete operation of cinder backup operation and with 1~3 seconds of difference) but it is always resulting in complete deletion.
Please let me know where should I check for the internal thing for the occurrence.