We are using as Cinder backup driver: 'cinder.backup.drivers.ceph.CephBackupDriver'
1) I used the openstackclient to change the backup state. `openstack volume backup set --state error <backup-id>`
It should do the same!? But no, I did not use the cinder client directly as you mentioned. The state could not be changed with the command I used.
2) Yes, I tried to solve the problem by let the cinder-backup service change the state to error. But this one checks at first if a volume for that backup still exists. I found the code line for that here [1]. It seems that cinder needs an existing volume even the scope is to change a backup state.
So the request fails because of the VolumeNotFound exception thrown here [2].
Hi Sofia,
thanks for your answer.
We are using as Cinder backup driver: 'cinder. backup. drivers. ceph.CephBackup Driver'
1) I used the openstackclient to change the backup state. `openstack volume backup set --state error <backup-id>`
It should do the same!? But no, I did not use the cinder client directly as you mentioned. The state could not be changed with the command I used.
2) Yes, I tried to solve the problem by let the cinder-backup service change the state to error. But this one checks at first if a volume for that backup still exists. I found the code line for that here [1]. It seems that cinder needs an existing volume even the scope is to change a backup state.
So the request fails because of the VolumeNotFound exception thrown here [2].
Thanks for your help.
[1]: https:/ /github. com/openstack/ cinder/ blob/78fac2960d 28e97f42454bb5f 385b46fbae23a3c /cinder/ backup/ manager. py#L230 /github. com/openstack/ cinder/ blob/d4535c7749 3a7b362091b962f 42f2613dea65dbe /cinder/ db/sqlalchemy/ api.py# L2126
[2]: https:/