I can only +1 to the issue, as regular members are able to issue a backup create request which will apparently fail on creation (I'd expect cinder API to fail on request if no backup services are registered though) and block further volume operations due to this existing failed backup, which should not have been created at the first place. On Thu, 27 Feb 2025, 20:28 franck, <franck.vedel@univ-grenoble-alpes.fr> wrote:
Hi, My problem is: openstack volume backup list --all-projects
+--------------------------------------+------------------+-------------+--------+------+ | ID | Name | Description | Status | Size |
+--------------------------------------+------------------+-------------+--------+------+ | af77d0e5-b00b-4dd2-9f98-4f6cce1f28b7 | kube ok | | error | 40 | | de360574-cb9d-48ae-afaa-7147176dafad | sauvegarde servb | | error | 15 | | 017e7b58-ffa4-4133-9580-77ebd4261c8a | k3s-slave | | error | 40 | | 35d432e2-f5cc-478b-a6f6-023276df8756 | sae4dc01 | | error | 20 |
+--------------------------------------+------------------+-------------+--------+———+
openstack volume backup delete af77d0e5-b00b-4dd2-9f98-4f6cce1f28b7 Failed to delete backup with name or ID 'af77d0e5-b00b-4dd2-9f98-4f6cce1f28b7': Service cinder-backup could not be found. (HTTP 404) (Request-ID: req-0bca34a6-e353-4bf3-aafc-a7adb05b786b) 1 of 1 backups failed to delete.
openstack volume backup show af77d0e5-b00b-4dd2-9f98-4f6cce1f28b7 +-----------------------+----------------------------------------+ | Field | Value | +-----------------------+----------------------------------------+ | availability_zone | None | | container | None | | created_at | 2025-01-28T22:47:22.000000 | | data_timestamp | 2024-12-09T10:09:54.000000 | | description | | | fail_reason | Service not found for creating backup. | | has_dependent_backups | False | | id | af77d0e5-b00b-4dd2-9f98-4f6cce1f28b7 | | is_incremental | False | | name | kube ok | | object_count | 0 | | size | 40 | | snapshot_id | 41b6559f-1d13-47cc-987b-35b53420a97e | | status | error | | updated_at | 2025-01-28T22:47:22.000000 | | volume_id | 4743398b-dfcc-4a0c-8ddc-62a730278e26 | +-----------------------+————————————————————+
I don't know how users were able to create these backups at one point, probably during a test of setting up this service before deleting it. But now: fail_reason | Service not found for creating backup.
How can I proceed to delete this volume backups ? I tried to restart the service and delete backups. No success.
Thanks for your help
Franck VEDEL